Posted by ADB52 on 6 October 2021 in English (English).

I am detecting problems with the uploads of changesets. Changeset 1139474 is to do with the relocation of the Utterland city of Galmosen to the east by 13 km. As can be seen on the map, there is a section of railway at a crazy angle, which is NOT shown as such on JOSM. Changeset 1134839 contains the deletion of several primary roads and railways in Utterland, which (again) are not shown as deleted on the map. Today, I discovered that changeset 1134798, uploaded by bhj867 served to delete parts of a river that forms the border between Isztianorszag and Utterland, following the deletion of a very large multipolygon of landuse=forest that stretched from Utterland to Pretany. bhj867 has informed me that he did not download data from Utterland. Does anyone else have similar glitches, and could this be looked into. Thanks.

Comment from bhj867 on 6 October 2021 at 20:22

I wonder if there is a way to revert that one multipolygon to reconstruct your border area

Comment from Luciano on 7 October 2021 at 17:35


It would be nice if you could provide links to your changesets. It makes researching things marginally easier. I’m a bit confused by the changesets you reference.

changeset 1139474 is listed as “not found” by OGF.

changeset 1134839 has a large number of deleted objects. I believe I’ve discussed this before, but I’ll mention it again here: mass deletions (1000’s of objects deleted in a single changeset) seem to cause problems for the replication-to-render pipeline, and result in “ghosts” of deleted objects persisting FOREVER in the render (until the render is reset from zero - not something I want to do frequently).

changeset 1134798 is attributed to user Y Knott (not bhj867), and included tag modifications of exactly 1 node and one way, with zero deletions or creations.

General advice for all users:

When deleting large numbers of objects, please be careful. This is not a use-case that the OSM software is designed to handle (think about it - mass deletions are NOT common on OSM). Divide up your deletions to cover small numbers of objects (<1000) and small areas (so if something goes wrong you don’t mess up large areas).

Comment from ADB52 on 7 October 2021 at 21:16

Sorry about the obvious typos in the change-sets I referenced. I also take on board the advice regarding mass alterations, something that applies to my move of Galmosen.

The three changesets from bhj867:

My changeset for Galmosen:

Login to leave a comment