Según la propia definición de Verifiability de OSM, lo importante es que otro mapeador pueda acudir al mismo lugar y obtener el mismo dato, “as far as is reasonably possible”; no que pueda comprobarlo necesariamente desde su casa.

OSM reconoce explícitamente local_knowledge como fuente cuando el mapeador vive, trabaja o frecuenta la zona y conoce la información de primera mano o por otras personas locales.

Por tanto, que este uso lingüístico requiera conocimiento local para verificarse no lo convierte por sí mismo en un dato no verificable.

Coincido en que name:es no debería contener traducciones inventadas o automáticas.

En este caso, las formas que añadí corresponden al uso real entre castellanohablantes de la zona. Ese uso local es precisamente el criterio que estoy siguiendo: reflejar cómo se denomina realmente el lugar en castellano, no generar una traducción por mi cuenta.

Por ejemplo, si localmente se usa de forma habitual “Plaza de Colón” (como ocurre en este caso), esa es la forma que corresponde reflejar en name:es; si también se usa “Plaza de Colom”, podría añadirse como alt_name:es.

Buenas. Con “usados por la población local” me refiero a formas castellanas de uso real entre castellanohablantes de la zona, no a nombres oficiales ni a modificar name=*, que he mantenido en catalán.

La propia guía española de OSM para Cataluña indica que name=* debe ir en catalán y que puede añadirse name:es=* cuando se conoce el nombre en castellano, incluso pone ejemplos de traducción del genérico como Carrer → Calle.

Si hay algún caso concreto de este changeset donde la forma de name:es no tenga uso real o sea una traducción inventada por mí, indícamelo y lo reviso. Pero no creo que sea correcto descartar todos los name:es simplemente porque la rotulación oficial esté solo en catalán.

Buenas, ¿Podrías compartir la fuente documental o cartográfica utilizada para definir los límites de Calafell Poble y Cal Bolavà?

Using that Wikipedia link actually proves my point, it explicitly lists Arabic under "Foreign languages". Having been to Ethiopia myself, daily life happens in Amharic and regional languages, not Arabic.

Bringing up etymology, linguistic families, and misinterpreting Wikipedia entries feels like making increasingly convoluted and flawed arguments just to avoid admitting a mistake. Please just acknowledge the error, follow OpenStreetMap standards, and place Arabic names in name:ar=* where they belong.

This will be my final message on this topic. The logical and proper thing to do when you encounter an error is to fix it, not multiply it. Everyone makes mistakes; what matters is having the humility to accept the facts and move forward according to established standards. Goodbye and thanks.

Whether I understand Arabic is not relevant to this discussion. The issue is compliance with OpenStreetMap's tagging conventions.

As I have already explained, if you believe some English names are incorrect, the proper course of action is to research the correct local name and tag it according to OSM's rules: `name=*` for the local primary name, `name:am=*` for Amharic, `name:en=*` for English, and `name:ar=*` for Arabic.

Please stop using existing tagging errors as a justification for introducing new ones. If you encounter incorrect data, correct it in accordance with OSM's guidelines instead of making the data even less consistent. That helps the project; adding incorrect values to `name=*` does not.

I strongly encourage you to follow the established tagging conventions in future edits rather than continuing to make changes that conflict with them.

If English names are currently placed in name=* without appearing on local physical signage, they should indeed be moved to name:en=*, adding another language to name=* does not fix an existing tagging error, it just multiplies it. The "On the Ground" rule strictly requires name=* to reflect physical signage or the primary endonym used by the local population, regardless of linguistic roots or historical connections. For natural features without signs, OSM guidelines mandate using the local endonym for name=* while placing Arabic names in name:ar=* and other languages in their respective name:*.

If you notice incorrect English in name=*, the constructive approach is to research the correct local endonym, update name=*, and move the English text to name:en=* without deleting information. Please acknowledge this core OSM principle and refrain from adding non-conforming languages to the primary name tag moving forward.

I agree, but OSM guidelines strictly separate local primary names from language-specific translations. The name tag must follow local signage and primary local usage ("on the ground" rule).
Etymology or historical origins do not dictate the primary name tag. To keep the map useful and accurate without violating tagging standards, local Arabic names should be added to name:ar=* rather than the main name tag.

There are rules in OSM. The official language of Ethiopia is Amharic. In Eritrea, the working languages are Tigrinya, Arabic, and English, so using a multilingual name tag is correct there, but not in Ethiopia or its cities.

Hi,
please do not add a language in "name", when it's not official in the country

Buenas,
¿Podrías explicar el motivo de traducir estos nombres?
Los añadí tras verificarlos sobre el terreno (on the ground). Los carteles muestran esos nombres exactamente, por lo que no entiendo el motivo de la traducción.

Hi! The spanish part should be in a description tag, i'll fix It asap!
The spelling is as in the inscription IRL, the marker shows the Amharic and the Spelling side by side

I agree, information=tactile_model seems more accurate, thanks

Buenas, perfecto, lo apunto para próximas ediciones!

Hi, why did you revert all the changes i've made?
I mapped the place as I was there, the paths, the park, the signs and even the names in spanish

Is it really all that big green zone the tibeto skveras? I mean there's no sign in the street that says that the north part across the street is the square.
On the Uzupis site and maps, the Tibeto Skveras is only the lower part.

My bad, i didn't see that was already mapped
I'll fix it

It's okay that the official name of the aiport is Васил Левски, but in Spanish as many other language, we don't say Vasil Levski, we say "Aeropuerto de Sofía" as the name:es is the common name of a place not the official_name=* that is a different tag, that, shouldn't be removed.
The official_name of the airport in spanish is "Aeropuerto Internacional Vasil Levski de Sofía" which is not the same as the common name (name:es)
Removing the name:es tag because it looks similar to the transliteration is an error, as "Sofia" (Latin/English) and "Sofía" (Spanish) are orthographically different.
Deleting these tags breaks map internationalization. Even if a name seems "descriptive", if it is the standard way a language refers to a feature ("Monumento a..."), it belongs in the name:XX tag. The historic=memorial tag defines the type of object, but it doesn't replace the linguistic name used by speakers.
osm.wiki/Map_internationalization
official_name=*

Hi, according to the OSM naming guidelines, localized names may be stored using name:<language>=* when they represent an official or commonly used name in that language.
For example, “Aeropuerto de Sofía” is the established Spanish exonym for Sofia Airport and should be tagged as name:es=*, not treated as a descriptive name. This also happens in Churches and many other objects.
I saw that you removed many names of different objects in different languages, please restore all data loss.
osm.wiki/Translation
osm.wiki/Names#Localization
osm.wiki/Names#Names_are_not_for_descriptions

Hi, i added it because the official Sofia Metro maps shows the connection, i didn't know it was under construction but if it's the case, the part under construction should be tagged as such instead of removing it from the relation.