Hi,
this railway got a "vmaxspeed" tag which looks like a mistake. Could you check that?
way/100972611

Hi,
'outdoor_seating:weather_comfort' seems to be a strange tag. Did you mean "outdoor_seating:weather_protection"?

Hi,
"orig_name" is not a very common tag - can you specify when this name was in use? E.g. if it was used in the 1800s, you could use a tag like "name:1800 = XYZ"

Hi,
welcome to OSM.
Please don't add private property items to OSM. Listing the equipment in peoples backyards is not really within the scope of OSM. These things shouldn't be tagged like we also don't tag names of people living in buildings or the number of cars they own.

Hi,
what exactly is this deaf phone service? A plain phone number doesn't seem very helpful if you're deaf. Is this for e.g. video chat?

Please check this road, something went wrong with the tags.

Hallo,
ein paar Anmerkungen:

- "operator3" Tags: es ist nicht üblich, einfach eine Zahl an ein Tag anzuhängen.
Es ist problemlos möglich, mehrere Einträge in ein einzelnes "operator" Tag zusammenzufügen mit Semikolon getrennt.
Wenn es wirklich getrennte Tags sein sollen, dann wäre "operator:3" mit Doppelpunkt die übliche Wahl.

- "start_date:Deu. Telekom": bitte verwende keine Leerzeichen in Keys. "start_date:operator:2" wäre die gängige Wahl.

- "Deu. Telekom" - in der Regel sollten keine Abkürzungen verwendet werden. Es sollte der ausgeschriebene oder offizielle Name sein, also "Deutsche Telekom AG" oder "Deutsche Telekom".

Please don't just dump nodes from Overture to OSM. Always check if the objects already exist, and remove tags that don't belong to OSM. And, don't add "sidewalk" tags to arbitrary paths. These are only for actual sidewalks along roads.

Alright. The tagging might not be perfect, but mixed shops are always difficult.

computer parts on sales can be tagged as
computer:parts=*
Or more general also as computer:sales

Please check this node, it got a strange "ABS" tag:
node/13508411050

I propose to revert these edits for now - than it's much easier to start over with a clean import.

Hi,
could you check your edits? You added the tag "rcn_région", but it should be the English spelling "rcn_region".

Hi,
are these actually 'natural = ridge' and not 'natural = cliff'?

Hi,
many of the 'special_needs', 'therapy' and education tags you added here are not used in any other places. Could you check for existing tags?

E.g. there are already some
https://taginfo.openstreetmap.org/keys/special_needs#similar
or the 'therapy' tags already exist with a `health_specialty` prefix.

Hi,
please don't dump data from some other source into the OSM database - the tagging must be corrected before uploading, and any imports must follow our import guidelines:
osm.wiki/Import/Guidelines

Hi,
"parking:for" is new.
But we already have customers=* which might be exactly what is needed here.

Thanks for the explanation! We don't have a defined "mail" tag, so I suggest to use conditional syntax here:

parking:right:access = no
parking:right:access:conditional = designated @ "mail service"

Mich stört das Tag nicht, widerspricht nur meinem Verständnis von "lane". Vielleicht sollte man da mal nachhaken, wie andere das verstehen damit es keine Konflikte bei der Interpretation gibt. Man muss sich ja noch nicht mal direkt auf das "width:lane" beziehen, sondern einfach fragen ob ein oder zwei Beispiele eher position=lane, street_side oder sidewalk sind.

Hi,
I tried my best to translate the tag "communication:hertzien" that was added a week ago.
E.g. wikipedia links "Transmission hertzienne" directly to "terrestrial television".
If I was mistaken, please feel free to correct it.

Hallo,
hier sind wieder "@id = node/57629868" Tags in den Daten, die sollte es nicht geben.

Außerdem: Bitte verwende keine keys wie "Hafas_ID" - Referenznummer sollten immer in der Form von "ref:XYZ" erfasst werden, z.b. als ref:hafas.