Key:crossing:signals

crossing:signals
Description
Indicates whether the crossing is controlled by a traffic signal.
Group: crossings
Used on these elements
Requires
highway=crossing or footway=crossing or cycleway=crossing
Useful combination
crossing:markings=*
See also
highway=traffic_signals crossing=traffic_signals
Status: in use
crossing:signals=* More details at taginfo
Tools for this tag
taginfo · AD · AT · BR · BY · CH · CN · CZ · DE · DK · FI · FR · GB · GR · HU · IN · IR · IT · LI · LU · JP · KP · KR · NL · PL · PT · RU · ES · AR · MX · CO · TW · UA · US · VN overpass-turbo OSM Tag History

The crossing:signals=* key indicates whether a pedestrian, bicycle, or equestrian crossing is controlled by a traffic signal.

Combined with crossing:markings=*, this allows for clear representation of all combinations of crossing markings and signals without relying on the older and often unclear crossing=* tag.

Values

• crossing:signals=yes – the crossing is controlled by a traffic signal, whether or not it has road markings
• crossing:signals=no – the crossing is not controlled by a traffic signal, whether or not it has road markings

Tags used in combination

• crossing:markings=* - the existence and style of crossing markings on the roadway
• button_operated=* – whether the pedestrian signals are operated by a call button
• traffic_signals:sound=* – the existence and type of audio cues emitted by the pedestrian signals
• traffic_signals:vibration=* – whether a haptic vibration accompanies the pedestrian signals
• traffic_signals:arrow=* - whether a tactile directional arrow is present

Examples

• 

  United States (Florida):
  crossing:signals=no
  crossing:markings=no

• 

  United States (Oregon):
  crossing:signals=no
  crossing:markings=zebra

• 

  United States (New Jersey):
  crossing:signals=yes
  crossing:markings=no

• 

  United States (New York):
  crossing:signals=yes
  crossing:markings=zebra

• 

  United States (Indiana):
  crossing:signals=* correct value unclear; location-dependent for whether pedestrians must obey the main traffic signal.
  crossing:markings=lines

Software support

Editors

• The JOSM Sidewalks plugin synchronizes crossing:signals=* between the way and node representations of a given crossing.
• OpenStop asks if the crossing is button-operated. [1]
• Rapid's crossing presets have a Crossing Signals field. [2]
• StreetComplete asks if the pedestrian must wait for a traffic signal at the crossing. [3]

Routers

• GraphHopper considers crossing:signals=yes to be synonymous with crossing=traffic_signals and crossing:markings=no crossing:signals=no to be synonymous with crossing=unmarked. [4]
• MOTIS Per Pedes Routing indicates whether the crossing is signalized [5][6][7] and can calculate a detour that avoids unmarked, unsignalized crossings. [8]

See also

• Crossings - main page for crossings
• Proposed features/crossing:signals - original 2019 proposal
• Proposed features/Crossing signalization – 2022 proposal which extends the key with more specific shared and separate values
• crossing:light=* and crossing:bell=* for railroad level crossings