I have reverted this change because it made the map quality significantly worse

changeset/165959421

I have reverted this change because it made the map quality significantly worse

changeset/165959401

I have reverted this change because it made the map quality significantly worse

changeset/165959374

I have reverted this change because it made the map quality significantly worse

changeset/165959341

I have reverted this change because it made the map quality significantly worse

changeset/165959258

I have reverted this change because it made the map quality significantly worse

I have reverted this change because it made the map quality significantly worse

I have reverted this change because it made the map quality significantly worse

No, the bullets are real, but the targets report the results electronically so it doesn't matter if the targets are located in the middle of the forest. Tom Scott made a video about a similar range once if you're interested https://www.youtube.com/watch?v=2h1s6S4kotE

Yeah thats a 300m rifle shooting range with the club house at the south and electronic targets in the north.

Please do not add nonsensical tags to objects

changeset/151745147

wieso eigentlich "Raiffeisenbank Zürich Flughafen"? Das ist ja recht weit weg vom Flughafen

This turn restriction relation/10587467 doesn't make sense. you cannot turn into a oneway road anyway, so there's no need to map it separately as a turn restriction

please do not modify the map with made up elements just because you want to catch pokemon

changeset/150858869

Ich habe das (Relation) mal aus dem Namen gelöscht, weil das gehört da nicht wirklich hin

It's not only buses and taxis that matter, but people might want to look up a name from a history book from the past, or look for where their family used to live, and their documents will have the old name of the town on it. So there is a reason to try to keep them searchable by names that might not be regularly used in the future anymore.

This is established OSM consensus like for example on node/31782520 and it is handled everywhere the same where conflicts make towns move ownership, as an example in Ukraine or Palestine.

You are correct, using old_name:xx would also have been a good option, but you deleted those too.

historic names stay relevant for a few generations at least until the old inhabitants have completely died off. i.e. in the Germany/Poland/Czech area you still have towns being called by three different names even though they last changed their state in 1945

i have since also found this thread on the forum https://community.openstreetmap.org/t/edit-warring-over-nagorno-karabakh-region-republic/57413 which states that it is policy that while the name=* should be adjusted to the new azerbaijani names, the old multilingual names shall not be removed

I will readd the old hy and ru names. That way they will remain available for searches. The map itself only displays the name=* tag

In this edit you removed some multilingual names for neighborhoods. What was the reason for removing these names?

Ihr habt in diesem Edit den Weg way/35322265#map=17/47.27606/9.41146 auf access=private gestellt. Das ist ja der offizielle Wanderweg von Wasserauen zum Seealpsee.

Sind da Bauarbeiten im Gange, so dass der Wanderweg gesperrt wäre? Auf Schweiz Mobil ist aber nichts angezeigt.

Shouldn't this rather be a vending=gas_bottles like on vending=gas_bottles