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, footway=crossing, or cycleway=crossing
Useful combination
highway=crossing footway=crossing cycleway=crossing crossing:markings=*
See also
crossing=traffic_signals highway=traffic_signals
Status: in use
crossing:signals=* More details at taginfo 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

This key indicates whether a pedestrian, bicycle, or equestrian crossing is controlled by a traffic signal. It is intended as a replacement for crossing=traffic_signals, making it possible to simultaneously indicate whether a crossing is marked and whether it is signalized. This combination is especially relevant in some regions where unmarked, signalized crossings and marked, unsignalized crossings are both common. See this proposal (and the updated 2022 edition Proposal:Crossing signalization) for more details.

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 to use in combination

• crossing=marked or unmarked – whether the crossing is marked on the roadway
• 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 kind of audio cues emitted by the pedestrian signals
• traffic_signals:vibration=* – whether a haptic vibration accompanies the pedestrian signals

Examples

• 

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

• 

  United States (Oregon):
  crossing=marked
  crossing:signals=no

• 

  United States (New Jersey):
  crossing=unmarked
  crossing:signals=yes

• 

  United States (New York):
  crossing=marked
  crossing:signals=yes

• 

  United States (Indiana):
  crossing=marked
  crossing:signals=yes
  (Pedestrians obey the main traffic signal; proposed to be tagged crossing:signals=shared.)

Country-specific information

In some countries, signalized crossings are reliably implemented in conjunction with marked crosswalks. However, in others, the presence of signals and the presence of road markings at a crossing are decoupled. Known countries where unmarked, signalized crossings may be found include the United States and Iran. This is a work in progress list, so if you have information about more countries where this combination can be found, you may add to this section.

Software support

Editors

Rapid's crossing presets have a Crossing Signals field. [1] StreetComplete asks if the pedestrian must wait for a traffic signal at the crossing. [2] OpenStop asks if the crossing is button-operated. [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
• crossing:light=* and crossing:bell=* for railroad level crossings
• 2019 proposal
• 2022 proposal – extends the key with more specific shared and separate values