Hi. "Medica Uruguaya" should be "operator", "name" should be only "Policlinica Prado". Or maybe "Medica Uruguaya" the "name" and branch="Policlinica Prado". But both should'nt be in the name.
It seems like mapping for the renderer...

Hola. No se como hiciste este relevamiento, pero este edificio no tiene esa direccion por Canaro, la puerta esta por Bulevar Artigas.

El StreetComplete te ayuda mucho, pero tenes que usarlo con cierto cuidado porque no siempre tiene razón en lo que pide.

in my opinion they are different cases, as the name on a street does not imply function, but in the case of these entrances it does.
having the entrances to the airport labeled in the language of the user is useful for navigation purposes.

following your criteria, no name:xx would be used in any elements, as the translations could be obtained outside OSM.

Hola. Herramientas de control de calidad marcaron muchos errores en esta zona por el cambio de nombre, que no se hizo en los nodos de los numeros de puerta ni en las relaciones.

Los datos oficiales del SIG de IMM muestran los nombres anteriores. Parece confusa la situación.

¿Que fuente tomaste para cambiar estos nombres?

Saludos.

it isn't also a case of a multilingual name, is a case of localization, and the use is described here osm.wiki/Names#Localization

Tagging spanish names for the entrances it isn't translieration.
There is no violation of "on the ground" rule. Just a translation of the name, like thousands of elements in de database have their translations in the name.

AFAIK there is no functional tag to tag this entrances at airports, so data consumers cannot translate into the language of their users, so for now, the only option is to use a translated descriptive name. The fact that polish word is on the board at promintent font size, and english word are also probably on the board, maybe with a smaller font as secondary name, due to the widespread use of english, does not means that in OSM other languages shouldn't be tagged.

no idea, but is useful for navigation.

Listo!

Gracias, es asi, hay que mapearlo porque no se permite, pero que se puede se puede, muchos autos lo hacen, aca y en muchos otros lugares pasan por arriba del separador ese.

Hola Carlos. ¿Como te ayudo? ¿Elimino ese nodo o lo muevo a las coordenadas que indiques?¿O revierto el cambio por completo?

Thanks. I see now, the issue is Uber as an organized team, is not doing the collaboration as OSM requires. I hope they can see the problem and fix it, because if done properly could be up to date and good quality data.

Hola. Va review que solicitaste.

En las escuelas publicas va el operator:type=public. Ver osm.wiki/ES:Key:operator:type

Hi. Are you sure? User @Neethu%20P%20G says it is part of Uber OSM project, so maybe the source is having drivers reports from a lot of cities.

Hi. In this changeset you seems to add tag "not:brand:wikidata" while keeping "brand:wikidata" with the same value. According to not:brand:wikidata=* both values should not be equal.

Please verify. Thanks.

En OSM landuse=religious significa esto landuse=religious

Hola, creo que o hiciste publicas unas zonas y no te diste cuenta, o estas mapeando informacion incorrecta. Esas zonas son residenciales, no religiosas, Revisalo por favor.

Gracias. ¿Y sabes con los numeros de puerta que hicieron? porque si no hicieron nada queda todo mal, salteado...

Ya antes del semaforo hay tres carriles pintados, y eso lo recuerdo bien porque me ha tocado esperar al medio ahi, lo que no me acuerdo es cuando antes empiezan.

Sorry. I thougth that JOSM doesn't mix different layers in the same changeset...