@apm-wa True. For what it’s worth there’re some aftermarket doors with smaller charging access door. That and the car speed (putting the battery access at the back), I never had any issue even through some harsh conditions be it humid freezing conditions or heavy rain (I’m still in disbelief at how good the pictures are. On the first sequence, there was a layer of frozen water on the front part of both lenses. On the second one, it was quite difficult to even drive).

Regarding the battery life, you’re aware that the device can be plugged into the car’s power socket right? During long trips I do that through a 3 m USB cable.

Using JOSM with the noteSolver plugin and NotesReview, it was quite a breeze to go through simple to skim simple notes (either useless or quick to map). I think I’ll stop here for the time being.

As @rompe said, there isn’t any good solution really, one would need to have Ulaanbaatar on its own watchlist for the situation to not decay has it has. The high POI density due to company offices and high-rises scattered all around makes it a pain to review though. Some notes aim to point to POIs which may or may not have replaced others. There’s also the language barrier as most of the notes have some local quirks difficult to translate or interpret. I’m especially dumbfounded by the sheer amount of supermarkets mapped. Pretty sure those are wrong tags but can’t be sure of it. Anybody wanna offer me the travel fare?

@Vétérini Si t’utilises JOSM alors je peux garantir que la mise à niveau est faisable rapidement. Je m’inquiète surtout pour la suite, éviter que la situation se reproduise d’ici quelques mois ou années. J’imagine plus sain que ce soit formalisé soit on tranche que on refera une mise à niveau dans 5 ans quand on se rendra compte que les les collectivités et les éditeurs logiciels pensent qu’OSM et l’interopérabilité des données c’est magique, soit on dit qu’on fait une mise à niveau là et que par la suite un protocole est mis en place pour les traiter au compte goutte (une simple note par la collectivité me paraît le plus simple), soit (grand luxe) la collectivité s’en empare et OSM gagne en pérennité.

@Vétérini Du coup on peut considérer que tu vas faire la mise à niveau et assurer une veille sur les prochains mouvements de classification du réseau ? Que je sache si je peux rayer ce sujet de ma besace ou pas.

(Je parle d’expérience) Pas de solution miracle. OSM est une base de données indépendante, et il faut prendre le temps d’aller modifier la clé ref section par section. Je suis dispo par message privé si nécessaire.

Par curiosité, c’est quelles applications ? De tête j’ai Inforoute ? Ivoir ?

special camera to scan the greenery and to automatically detect those invasive species.

Could you elaborate on that? Both Panoramax and OSM could be used to tag those species (may even be linked up to Wikidata). Sharing or applying the method to default users pictures would be interesting.

We all draw map with hidden hope that AI sometimes replace all of us

@_PG No we don’t.

La question manque de contexte. Où est le problème, et qu’est ce que tu cherches à faire exactement ?

@JD586 Guess you’ll have to try and find out if that fit your workflow. I only use the phone app as a last resort (I prefer to carry a 360° camera which does require a bit of planning ahead), but it did the job quite well for single pictures or sequences.

@LucianoC63 Or more recently, and driven by the french OSM branch (instead of Meta), there’s also Panoramax. While not as populated in the Chicago area, the project main benefits is its federated core. The last ones who have launched their own instance are focused on Argentina.

My only “issue” with your idea is about the traffic signals. While that may be fine as a first approach to insert the traffic light into the road way, that’d be opposed to the “one object, one element” rule where one have multiple lanes drawn. Furthermore, I’d rather like to have the exact position of the traffic light rather than where one is supposed to stop. Should we keep highway=traffic_lights for actual poles location (how about lights hanging on top of lanes?), and create a highway=stop=traffic_lights?. That’s only my opinion.

Any statistics about the common tennis pitches you encountered?

Related: * osm.org/user/SK53/diary/401423 * osm.org/user/SK53/diary/401423#comment54715 * osm.org/user/SK53/diary/401423#comment54779

Had a similar idea about cycleway=asl. To add some context, in France the law required traffic signals (named R11v) to be both on top of a pole, and repeated lower on it. Since 2015 the repetition isn’t required anymore, but nearly every city still has them (Paris seems to have started some removal). One consequence of having them so low on ground is that car drivers use to go up to the pole before stopping and looking at it through the side window. This situation is problematic in numerous ways as drivers’ attention at green light is focused on the light instead of the front of the car, and it’s difficult for cyclists to turn at intersections when coming from a painted bikelane.

Due to the car geometry, removing the repeaters would push back drivers a few meters away from the pole, thus creating an artificial advanced stop line for cyclists. And so, I created a little snippet to query the cycleways leading to traffic signals where ASL could be created with, or without any operators’ agreement (would be a shame if some plastic trash is flown by the wind and stuck to the repeater).

Code snippet for Kiel {{geocodeArea:Kiel}}->.searchArea; ( way(area.searchArea)[~"^cycleway.*$"~"."]; > -> .cyclable; ); node.cyclable["highway"="traffic_signals"]; out geom;

Any tips about the “disconnecting” part of the process?

My two cents, I can see two ways these crossings may be improved:

• crossing:markings: it seems the right of way could be better implied with painting

• crossing:continuous: self explanatory, similar to traffic calming

The grass buffer you mentionned is, still IMO, necessary. As it induces larger turn angles: slowing down drivers and offering better visibility between users at the crossing. Taking for reference the CROW, used for road design in Netherlands.

Good job people! Another usecase (that I’m working on) FYI would be winter service, as shaded areas are more prone to icy patches during the day (aggravated by the lack of visibility to drivers).

J’‘ai bien vu que c’est un WIP, mais ça m’étonne que la réflexion ne démarre pas de la clé generator:method=anaerobic_digestion.

AFAIK there’re not 3 but 4. I wrote up some notes about them in french.

Idem, y a la carte parisienne de Joachimesque.