Railway Crossing Alerts: Difference between revisions View history

(Removed confusing wording that I added that adds no value)
No edit summary
Line 7: Line 7:
*Railway crossing alerts '''should be manually locked to level 3''' after creation.
*Railway crossing alerts '''should be manually locked to level 3''' after creation.
*Initially, mapping of railway crossing alerts should focus on higher road types such as highways and primary streets.
*Initially, mapping of railway crossing alerts should focus on higher road types such as highways and primary streets.
Add Rail Crossing Alerts to These
<gallery>
Arxa01.png|Rail Crossing Without Boom Gates
Arxa01.png|Rail Crossing With Static Signage
</gallery>
Do Not Add Rail Crossing Alerts to These
<gallery>
Urxa01.png|Rail Crossing With Boom Gates
Urxa02.png|Light Rail Crossing
Urxa03.png|Tram Crossing
</gallery>

Revision as of 01:33, 8 December 2020

A new feature introduced April 2020, to provide an audible and visual alert when approaching a railway crossing. The feature was designed for partners in the United States, but all countries had access to it. Below are the guidelines for implementation in Australia - note they differ from other countries.

  • Railway crossing alerts in Australia should only be added for railway crossings without boom gates.
  • Further, they should not be added for tram or light rail crossings, due to their high risk of creating map clutter and alert fatigue in dense areas.
  • They should be placed close to the actual rail lines, and aligned in the same way as speed/red light camera - facing the direction of travel for the alert.
  • A separate railway crossing alert is needed for each direction.
  • Railway crossing alerts should be manually locked to level 3 after creation.
  • Initially, mapping of railway crossing alerts should focus on higher road types such as highways and primary streets.


Add Rail Crossing Alerts to These

Do Not Add Rail Crossing Alerts to These