Hi,
I found several tags with spelling mistakes. Please make sure that the spelling of all tags is correct - otherwise no software can understand them. Would you mind having a look and fix these issues? Example:
"roof: material" -> "roof:material"
... and several other, similar keys.

Thanks, Jan

Hi,
you're right, the tag is new, but correct. Would you mind adding it on the wiki page for sockets?
socket=*

Dafür gibt es dieses praktische Tool:
http://osmtools.de/traffic_signs/?signs=260,1026-38

Hallo,
"metal" als Oberbegriff (Aluminium ist ja auch ein Metall) ist durchaus gängig. Wenn du es genauer weißt, kannst du das gerne ändern. Das gleiche gibt es ja auch bei Tags wie "surface": "paved" als grobe Einordnung, das bei genauerer Kenntnis ersetzt wird durch z.B. "concrete".

"metal" ist allerdings etwa 100 Mal häufiger als Tag benutzt als "aluminium", was eventuell das eine oder andere Tool nicht interpretieren kann.

Hallo,
kannst du hier mal nach den maxspeed-Tags schauen? Da sind zwei sich widersprechende.
way/243274570

Hi,
you're using the key "traffic_signal" on many nodes, the correct key would be "traffic_sign".

Could you have a look and fix this?
Jan

Hi,
I saw that you added the tag "traffic_signal = E53c" on several nodes - the correct key is "traffic_sign". Could you have a look and fix this?

Thanks, Jan

Hallo,
dürfen hier wirklich nur Fußgänger, Radfahrer und Pferde durch? Keine forst/landwirtschaftlichen Fahrzeuge?
Jan

Hi,
these edits on ~100 stores look a lot like an edit for SEO.
You're introducing many new tags, don't add any source of the information.
Please spend some time to change all these POIs to use common tags like they are described in the Wiki.

Hi,
please watch out for the correct spelling of tags: it's "landcover", not "lancover".

Cheers, Jan

Hi,
tags like "fut_ref_1" are not common. You could use "proposed:ref = I-69;IN 37" instead.

Cheers, Jan

Hi,
please watch out for the spelling of tags - it's "highway", not "hidghway".

Jan

Hi,
please watch out for the spelling of tags - it's "highway", not 'hidhway'.

Cheers, Jan

Hi,
could you explain the tag "tm_data" you added on these nodes?
Thanks, Jan

Hi,
this looks like an import of at least 82 schools.
The source you give ("ESRI") is obviously wrong. Where can we find the obligatory description of this import?

Also, all these nodes have many strange tags which don't look like they belong in the OSM database like these:
Capacit�=-4.864
Date_mod=20/05/2018
Longitude=14.193
OBJECTID=3096
Province=Kongo Central
Source=UNICEF
type=school

Could you please check and fix these issues?

Could you please check this import? It created hundreds of areas with foreign tags, that don't look like they should appear in the OSM database, like the ones below.
commune=78117
contenance=6521
created=2007-02-21
id=78117000AK0068
numero=68
prefixe=000
section=AK
updated=2014-02-21

I also doubt that landuse=grass for these - this looks more like private gardens, a "landcover=grass" would be more appropriate.

Take the link "Privacy e note legali" and scroll to the last paragraph - the license is cc-by, which is an "open license", but not compatible to ODbL - we can't guarantee that the attribution is always kept along with the data.

Hi,
the cc-by license of this data is incompatible with ODbL. This data must not be used in OSM, unless you have a written permission to use it.

Hi,
could you explain the meaning of the tags route_id and shape_id ? These are not used on other bus routes.

Thanks, Jan

Hi,
you used the key "socket:typee" which looks like a mistake. Could you check what the right socket type is?

Jan