I just used the usual reference tool to check the results

https://openingh.openstreetmap.de/evaluation_tool/

Der ist durch einen teils 2 Meter breiten Grünstreifen mit Bäumen und kleinen Büschen bau(m)lich getrennt, kann also extra erfasst werden. Natürlich inklusive der Baumreihe, Grünstreifens und der diversen Durchgänge.

Ich sehe bei Mapillary nichts was ein "cycleway" Tag rechtfertigen würde. Nur zwei parallele Wege links und rechts der Bäume, von denen der äußere anscheinend ein sidewalk:bicycle=yes und sidewalk:bicycle:oneway = no bekommt.

Hi,
the tag "healthcare:psychotherapist" doesn't exist. It's either healthcare=psychotherapist, or "health_specialty:psychotherapy"

Hallo,
du hast hier das Tag "operator:signed = Post" ergänzt. Der Key "operator:signed" ist aber nur dafür da anzugeben, ob der Operator vor Ort ausgeschildert ist, nicht für den Namen.

Das gleiche gilt für "operator:signed:wikidata" - das wäre der Wikidata-Code für den Eintrag, ob es vor Ort ein Schild gibt, aber nicht der Eintrag für den Operator.

I managed to compress the opening hours into one tag by reusing the time spans common on each day :)

Do you have a link? All I can find is Bosch smart home equipment.

Hi,
could you check the sockets here?
node/13069836214

"bosch_smart" is not a common socket type.

Bitte überprüft hier die Gehwege - da sind einige Tags wie
sidewalk:right:cycleway die keinen Sinn ergeben.

Re 2) The same is true for the definition of a trunk in many countries. That means, a "highway:motorway" tag might be a too narrow scope.

I suggest to put this up for discussion in the (global, not US) forums, get some feedback, adapt the proposal if necessary. And only then, when there is some positive feedback I'd start adding the new tags on some objects.

Ja, so ist der "übliche" Weg.

Hi,
please don't use the "name:XX" tags to add transliterations and duplicates of the name of a village in 195 (!) different languages. The tag should be used only if there is an actual name in this language.

Hallo,
schau bitte nochmal über die Edits, 5 Wege haben nur fremde Tags die nicht in OSM gehören, z.B. way/1422893750

Hallo,
die Tags an einem "charge_point" sollten keinen "charge_point"-Präfix haben:
osm.wiki/DE:Tag:man_made%3Dcharge_point

Außerdem gibt es keinen "socket:ccs", das wird wahrscheinlich "socket:type2_combo" sein.

Nein, destination:ref:to:lanes:backward

Das ":to" gehört zum destination-Tag, deswegen muss es vor den generischen lanes/forward Endungen stehen.

So wie es im Wiki steht:
destination
[:hgv|:bicycle|...]
[:subkey]
[:to]
[:lang:XX]
[:lanes] [:forward|:backward|:both_ways]

You might want to finish the draft, announce it in the forums and ask for first feedback before doing a large scale edit on more than a thousand objects.
There might be some problem with road classification in your local area, but we already have many tags for classification. Adding a second highway tag to roads might not be the best solutiin.

Hi,
did this way got blocked due to the landslide? Then there should be some access tag on the way to mark it as unusable.

Hi,
you used 'communication:3GZB' and 'communication:4GZB' here. I can't find a definition for these. Could you help?

This is what happens if some software developer decides to add new tags without discussion and documentation.

"menu:url" was the tag used until a while ago (that is the tag in line with others like "opening_hours:url").
Then somebody forced the use of "website:menu" (which is technically wrong and against the definition of 'website' and 'url' tags in case of images or PDF) through a not well prepared tagging challenge.
And now mapcomplete introduced yet another tag. https://community.openstreetmap.org/t/adding-image-menu-on-resturants/120806
- problematic because of very unclear copyright situation
- opposed by half of the mappers participating in the discussion
- misusing panoramax street-level images as generic image hosting

Hi,
please have a look at this object, something went wrong with the tagging.