You and your colleagues introduced new tags here:

maxheight trimble
maxheighttribble
maxheighttrimble
maxweighttrimble
hgvtrimble

Please explain what all these tags mean.

You and your colleagues introduced new tags here:

maxheight trimble
maxheighttribble
maxheighttrimble
maxweighttrimble
hgvtrimble

Please explain what all these tags mean.

You and your colleagues introduced new tags here:

maxheight trimble
maxheighttribble
maxheighttrimble
maxweighttrimble
hgvtrimble

Please explain what all these tags mean.

Hi & welcome to OSM!

You added several tags here that are not used in any other place. 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.

Regarding accessibility of toilets, there's already a large set of tags in use

Ups, danke fürs korrigieren. Ich habe gerade noch die beiden anderen "protected_title" in der Datenbank korrigiert, dann taucht der Fehler auch wieder in der QA auf wenn er wieder passiert.

Hi,
please watch out for the correct keys: The key is "maxspeed:bus:backward", not "maxspeed:backward:bus": First the vehicle, then the direction.
I just corrected a couple of them.

Hi,
could you check your recycling tags on this node? node/11207390973
There's a list in the wiki with the usual tags, but several of the ones you used here are not used in any other place.

PS: I'm not sure if I caught all problematic changesets - please have a look if there is anything else. You can usually notice these objects by their @id tag - but I see that you already removed many of them.

Hi,
I had to revert this and two more changesets of yours. All the objects uploaded are duplicates of existing ones.

This happens if you load a geojson or similar file into JOSM and then try to upload it. You have to load data directly from the API or Overpass - every other way will lead to duplicates and not to editing the already existing objects.

Could you check these ways, "difficult_alpine_hiking" is not a common tag.

To get other users to recognize and use the tags, they need to know about them. I'd suggest to write a post in the community forum and ask for some feedback. Then the tag should be documented in the Wiki. It's a minor addition without side effects, so there doesn't need to be a full proposal and voting about it.

The application maintainers usually don't monitor OSM closely enough to find the new tag, so your best bet is to contact them directly in their preferred way of reporting issues for new features.

Thanks for the explanation. In this case i suggest to use
traffic_signals:sound:radio_operated
This would use the same scheme as the existing traffic_signals:sound:button_operated

Hi,
you introduced 3 new Tags:

traffic_signal:soundondemand
traffic_signals:sound_on_demand
traffice_signals:soundondemand

There's a tag already used a few times: "traffic_signals:sound:button_operated"
This should fit your purpose without introducing a new tag.

Hi,
you added 4 nodes with a "DUPLIKAT" tag like this one:
node/11161372880

Could you check that?

Hi,
please check the parking tags you added, e.g. "parking:side:fee:conditional". There's shouldn't be "side" in the key, it has to be replaced by left/right/both.

Hallo,
du hast hier das neue Tag "arrow:symbol" verwendet. Auch wenn es sich hier um route_marker und keine guideposts handelt, würde ich vorschlagen, die dort üblichen Tags zu verwenden. Also entweder "destination:symbol" oder einfach nur "symbol". Alternativ könnte man auch "osmc:symbol" verwenden, allerdings gibt es da bis jetzt kein Bahnhofs-Symbol.

Hallo,
du hast hier viele neue Radwege eingetragen - allerdings waren viele davon schon vorher erfasst mit "cycleway" Tags an den Straßen. Beides zusammen ist leider nicht richtig und führt jetzt dazu, dass es an vielen Stellen zwei Radwege zu geben scheint, wo tatsächlich nur einer existiert. Hier müsste noch deutlich nachgearbeitet werden, damit die Daten wieder mit der Wirklichkeit übereinstimmen.

Hi,
please explain the new tag "hgvtrimble". This is not documented and not used in any other place.

Please check these nodes. They all got a HOVEDGRUPPE tag that looks like it shouldn't be in OSM.

And: what is the source of this data "Norway Orthophoto" can't be right.

Hi,
please check the buildings you added here - there are many with strange tags like
building_c
building_l
building_m
building_s
capacity_p