MxxCon, good point! https://github.com/Zverik/every_door/issues/746

From https://community.openstreetmap.org/t/proposal-osm-org-editor-inclusion-policy/106589 and linked issues I see not much has changed in osm.org governance since 2017, so I’d be wary of going in :)

This really feels like surface:grade tag, which ranks the subjective quality of a road on a 0..3 scale :)

Remind me how in 2010 I looked at populated places in Russia and adjusted tagging to make it feel better: osm.wiki/Proposal:Place_In_Russia

Thank you for sharing! Streaks are indeed detrimental on the long run, and it was one of the reasons Github tried to abandon the day chart. Please rest as much as you can.

fortera_au, I guess you don’t know about three versions of the schema, about how the one we use is practically unusable for apps, and the differences in mapping between countries :) Public transport is indeed the most complex thing to map.

As a person living under all the layers and a few layers down, I’d rotate this 180° :)

А на русском и менее структурированно — вообще в 2016: https://www.youtube.com/watch?v=MKLwLI8fyn0

Ну, я об этом — и что нужно делать — говорил ещё в 2019: https://youtu.be/aRcHLKbXlcM?si=ENu-Z0iLqlHOSPxF&t=878

Моя позиция, как всегда, — bounding box не характеризует правку, а changeset — надуманная группировка для правок, которая не характеризует изменения. Валидировать изменения нужно без оглядки на пакеты правок вообще. Но пока корпорации с деньгами поддерживают старый путь (см. osmcha), незадачливые вахтёры так и будут огрызаться не по адресу.

I’d say the major part of this disruption you’re commenting about came with Rapid, not Overture. Rapid is (and has been) the bigger threat.

Well yes, and also I don’t care :) True, there have been many businesses for packaging the OSM data. Some of which will be disrupted. But very few of those, if any at all (Geofabrik?), made tools that affect mappers.

So if you read OSM as the community of mappers and an ecosystem of data collection, ingestion, and validation tools, then nothing would change with Overture. It was volunteer before and stays hobbyist after.

Hahaha I missed that, thanks Tom!

For the wiki, you should use tokens it provides: osm.wiki/Special:ApiSandbox#action=query&format=json&meta=tokens&type=login

I believe it’s the same for wikidata, since it also uses MediaWiki (I guess?)

Of course, should be fine. It stores a user token to $HOME/.config/PythonCliAuth/tokens.json on Linux, or an equivalent on other systems. Dictinary hashes are provider id (“openstreetmap”) + oauth client id for the app. So as long as you make library users provide you with a client id, you’ll be fine.

This is a really thourough work, thank you for researching this!

Thank you for this write-up! As the author of Every Door, I’m intrigued by OsmAnd’s quick actions and other productivity features, will check them one day.

Regarding ED, the customization feature is on the road map, which would help e.g. spot racks without capacity or use check_date tag for those. But that depends on when I get a couple months working on that exclusively, since it’s the biggest thing planned.

Thanks for mapping with Every Door and making this post, Martijn! I’m glad it helps make the map better in your area :)

• The tree mode is called “micromapping mode” — you can see a title for any button by pressing and holding it.
• Conflicts have a very very low chance of happening, because the app downloads the objects it intends to update and does a three-way merge to build the final object to upload. But of course you can have duplicates that way.
• You can rotate the map with two fingers.

Ha, definitely did not plan for than kind of load :) Thanks for the heads up!

Thank you Amanda! My “later won’t work” was in the context of, “collect data now, map later”. Which I can tell from my experience seldom works: ain’t nobody got time for that. Just “map now”, whenever that “now” can happen for you. When your job is done, it gets harder to procrastinate :)