User:Hawkeygoal/Global Pages/RTC Cross Traffic(2016 06) View history

Revision as of 18:30, 30 June 2016 by Hawkeygoal (talk | contribs) (Amended text to clarify departing starting point will route off closed segment)

Overview

The goal of this page update is to provide guidance for editors relevant to lessons learned in handling real-time closures (RTC) and cross-traffic at junctions.

This information is a draft under development.
It should not be considered official guidance.

Content

Junctions and cross traffic

When adding a Real-Time Closure consider whether any cross traffic will be blocked as well.

Often in work zones and for special events (parades, 5K and 10K road races, marathons, half-marathons, festivals) cross traffic is not allowed at one or more junctions.

It has been observed that Waze will not route through a closed segment; however, it will route on to or off of a closed segment to reach a destination or leave a starting point on that segment. If traffic going across your Real-Time Closure must be blocked at a junction, you will need to close at least one of the cross street segments as well.

  • One-way cross street
  • Close the cross street s-in segment.
This prevents traffic from routing through the junction and onto closed s-out segments to reach a destination.
  • Two-way cross street
  • Close both cross street s-in segments in both directions.
Closing a single segment will allow routing across the junction to destinations on s-out segments. Closing both segments will prevent routing across the junction when to reach a destination or leave a starting point.
  • T-intersections
  • Close the cross street s-in segment in the direction approaching the junction.
This is necessary only to stop routing to destinations on s-out segments of the main closure.

[NOTE: Images need to be updated after text finalized]

Click on these illustrations to see them in full size.
1. 2. 3.

Discussion

This proposal is still being drafted prior to open discussion.