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

From Wazeopedia


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.

The specific challenge addressed by this revision is to overcome a limitation of real time closures (RTCs) which impacts routing to destinations on cross-streets of main roads which are closed and don’t physically allow cross traffic at their intersections, due to events or construction.

In the image below, a long stretch of main road has been closed for a parade. Crossing the parade route is not allowed at the cross-street intersections. The driver is on one side of that parade, and the destination is on the other side. An ideal route would take the driver around the end of the parade route, to approach the destination from the side where it can actually be accessed.

Current wiki guidance is to close only one segment of the two-way cross street (in both traffic directions) on one side of the main closed route. This effectively prevents routing across the closed road in either direction, except in situations like that in the example above, where the destination is on the single closed cross street segment, and on the opposite side of the main closed road from the user. Waze will route the user to the nearer, incorrect, side of the closed route, unable to reach the destination.

Hawkeygoal 160620 Img01.jpg

If side-street segments are closed (both directions) on both sides of the main closed road, then the user will be navigated to the correct side of the main closed road for the destination. The purple route line, unfortunately, will end before entering the final destination segment, but this is a much smaller inconvenience than having to find one’s own way to the other side of a long closed route, such as a parade or marathon.

Hawkeygoal 160620 Img01.jpg

This RTC approach has been tested in real-life closure situations and found to yield superior routing results as compared to the previously recommended method.


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.

Waze will not route through a closed segment. It will, however, route up to the nearest end of a closed segment to reach a destination within it. Waze will also route out of the most convenient end of a closed segment if the user starts within it. 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 a destination on that segment in s-out direction. Closing both segments will prevent routing across the junction to reach a destination or leave a starting point, regardless of the user's position in relation to that junction.
  • Median segments of closed divided roadways
  • When both directions of a divided roadway are closed and cross traffic is disallowed, consider closing only the median segment.
When cross traffic between the lanes of a divided roadway is prohibited, closing the median segment will prevent routing to destinations on the fara side of the divided roadway. However, routes from s-in approaches to connected closed s-out segments may be possible. If this needs to be prohibited, consider closing the s-in segment as well.


Below is an example implementation for a New Year's Day parade in RTC Town.
RTC Town has scheduled a parade down Main St on January 1 starting at 13:00 and ending at 14:00. Traffic must not be allowed to travel along Main St or cross at any intersection. Hawkeygoal 160620 Img11.png
Select the parade route on Main St and set a two-way closure between 13:00 and 14:00 on January 1. Hawkeygoal 160620 Img11.png
Plum Rd is a two-way cross-street. To route traffic to the correct sides of Plum Rd, the segments north and south of Main St should be set with a closure between 13:00 and 14:00. Hawkeygoal 160620 Img11.png
Traffic flow on Orchard Rd is one-way southbound. To prevent routing drivers to the wrong side of the Main St closure, close the southbound segment north of the Main St junction (s-in) Hawkeygoal 160620 Img11.png
Similarly, Mulberry St is a northbound one-way street. To route drivers to the correct side of the parade, close the northbound (s-in) segment to the Main St junction. Hawkeygoal 160620 Img11.png
The completed set of closures in this example would look like those on the right. We’re all set to watch the parade! Hawkeygoal 160620 Img11.png

Now we look at a divided road closed for construction.
Willow St will be closed for two weeks for construction. So we set a closure for the length of both carriageways. Hawkeygoal 160620 Img11.png
Cherry Ave crosses Willow St in a ‘H’ intersection. In this case, we need only close the median segment to prevent traffic from being routed through, or to the wrong side of, the intersection. Note, we set no closures on Rose St because it is a T-intersection. Hawkeygoal 160620 Img11.png


This proposal is still being drafted prior to open discussion.