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.

Hi,
could you check the destinations you added recently? You used a "direction" tag instead of the common "destination".

And: If you have a "direction:forward", then the "forward" suffix also needs to be on the other tags like "direction:colour:text:forward"

'cocktails' is the older and much more common tag (10 times more)
osm.wiki/Key%3Acocktails

Hi,
the 'description' tag is fine (although nobody used 'description:subject' before, but 'subject:description' is used a dozen times and might be a better choice)

I referred to the 5 translated "person:job" tags (also used nowhere else).

- in general, translations should not be tagged - simple things like this can be translated automatically very well
- "job" is a rather modern word, something like "profession" seems to be a better fit for a person with a memorial.
- I'd prefer this kind of information within the description and not with its own tag - it's very unlikely that there will be more than a few of these around the world.
- In general we should have a wikidata or wikipedia link for the subjects where all information can be retrieved easily

Hi,
could you check this way, it got a strange gtfs tag:
way/684101528

Hallo,
was soll denn "disused:conditional = designated" bedeuten?

Hier der zweite Link:
destination=*#Further_details

Das ":to" kommt immer ans Ende des Subkeys.

Das Schema ist ganz einfach, und konsistent über fast alle Tags, deswegen kannst du es auch aus dem generellen Schema ableiten:
osm.wiki/Order_of_key_parts

Es gibt seit Januar 2023 keine einzige funktionierende Telekom-Telefonzelle mehr.
Die Tags die stehengelassen worden waren beschreiben das Objekt wie es jetzt da ist gut.

Bitte schau nochmal nach deinen destination-Tags. "lanes" und "forward/backward" kommen immer hinter alles andere.
Ich korrigiere im Moment fast täglich das eine oder andere Tag.

Hallo,
die Details an einem seit Jahren nicht mehr verwendeten Telefon, das auch nie wieder in Betrieb gehen wird, können wohl wirklich bedenkenlos gelöscht werden und brauchen nicht wieder hinzugefügt zu werden.

Hi,
you used some uncommon tags on guideposts here. Could you have a look to the very common direction_north etc. tags?
direction_north=*

Hi,

"road_marking = GB:1043" is in widespread use (850 uses!) and wasn't actually deprecated by the latest changes to the tag.
There was no new tag introduced to hold the code of the marking and IMHO
traffic_sign = GB:1043 would be appropriate on objects like these.