Could you check this way, it got a strange tag:
way/1502549257

Is this really correct? Are there really 10000 hairdressers in this small area, and more than 30 separate ones in some buildings?

Also: Please make sure you follow our Import Guidelines - what is the source of all this data, where is the mandatory documentation of the import?

Hi
you used a strange 'Nro' tag here. Is this the house number?

Hi,
please check this way, it didn't get a proper tag:
way/1501222416

Thanks! For this kind of signs its often better to use the "conditional" syntax:
vehicle:conditional = no @ "commercial vehicles"
This makes it clearer that it is just some random text and not an official category.

Something went wrong here - 25000 buildings got a strange "ed_ciu" tag. Many also have invalid values for their height, e.g. 0.

Hi,
what does 'access:commercial' mean? This tag isn't used in other places.

Hi,
thanks!
We somehow never managed to define a proper scheme for fixed coordinates of survey points...

There are various things, mostly from one-time imports. On two nodes I found this scheme, which seems quite self explanatory and useful:

survey:datum:EPSG = 21037
survey:easting = 207702.062
survey:northing = 9970033.323

Ist dieser Hydrant nur Deko? Dann sollte er kein emergency=* Tag haben.

Hi,
what kind of coordinates are "eov"? This tag is not used in any other place.

Please check this import. You added many thousands of misspelled "building:levels=" keys.

Hi,
you added the strange tag "addr:street_clean' thousands of times across the world. Please check and fix this. Also, please read and follow our Import Guidelines - there is no link to the mandatory documentation.
osm.wiki/Import/Guidelines

Something went wrong here. All these objects have a strange "alt-piso" tag. You're also missing the mandatory documentation of the import.

Hi,
are you sure about this node? It's in a strange place and also has a strange tag.

Hi,
what do these areas represent? They don't have any tag describing what they are. If you want to import boundaries, please check the wiki for proper tagging and the import guidelines on how to prepare an import.

Hi,
you added the strange tag "UPDATEPOP=1" to 777 objects. Is this a mistake?

Please don't tag for your specific application. OSM only works if everybody uses the same set of tags. And if some tag is not supported by one application - just use one that already supports it, e.g. Waymarkedtrails.

Quite obviously no properly written tool. At the very least you (yourself!) have to (manually!) check that the tags created match those documented and in use in OSM.

You will very quickly find that 'duration' is never used with 'destination' and that numbers are never added directly after 'destination' and that 'ref' is never used to add the name of the destination.

The tags your artificial non-intelligence used will not show up in any application and therefore are useless.

Although the scheme Ivan linked is very common in Italy, I would recommend the "direction_north" scheme that is better suited to include also the directions the sign points to.

Hi,
you introduced several keys that are not used in any other place - could you explain what they mean? E.g.
sa_cuerpo = Cuerpo Buenos Aires
sa_division = División Perú
sa_territorio = SAW

Also: Please do not delete existing objects and replace them by new ones - instead please edit the old ones to keep their history.

It's not only this changeset but all 120 changesets...