Hallo nochmal,
an anderer Stelle hast du jetzt nochmal direction_*:routes verwendet. Das finde ich für die vollen Namen auch völlig in Ordnung, aber könnten wir uns auf den Singular "route" einigen? Das ist bei den meisten Tags ja so üblich, auch wenn es mehrere Einträge gibt.

You can search for tags like here:
http://overpass-turbo.eu/s/1zcW

Seems that there are none left at the moment.

There's no good solution for this that is also widely supported.
Some people try to put lists in the direction tag like direction=90;90;270 and traffic_sign = maxspeed;speed_camera;maxspeed.
Others use traffic_sign:forward and :backward - but if the node is not connected to a road this can't be evaluated easily.

It seems to be better to keep two nodes like you did.

Hi,
you introduce a couple new tags here, which already exist in another form used with hotels, e.g.

service:breakfast -> breakfast
service:laundry -> laundry_service
service:gym -> fitness_centre

Would you mind changing these to the common tags?

Das Tagging mit direction_* ist natürlich etwas eingeschränkter als z.B. mit destination_sign Relationen. Dort könnte man ganz einfach eine Relation mit Routen und eine mit Zielen anlegen. Oder auch den Knoten in die Routenrelationen mit aufnehmen mit der Rolle destination_sign.

"Dormagen via Fähre" vs "Dormagen (ferry)" - da würde ich definitiv die erste Version bevorzugen. Ein englischer Begriff ist da verwirrend und würde z.B. beim Vorlesen am Navi auch nicht richtig ausgesprochen werden.

Hi,
please check the spelling of the keys you add. I'm fixing spelling mistakes in the keys of Monoglian names almost every day!, e.g. at_name -> alt_name, mn_mong -> mn-Mong etc.

Und: "direction_north:symbol" wird schon verwendet und wäre sicher die bessere Wahl anstelle von "(ferry)" neben der Richtungsangabe.

Hallo,
spricht etwas dagegen "direction_north:ref" zu verwenden anstelle von "...:route"? Dieses Tag ist zwar auch noch nicht in Benutzung, aber es würde zu anderen Tags passen, z.B. destination:ref.

Hi,
you added a strange "souce ID" tag to three nodes, could you check that?

Hi,
are there two traffic signs on this node?
node/11117712880
You can combine them in one tag: traffic_sign = maxspeed;speed_camera

Hi,
what's the meaning of "motor_vehicle:bus = none"? This tag is not used anywhere else.

Reminder: Please stop adding your own, private tags and read and respond to the comments you received.

Hi,
please check these hydrants, they got strange tags like "ПГ-71 = К-250".

Hi,could you check this node?
node/4591949018

There's a "name:ja-" key. Should that be name:ja_kana?

Hi,
please check the objects you added here - they look like buildings but don't have a 'building=*' tag.

And: Please write useful changeset comments, describing what you edited.

Something went wrong here. You added 35000 buildings with tags that shouldn't be in OSM like these:
GPO_Unique = 059_7715
SourceID = 465700

The changeset is missing a link to the documentation of this import as mandated by
osm.wiki/Import/Guidelines

Hi,
please don't add tags like these to OSM - project specific data needs to be kept in a separate place but not in the main OSM database.

Hi,
please check your tags. It's 'operator', not 'operetor'.
It should be enough to have these tags on the whole amenity=parking area and not on every individual parking space.

Hi,
many of the buildings you added have strange tags like FID or verificado.
Please make sure you only use tags that are documented or available as presets in your editor.

I also see that there are many buildings overlapping with other buildings or streets. This should give you warnings and errors in JOSM before uploading - please make sure you fix all these issues before uploading them.

Hi,
could you explain the meaning of "Ramal = 2-7"? This tag is not used in any other place.