This will be a good test for osm.ng because the current solution runs entirely in the browser and uses the OSM API aggressively (: And still limited by the current API (one, two)

For those who want to implement it like this, I collect a list of tricky changesets that broke my script

I can’t find any like/dislike buttons

Try opening the browser console (F12 or right-click -> Inspect element) Are there any errors there?

Also try just opening osmcha.org and check that you are logged in to it.

By the way, do you have an OSMCha icon displayed next to the undo changeset button?

it can be offensive in some cultures

👀
I want to try making a button with response templates that users can edit. This is more relevant for changeset, but it can also be done for notes.

Here it is: https://github.com/Lasith-Niro/OSMTimeMachine But apparently there is no working site right now

There is a small warning about multipolygons and ways: if only the coordinates of the line nodes have changed, then the new version of the way/relation will not be created.

I’m still thinking about how to display this in the interface, but somewhere I saw a site that showed the object’s timeline with all the intermittent changes. I can’t remember :(

А есть топ по зарубежью, поглазеть что там у коллег?

№2 ✅ https://github.com/iandees/image-to-osm

Multiple Changeset Bounding Boxes OpenStreetMap-NG is resolving one of the most common newbie issues on OpenStreetMap while making area monitoring more accurate. Changesets now support incremental and deterministic clustering of changes, enabling multiple bounding box support.

osm.org/user/NorthCrab/diary/404701

@GanderPL I will be waiting for your userscript 😉

Two of the nodes modified were information boards that were part of the Belarus - Ukraine border and Belarus-Russia border.

In light of the latest vandalism that breaks the current render, this looks like a tasty target for vandals in the future.

And vectors generalize well to three-dimensional space!

via osm.org/user/Magick93/diary/403416

I forgot to write about one unpleasant feature of open changesets: while they are open, you can’t comment on them. I wouldn’t risk rolling them back either. You can find a full story about the problems of changesets here https://youtu.be/aRcHLKbXlcM

I Have seen that table before, haven’t I? On Github or on Discourse?

I published it only in the Telegram chats: https://t.me/OpenStreetMapDev/7668 https://t.me/ruosm/792186

but I guess there’s not much “monitoring” involved.

The problem is that you already suggest that open changesets should be handled in a special way. This already sounds weird.

As you can see, after a glimpse of 3600 seconds, these are changesets that are closed automatically. These are either StreetComplete users who no longer made any edits as part of the quest. Or connection breaks.

@NorthCrab, in its implementation of API 0.7, offers one interesting thing: sending changes with a single HTTP request. Take a look at the current API and realize how overcomplicated it is: (

Open changesets in their current form, a strange and inconvenient thing. But I think they can be made better.

A rather non-trivial arrangement of documentation about this :)

But even more interesting is that this token is the same in all your sessions. As if there is no problem in this, but the solution is suspicious.

Things get a lot more interesting. If you open the browser console on osm.org (It is important that the map is visible), you will see an OAuth token in the ‘head’ tag with access to edit the map and notes. You don’t even need an extension ̄\(ツ)/ ̄

Blurring is a few lines of css, so it was easy :)

Кстати, Enhanced Replication увидело свет или осталось идеей?

Если алгоритм работает и с веями, и с отношениями, и они еще связаны как то между собой, то всё становится сложнее.

Если веи/отношения как-то связаны/пересекаются, то и разбивать такие пакеты не нужно. Для простоты можно смотреть пересекаются ли bbox объектов.

Кстати, если затронуты только теги, то разбивать тоже просто.

Но ещё проще не доводить до больших правок

bounding box не характеризует правку, а changeset — надуманная группировка для правок

мне взяло где-то 48 часов как бы осознать вообще что происходит…. Ну как это может быть в 21 веке?

Что чейнжсеты бесполезная штука, которыми нельзя даже копию базы поддерживать, это прям грустно. И подпорок, которые сейчас нельзя сломать, для этого особо нет.

Then check out https://prometheus.openstreetmap.org

https://uptime.openstreetmap.org

I localized the Every Door map in Odia language. Let’s see when it will be released to the App.

Please note that in order to work comfortably in your language, you should make sure that the basic tag presets are translated https://app.transifex.com/openstreetmap/id-editor

This App can help me maintain my 100-day streak.

Note to http://streak.osmz.ru and the Telegram bot https://t.me/osm_streak_bot