No, not yet. I would wait a few days for a response first.

I reverted this changeset.

I reverted this changeset.

Hallo,
hier stimmt mit dem 'motor_vehicle' tag etwas nicht.
way/311809767

You can use the example section in the proposal to demonstrate them.

Symbols are mostly a defined set of officially defined icons, these can easily be mapped to a single value of the symbol tag.
Many symbols don't have a direct equivalent in OSM main tags. There's one symbol for a place to eat - and it might refer to amenity = fast_food, restaurant, cafe, ... should all of these be tagged differently?

indication:* is different - marker signs always refers directly to an actual object in OSM.

destination:access:* is also different: The tags are referenced in the destination:symbol tag, so any software exactly knows what to look for.

Please don't try to discuss everything in changeset comments, start a thread in the forums.

Please don't simply upload data from other sources into OSM. All these objects have many tags that shouldn't be there. The source of the data and the mandatory import documentation is missing as well. Please have a look at our import guidelines:
osm.wiki/Import/Guidelines

Something went quite wrong here. It seems that most of these roads are duplicates of ones that already exist in OSM.

Something went quite wrong here. It seems that most of these roads are duplicates of ones that already exist in OSM.

Please ask for comments before using any of this. The proposal is a mess of hundreds of tags instead of one simple one. There's no way to make any use of that data without thousands of lines of code and months of work. A symbol on a destination sign is not an aeroway or amenity.

Hi,
"parking:entrance:conditional" is not common - may I suggest to instead use access tags on the access way / access barrier?

opening_hours = 06:00-22:00 || 24/7 "exit only"

or

access:forward:conditional = no @ 22:00-06:00

I suggest to use the "direction_north" syntax here, e.g.

direction_southeast:symbol=shoe
direction_southeast:colour=red

You could also use osmc:symbol, but there is no (not yet) symbol for a shoe / sole.

I didn't check them in great detail - let me know if I can help somehow.

Hi,
please check these routes:

- "ref= publictechstudio=124" looks like a mistake

- "seasonal:disruption =yes" is a new tag. If the route only operates during specific months, this should be added to the opening hours

- your opening_hour tags don't mean what you think they mean, times don't add up if you use semicolons, e.g.
https://openingh.openstreetmap.de/evaluation_tool/?EXP=Mo%2CTu%2CWe%2CTh%2CFr%2CSa+07%3A00-10%3A00%3B+Mo%2CTu%2CWe%2CTh%2CFr%2CSa+10%3A00-16%3A00%3B+Mo%2CTu%2CWe%2CTh%2CFr%2CSa+16%3A00-18%3A30%3B+Mo%2CTu%2CWe%2CTh%2CFr%2CSa+07%3A00-10%3A00%3B+Mo%2CTu%2CWe%2CTh%2CFr%2CSa+10%3A00-16%3A00%3B+Mo%2CTu%2CWe%2CTh%2CFr%2CSa+16%3A00-18%3A30&lat=48.7769&lon=9.1844&mode=0&DATE=1777715256030

Hi,
you added the tag "id_fcu" here. Reference numbers of objects are usually tagged as "ref:fcu" or "ref:FR:fcu". Could you check / fix that?

Please check this import.

- there is a strange "date_der_maj" tag
- some addresses now appear twice
- JOSM gives many warnings about nodes in identical positions
- the position of nodes is mostly on roads, but not on buildings / borders of lots

Das Tag "operator" steht nicht nur spezifisch an Dingen die im Deutschen das Verb "betreiben" haben, sondern steht ganz allgemein für denjeningen, der für ein Objekt zuständig ist.

Der Operator der Anlage ist der Turmbetreiber, der Betreiber der Kommunikations-Infrastruktur ist das TK-Unternehmen. Genau das bilden operator und communication:operator ab.

Hi,
"ref_direction" is a new key. Could you explain what it means?

Hi,
could you check your maxspeed tags? They should read
"maxspeed:hgv:forward" instead of "maxspeed:forward:hgv". I.e. the type of vehicle comes before the direction on the road.

Thanks!

Die Verwendung ist nicht hoch, aber seit vielen Jahren immer mal wieder. Vor einer Weile habe ich die Verwendung hier zumindest erwähnt:
communication:=**

operator=Funkturmbetreiber
communication:operator=Belekom;Vorderfon;P3

Eine Unterscheidung der Betreiber nach Kommunikationsarten, z.B. gsm und lte ist mir bis jetzt nicht geläufig, würde aber mit "communication:lte:operator=X;Y" funktionieren

Aus diesem Grund wurde "communication:operator" erfunden, um genau diese Unterscheidung zu haben.