Hello Supaplex, with this changeset you've added a lot of multilingual names to the Orlando city relation but quite a few of those had the value of "Florida" (and only Florida) in those languages but not "Orlando". This was probably a mistake in your large changeset. I hope that my deletions of those wrong name:xx tags (Florida instead of Orlando or Orlando, Florida) in changeset/152561390 are ok with you.

I did delete a lot of name:xx tags that have misrepresented Orlando as Florida. Please check your language to see if the name in your language translates to Orlando or Orlando, Florida (both fine) or Florida (wrong).

Sorry, you are right, this El Valle is not the El Valle that is the region DO-37, I see it now. I misunderstood your changeset comment when I first read it. But with your explanations and while looking at the regions of DO again, it makes sense.

[sorry about the all typos, it should have been:
*all carrying an ISO3166-2 code...
*I would love..
*these codes...
]

Hello thefrankbraun,
El Valle has it's own ISO3166-2 code and that is DO-37. You are right about the two subdivisions, they have their own codes as well. But DO-37 is the code for El Valle, so it should not be removed. DO has two levels of subdivions all caring a ISO3166-2 code. You have already been asked elsewhere (Belgium area) to start a topic at community.openstreetmap.org about your ISO3166-2 code changes. It would love to see if you do that before you continue to work on this codes and delete good information. Thank you.

Looking at the satellite image I don't see a wood in this form otg. Nice art though but please do not enter "artwork" into the map that is not reflecting what is on the ground. Yes, there are a few trees but not a heart-shaped wood. Would you revert this changeset? Thank you.

E.g. the English speaking world in GB and the USA has been faster in adopting the wanted Kyiv instead of the old Kiev and therefore it is right to use Kyiv as name:en and not Kiev anymore. But unfortunately this is not the current situation in e.g. Germany as the Germans may have a habit of adopting changes slower.

and why I truly understand your motivations, this is not how OSM works. OSM reflects how the world is, not how the world should be. So right now for e.g. :de it would be official_name:de and alt_name:de as Kyjiw and name:de as Kiew (and yes, this might change in the future if Kyjiw becomes familiar in German and is widely used in German. But this is not the current state in German so this would not reflect the current reality).

There is no otg truth for how a place is named in a foreign language. otg is applied for name and name:uk but not name:de, name:fr etc. Those "otg" would eg. newspapers in German, French, etc, or scientific papers, how people in Germany, France etc. would spell the name, etc.

Hello avinet_ua, please stop editing name:xx values where local knowledge does not apply. The official name is to be recorded in official_name:de, not name:de. name:de is for the commonly used name in German speaking communities and should therefore be edited by the German speaking OSM community. The same applies to name:fr etc. With your local knowledge you should just edit name and name:uk values but not other language name tags. You are also destroying the logic of alt_name:xx and official_name:xx that are used to reflect the current naming in e.g. Germany or France, etc. So please revert your changesets of the last couple of days in regard to your name:xx changes.

Ciao,

l'aggiunta del "name:it" segue questa logica:

osm.wiki/Names#Rationale

these reverts may temporarily not fix the problem with vandalism as those vandalism is stacked and several reverts are sometimes needed to fix the node/relation/way

changeset/140431615

these reverts may temporarily not fix the problem with vandalism as those vandalism is stacked and several reverts are sometimes needed to fix the node/relation/way

changeset/140431604

these reverts may temporarily not fix the problem with vandalism as those vandalism is stacked and several reverts are sometimes needed to fix the node/relation/way

changeset/140431597

these reverts may temporarily not fix the problem with vandalism as those vandalism is stacked and several reverts are sometimes needed to fix the node/relation/way

changeset/140431583

these reverts may temporarily not fix the problem with vandalism as those vandalism is stacked and several reverts are sometimes needed to fix the node/relation/way

changeset/140431564

these reverts may temporarily not fix the problem with vandalism as those vandalism is stacked and several reverts are sometimes needed to fix the node/relation/way

changeset/140431556

these reverts may temporarily not fix the problem with vandalism as those vandalism is stacked and several reverts are sometimes needed to fix the node/relation/way

changeset/140431553

these reverts may temporarily not fix the problem with vandalism as those vandalism is stacked and several reverts are sometimes needed to fix the node/relation/way

changeset/140431543

these reverts may temporarily not fix the problem with vandalism as those vandalism is stacked and several reverts are sometimes needed to fix the node/relation/way

changeset/140431535