Hawkeygoal (talk | contribs) (More s-out replacements) |
Hawkeygoal (talk | contribs) (Graphics added) |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
| This information is a draft under development.<br>It should not be considered official guidance. | | This information is a draft under development.<br>It should not be considered official guidance. | ||
|} | |} | ||
''A specific challenge addressed by this revision is the routing to a destination on a closed segment from the far side of a adjacent thru-closure. For example, rather than routing to the destination from Whitworth the route suggest approaches from other side of a closure necessitating either manually navigating to the far side or crossing a closed intersection. | |||
[[File:Hawkeygoal 160620 Img01.jpg|300x300px|framed|center]] | |||
== Content == | == Content == | ||
| Line 14: | Line 16: | ||
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. | 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 | 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 | :* One-way cross street | ||
::* Close the cross street s-in segment. | ::* Close the cross street s-in segment. | ||
| Line 20: | Line 22: | ||
:* Two-way cross street | :* Two-way cross street | ||
::* Close both cross street s-in segments in both directions. | ::* 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 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 | :* T-intersections | ||
::* Close the cross street s-in segment in the direction approaching the junction. | ::* 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.'' | :::''This is necessary only to stop routing to destinations on s-out segments of the main closure.'' | ||
{{red|''[NOTE: Images need to be updated]''}} | <!-- | ||
{{red|''[NOTE: Images need to be updated after text finalized]''}} | |||
<center>''Click on these illustrations to see them in full size.<br /> | <center>''Click on these illustrations to see them in full size.<br /> | ||
<sup>''1.''</sup> [[File:Closure cross streets 1.png|150px]] <sup>''2.''</sup> [[File:Closure cross streets 2.png|150px]] <sup>''3.''</sup> [[File:Closure cross streets 3.png|150px]]</center>{{clear}} | <sup>''1.''</sup> [[File:Closure cross streets 1.png|150px]] <sup>''2.''</sup> [[File:Closure cross streets 2.png|150px]] <sup>''3.''</sup> [[File:Closure cross streets 3.png|150px]]</center>{{clear}} | ||
--> | |||
<center> | |||
{|style="margin:0; cellpadding:0; text-align:center;" | |||
| colspan=4 | ''Click on these illustrations to see them in full size.'' | |||
|- | |||
| [[File:hawkeygoal 160620 Img11.png|thumb|100px]] | |||
| [[File:hawkeygoal 160620 Img12.png|thumb|100px]] | |||
| [[File:hawkeygoal 160620 Img13.png|thumb|100px]] | |||
| [[File:hawkeygoal 160620 Img14.png|thumb|100px]] | |||
|} | |||
</center> | |||
== Discussion == | == Discussion == | ||
Latest revision as of 19:45, 1 July 2016
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. |
A specific challenge addressed by this revision is the routing to a destination on a closed segment from the far side of a adjacent thru-closure. For example, rather than routing to the destination from Whitworth the route suggest approaches from other side of a closure necessitating either manually navigating to the far side or crossing a closed intersection.
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.
| Click on these illustrations to see them in full size. | |||
 |
 |
 |
 |
Discussion
This proposal is still being drafted prior to open discussion.