Traffic sign: How to map an "arbitrary text"-exception? (Germany.)

Ahoj,

I here have a “no stopping” traffic sign in addition with a custom excemption: “DVB - Fahrzeuge frei”.

The traffic sign is located here and applies to this area.

How to map that?

  • For the traffic sign:
    traffic_sign=no_stopping;??? – what to enter for “???”?
  • For the area:
    restriction=no_stopping, restriction:conditional=??? – what to enter for “???”?

(Or completely different?)

See this photograph:

Regards!

It’s not an official sign of the StVO, so there is no sign ID it correlates with. However, there are several groups of exception-signs, one being called „ Zusatzzeichen 1028 – sonstige Fahrzeug-, Personengruppen frei“. So in theory, you could probably use traffic_sign=no_stopping,DE:1028[DVB-Fahrzeuge frei], because there is no corresponding sub-id for 1028. Or you just ignore it,or add it in a note=*, which is what I would do with these non-official signs.

2 Likes

Thanks; can you review the current tagging?:

I am unsure/ confused especially about what to do with the area.

Normally restriction relations would use except=* to record any exceptions to what’s in restriction=*, but this key doesn’t accompany restriction=* on ways. Instead, the street parking tagging scheme specifies parking:side:restriction:mode=none, where mode is the transport mode corresponding to the exception.

Does “DVB-Fahrzeuge” refer to buses operated by Dresdner Verkehrsbetriebe? We don’t have any established tagging for organization-specific exemptions to restrictions, but there are some other real-world examples of these exemptions that we might want to handle similarly:

I’ve tagged this restriction relation except:network=* and except:network:wikidata=* based on a sign that exempts specific bus route networks. However, the adjacent tram line has DVB as an operator=* rather than a network=*, so I guess it would be except:operator=* for a restriction relation and maybe something like restriction:conditional=none @ (operator=DVB) for this bus pad.

No.

Service vehicles.

This is too small to be used for buses.

What does the italic print of side and mode mean here? (And how could you add italic letters in the inlinecode at all? When I do the markdown

`parking:*side*:restruction:*mode*=none`

the * do get printed verbatim and are not interpreted to switch to italic.)

They are placeholders to be replaced by left, right etc - you wouldn’t actually use the words side or mode in tagging.

Ah, in that case, maybe we could treat it as a private service road, using private=maintenance and operator=* to clarify the intended road users. That’s similar to what I did for airport maintenance roads.

I was quoting from the street parking tagging scheme, which uses side subkeys to distinguish between the left and right sides of the street and mode subkeys to distinguish among different transport modes, similar to how we use access keys for ordinary access restrictions. The side isn’t relevant for the area that you’ve mapped, but the mode could be relevant if you think there’s a distinction between DVB maintenance vehicles and DVB maintenance… bicycles or something.

I had to switch to HTML to nest italics inside inline code:

<code>parking:<i>side</i>:restriction:<i>mode</i>=none</code>

Very annoying to type on a phone.

But general access is not forbidden by a sign (although it is useless), only stopping is forbidden.


[Off-Topic: Formatting help]

Many thanks for this knowledge!

Understood, the street parking scheme reuses the private=* key in a manner that suggests you could tag parking:access=prívate parking:private=maintenance or something like that. I think the assumption would be a no stopping restriction for everyone who isn’t able to park there, but I’m a little uncertain about that.

1 Like