Hi,
you added a strange 'addr:streu' tag here - could you check that?

Hi,
this lake got a strange 'OSM_name' tag:
relation/6319672

Hallo,
bitte schau nochmal in die Doku der parking-Tags.
"parking:lane:parallel" lässt sich nicht ersetzen durch "parking:parallel"

These multiple nodes on the same spot are not correct. There should be exactly one 'amenity=charging_station' for each group, or individual nodes with 'man_made=charge_point'. Everything else is not according to approved tagging schemes.

E.g. this one:
node/11253014523

In this location there seem to be 3 charge_points with two connectors each. But what is mapped is 2 independent carging_stations with a total capacity of 6 cars at once.

Please stop this import, revert the edits and restart planning of how your data can be mapped to proper OSM objects.

The type_2 typo currently exists 575 times, mostly added in the last 24 hours.

IMHO The multiple nodes and output values are something to be fixed before import and not edited afterwards

See the previous comments:

- type_2_combo -> type2_combo
- socket:X=yes -> socket:X=NUMBER
- socket:max:output -> output
- 6 or more nodes on the same spot

Please stop importing these nodes until all the tagging errors have been fixed (see changeset comments from last week). The mistakes now spread across the whole world...

Hi,
you added 'ELVIS' tags to several rivers. Shouldn't that be the 'name' tag?

Hi,
could you explain the 'external_uri' tag you added on several objects? What does it mean?

Could you point us to the mandatory description and documentation of this import?

It seems that something went very wrong here. Some charging stations got imported 5 or 6 times!

Another thing: "socket:type2_combo=yes" is not correct, the value should be the number of sockets.

And yet another remark: What is the meaning of socket:max:output? This tag doesn't exist in any other place. The correct one would be either 'output' (for the total output) or 'socket:XXX:output' for the output of one socket.

Hi,
please check the ~500 objects you imported. There is a spelling mistake:
type_2_combo -> type2_combo.

Could you explain why all these "image:*" tags are there in the first place? They just seem to copy information that is already included in the mapillary link.

Hi,
welcome to OSM!
You used several strange tags here, like

is_in:evacuation = No
is_in:location = Marereni
is_in:prone = Partially

Could you explain what they mean?

Please use only tags that are described in the OSM Wiki or are available in the presets of your editor.
This is necessary to make sure that every other user can understand the data.

You can compare to e.g.
maxspeed:hgv
or
maxweight:agricultural

Here's a page in the Wiki that describes an order that matches most keys we have:
osm.wiki/w/index.php?title=Order_of_key_parts

But: Maybe "priority" isn't even the correct tag here? Wiki says it's to give priority to one direction of traffic. Maybe "priority_road" is better suited on the ways here?

Hi,
you used the new tag "bicycle:priority" here. As it's a tag describing priority, the common form of the key would be "priority:bicycle" - first the key, then the vehicle class is applies to. Could you consider changing that?

Welcome to OSM!

You added many tags here that are not used in any other place and don't match common tagging practices, e.g.:
Bathroom = yes
Braille Information Board = no
Child-Friendly Toilet = yes
Directional Signage = yes
Janitor's Room = yes
Napkin Disposal Machine = yes
Sanitary Napkin Dispensing Machine = yes
Tactile Pathways = no
Third Gender Toilet = yes
User-Friendly Payment Option = yes

Please use only tags that are described in the OSM Wiki or are available in the presets of your editor.
This is necessary to make sure that every other user can understand the data.

Hi,
please check the spelling of keys:
You added "addr:postecode" instead of "addr:postcode".

Hi,
please have a look to the Wiki to see how monitoring stations are typically mapped:
man_made=monitoring_station

These tags are also already in use:
monitoring:PM10=yes
monitoring:PM2.5=yes