User:Ulamm/Regulations and level design of crossings
This is a concept for a comprehensive use of the key crossing that ought to be used with nodes as well as with lines:
- As a node
on the crossing point of a cycleway-line (or footway-line , briddleway-line …) with a road-line (or railway track).
- highway=crossing
- + crossing=* *=wait (instead of uncontrolled) or *=priority or *=equal or *=Traffic_signals or *=zebra
- + further tags see below
- As a line
linking cycleways or footways on either side of a road or intersection, passing one ore more road-lines and perhaps tram tracks. Often several such lines have to be crossed without an island. If there is an island, the line may be cut there or not (if the conditions on both sides of the island are equal). Where the geometry of an intersection is complicated, the crossing ways must be drawn anyway. Even if such a crossing lane is passing only one roadline, it is less effort to describe this line than to set a an additional node.
- highway=cycleway or *=footway , *=briddleway …
- + crossing=*
- *=wait (instead of *=uncontrolled)
- *=priority (typical for the roadside cyclway of a major road crossing a smaller road)
- *=equal (also for priority to the right)
- *=traffic_signals
- + control=*
- *=buttons
- *=sensors
- *=buttons&sensors
- *=central
- special U.K. types of signalized crossings
- *=zebra (including the Polish & Austrian type of privileged bicycle crossings)
- + marked=*
- *=yes
- *=no (not necessary with crossing=traffic_signals or crossing=zebra)
- + sight=* (for crossings without signalization)
- *=good
- *=limited
- *=bad
- + slopes=*
- *=no (optimal value)
- *=little
- *=medium
- *=steep
- + curbs=* or if necessary curbs:acute_angled=* (never with the value "no")
- *=no (optimal value)
- *=2 cm (or another height)
- *=round_sills (typically 5 cm or higher)
- *=full_curb (worst case)
- *=sinus_curb (a relatively comfortable one)
- another local standard type
- + surface=* (to be used especially, where it differs from neighbouring both cycletrack and carriageway surfaces)
The functional subkeys need no subkey layout as the type of node or line and their meaning is defined by the presence of crossing=*.
These tags shuold be available. That does not mean that every crossing must be tagged perfectly.