|Further refinement for nodes already tagged with highway=crossing or railway=crossing|
|Used on these elements|
|Tools for this tag|
This tag is used for more accurately describing specific types of pedestrian crossings across roads, and other types of crossing over road or rail. Crossing infrastructure for the convenience of pedestrians, cyclists etc. should first be tagged with highway=crossing or railway=crossing as appropriate. The specific type of crossing may be further specified with the crossing=* tag and other properties described below.
The tag is set for the node where the both ways are crossing (footway and street, street and railway and so on). For detailed mapping it may be useful to tag ways leading from a sidewalk to the crossing node with footway=crossing or cycleway=crossing as appropriate.
The crossing tag
- Position this tag where the crossing-traffic (pedestrian, bicycles) have their own traffic lights.
- Mostly near highway=traffic_signals.
- Pedestrian traffic (Pelican/Toucan/Pegasus) with sound for the visually impaired.
- Pedestrian traffic signals (Pelican/Toucan/Pegasus) with vibration for the visually impaired.
- A generic crossing with no traffic-signals of any type, just road markings; e.g., zebra-crossings. Generally referred to as a "crosswalk" in the US).
- Mostly in combination with highway=crossing.
- Where definitely no crossing is possible/legal. This tag must be used without a highway=crossing, so data consumers only evaluating the high-level highway tag are not mislead into assuming a crossing here.
As crossing=no excludes the existence of a crossing, the combination of highway=crossing and crossing=no is invalid.
Thus, if there is a place where one would expect a crossing but where is definitely no crossing, you may tag this with crossing=no but without highway=crossing.
- A crossing without road markings or traffic lights
- A crossing with a small traffic-island for pedestrians in the middle of the road. Note that this tag is highly confusing, as it is orthogonal to traffic_signals/uncontrolled/unmarked classification. Tagging highway=crossing with crossing=island makes impossible to distinguish between crossing=traffic_signals and crossing=uncontrolled. For this reason many editors do not use this tag and some consider it as a broken tagging scheme. Alternatively, crossing:island=yes can be used in addition to crossing=traffic_signals/uncontrolled/unmarked.
- Mostly in combination with highway=crossing, it would be very unusual for this feature to appear on railway=crossing.
- A value of
yesmeans that pedal cyclists are permitted to ride across the crossing.
- A value of
yesmeans that horse riders are permitted to ride across the crossing.
- Green light on a traffic signal can be requested by a bicycle rider or pedestrian by button press.
- Like many others, this parameter is Boolean , i. e. it can take the values "yes" or "no". Different from several other Boolean parameters, in this case no default is assumed. A value of
yesindicates that crossing traffic of differing types is segregated from each other (there is a separate crossing area for each mode of transport). At many traffic lights, crossing foot and bicycle traffic are segregated. A more regional example is the segregation of horse and foot traffic within some UK Pegasus Crossings.
- This is a Boolean parameter, too. But there is the default
no. A value of
yesindicates that the crossing may be managed by a crossing guard at busy times.
- The traditional, region-specific reference, such as
- To indicate whether a wheelchair can pass the crossing.
- Tag on the node representing the kerb (en_US: curb) on the highway=footway for each side of the crossing. Add the footway as single way where needed. (Consider using kerb=* instead as it is a more general purpose method. Add your input to the relevant talk pages.)
- To indicate whether there is a pattern in the ground to aid the blind.
- Tag on the node representing the kerb (en_US: curb) on the highway=footway. Add the footway as single way where needed.
- (default is
no) A value of
yesindicates that flashing lights warn drivers when a pedestrian is crossing. For more detail, consider using a value of
sensor(if the lights turn on automatically), or
always(if the lights are constantly flashing).
The following table shows how the crossing might be tagged:
|Name and description||Tags|| Shortcuts
(crossing=* and crossing_ref=* combined)
| Zebra crossing
| Pelican crossing (traditional British name)
| Tiger crossing
| Toucan crossing (traditional British name, like "two-can")
| Pegasus crossing (traditional British name)
|An unmarked crossing with sloped curbs.||highway=crossing|
|A crossing with a traffic island (implicit mapping with a property or explicitly to mark a footway or similar on a traffic island crossing).||highway=crossing|
| A supervised crossing (additional property)
| Traffic signals without a pedestrian crossing.
Tagging crossings as ways
Some mappers tag a way segment of a highway=footway or highway=cycleway that crosses multiple roads and/or railways with crossing=traffic_signals to indicate that there is only one traffic light controlling the cyclist or pedestrian, to avoid multiple nodes being tagged as crossings.
Disadvantage: Please note that this mapping style makes it difficult for routers and navigation systems to recognise that there is a crossing for pedestrians or cyclists along the road, since there is no special crossing node on the route being evaluated.
- Approved features/Road crossings - the original proposal for this tag
- Cycle routes - closely linked with many toucan crossings
- Proposed features/Traffic_island
- Pedestrian_crossing (wikipedia) - international differences and terminology