Get a sneak peek at whats next for Permanent Hazards on our April 7th Office Hours!

Post Reply

[NEW] Guidance for turn instruction overrides

Post by
The following is a draft started by subs5 & nzhan1. I am posting it to get a draft in front of wiki folks quickly because the feature is live in WME Prod and we're behind.

The initial draft is simply a documentation of the feature. We need to add specific guidance on when to use them. And when they can take the place of a wayfinder and when they cannot.

There is also no formatting set in this draft.
--

Creating an Override Instructions
wme_turn_override_hover2.png
When in WME and you click on a segment and hover over a Green or Yellow Turn Connection/Restriction Arrow, both the Time Based Turn Restriction (TBTR) clock AND the Turn instruction Override speaker icon will appear. If the turn is Red (restricted), then the override icon will not appear.

Available Override Instructions
When you click on the '''Speaker", you have the following choices:
wme_turn_override_list.png
  • Waze Selected (this gives the default voice prompt turn, exit, keep right/left, etc)
  • None (No verbal instruction/recommendation is given)
  • Turn Left (The instruction/recommendation "Turn Left" is given)
  • Turn Right (The instruction/recommendation "Turn Right" is given)
  • Keep Left (The instruction/recommendation "Keep Left" is given)
  • Keep Right (The instruction/recommendation "Keep Right" is given)
  • Continue (Not available as of 2016-12)
  • Exit Left (The instruction/recommendation "Exit Left" is given)
  • Exit Right (The instruction/recommendation "Exit Right" is given)
  • Uturn (The instruction/recommendation "Uturn" is given)
If there is a selection other than the default "Waze Selected" then the circle around the speaker changes color from https://wiki.waze.com/wiki/images/6/62/ ... r_icon.png (Cyan) to https://wiki.waze.com/wiki/images/2/26/ ... active.png (Orange).

When to Use Override Instructions

Exit Left
When there is a the Big Green Sign (BGS) indicating an exit left.
Discuss with your Regional Coordinator(s) and/or State Manager(s) to see if they want it added to locations where a HOV or HOT/Express Lane is separated from the regular freeway, highway, etc.
https://wiki.waze.com/wiki/images/6/6b/ ... _hover.png

U-turn
This works well for one way segments that have a u-turn only lane. You can post a "u-turn" verbal prompt on the first left turn and "None" on the second one.

Streets not meeting at right angles
When streets meet at some kind of diagonal, the default turn instruction may end up being a "stay to the left/right" even though the driver would consider it a left or right turn. In these cases, we have historically modified the angles the roads meet at a very high zoom level:
https://wiki.waze.com/wiki/images/e/ef/ ... al_fix.png https://wiki.waze.com/wiki/images/3/37/ ... rriden.png

Simple Wayfinder
Simple wayfinders use an unnamed segment simply to force an instruction where one would normally be voiced. This is most often a "stay right" or "stay left." A basic example is a roadway with a split where left lanes go left and right lanes go straight ahead. To ensure the driver is kept on the correct side of the roadway to stay on the expected route, we create a wayfinder on the "straight" segment to force a "stay to the right instruction."

An example of this is shown below. The selected segment is unnamed, and you can see the name of the street on both sides of the wayfinder are the extact same name. For drivers heading the direction of the arrow, the unnamed segment forces the app to give the driver the instruction "stay to the right to El Cajon Blvd."

https://wiki.waze.com/wiki/images/3/3d/ ... xample.png

The guidance here is to remove (or rename and join) the unnamed segment, and replace it with a "keep right" turn instruction override.

Complex Wayfinder
A complex wayfinder is one where the legs (child segments) are named differently than the subsequent segments. The wayfinder segments are named for the Big Green Sign (BGS) verbiage for clarity.

For these kinds of wayfinders, a turn instruction override does not have the required functionality and should not be used.

POSTER_ID:701618

1

Send a message

Post by Inactive user -1649923503-
PleaseDriveFast wrote: I think it's a good start. After reading it, I'm beginning to wonder if we need to be more explicit that this should be replacing mDLs where possible or if the override should only be used in exceptions. Can we get clarity on which is preferred or is that another can of worms to discuss?
Sent from my iPhone using Tapatalk
I think we are looking at a whole retraining of editors on how to design an intersection potentially and further challenges if TIO is rank locked on how best to proceed.
Inactive user -1649923503-
Posts: 1023
Has thanked: 404 times
Been thanked: 460 times
Send a message
-John
-------
https://j.mp/1BqcgbWhttps://s.waze.tools/c5.png
VT - State Manager
New England - Multi State Manager

Post by Inactive user -1649923503-
I don't think people are advocating for a rush to change things. I think it is important to ensure new edits going forward are utilizing this feature over our historic alt name or road to nowhere hacks. And to think about the longer term plan.

It is also important to think how this will impact the next generation of of editors training and learning. All of the sudden we have a tool that impacts BC, junction angles, wayfinders etc. if it ain't broke don't fix it mentality should be taken as mass fixing things will result in mistakes as you mentioned.

Clearly this is the future of how we design intersections moving forward and finding the right balance to aid in this transition is important.
Inactive user -1649923503-
Posts: 1023
Has thanked: 404 times
Been thanked: 460 times
Send a message
-John
-------
https://j.mp/1BqcgbWhttps://s.waze.tools/c5.png
VT - State Manager
New England - Multi State Manager

Post by Inactive user -1649923503-
With scripts helping point out TIO. The need for the MC was negated. Now it would be great if this option was native to WME and not script based but this helps address new editors who don't know better and allows a more meaningful usage of MC. I think the removal of MC was the right decision.


Sent from my iPhone using Tapatalk
Inactive user -1649923503-
Posts: 1023
Has thanked: 404 times
Been thanked: 460 times
Send a message
-John
-------
https://j.mp/1BqcgbWhttps://s.waze.tools/c5.png
VT - State Manager
New England - Multi State Manager

Post by Inactive user -1649923503-
Is it possible to start working on the scenarios for when to use "Continue" as this way we can be ahead of this scenario when it goes live.
Nagamasa wrote: - country borders
- change of designation in freeways
- BC to and from ramps
- last node before a tolled segment
The wiki currently indicates the "Continue" for an on ramp, and I completely agree.
In an earlier post from Nagamasa,
-I agree with country borders
-Changes of designation in freeways (wording to more express the ending of one and the start of another)
-Ramps should be worded in a way that they can be evaluated for clarity if a "Continue" prompt would help
-I do not support the tolled segment one as general guidance, there is definitely some examples where it would be helpful but with the toll indicator for the route. The limitations that exist in the waze app regarding tolls and routing, carpool lanes, and other variations would further complicate this discussion.

Any other ideas for "Continue"
Inactive user -1649923503-
Posts: 1023
Has thanked: 404 times
Been thanked: 460 times
Send a message
-John
-------
https://j.mp/1BqcgbWhttps://s.waze.tools/c5.png
VT - State Manager
New England - Multi State Manager

Post by Inactive user -1649923503-
Couple thoughts
Greater than 20 degrees should be practice since that makes in app closures easier.

I agree avoiding the 45 degree mark is important to help ensure no accidental turn vs keep.

My philosophy has always been a turn requires some form of braking a keep does not and I do not like utilizing exit prompts unless it is off a limited access road.

From everything I have heard microdog legs should be avoided. And yes the editor leaves something to be desired in identifying them without scripts which is a problem for both mobile editors and new editors that dont know this feature even exists. We should continue to give feedback to HQ on that instead of creating workarounds for this shortcoming in the interface. The hacks for BC are gone thanks to TIO lets not create new hacks.
Inactive user -1649923503-
Posts: 1023
Has thanked: 404 times
Been thanked: 460 times
Send a message
-John
-------
https://j.mp/1BqcgbWhttps://s.waze.tools/c5.png
VT - State Manager
New England - Multi State Manager

Post by Inactive user -1697532064-
DwarfLord wrote:overrides are something you use when other approaches are awkward, hackish, or impossible, and not just when it's the path of least resistance.
Why not though? If a turn instruction override is a more straightforward and robust solution (a slight change to angles doesn't mess up instructions), I don't see the need for caution about its use.
Inactive user -1697532064-
Wiki Master
Wiki Master
Posts: 1308
Has thanked: 549 times
Been thanked: 703 times
Send a message
Galaxy S20 FE on Mint
Retired SM Ohio
Then you will know the truth, and the truth will set you free.
-John 8:32

Post by Inactive user -1697532064-
Yes, TIOs change the visual as well as audible turn instructions. I always thought the speaker icon was misleading, because they do more than changing what the app says.
Inactive user -1697532064-
Wiki Master
Wiki Master
Posts: 1308
Has thanked: 549 times
Been thanked: 703 times
Send a message
Galaxy S20 FE on Mint
Retired SM Ohio
Then you will know the truth, and the truth will set you free.
-John 8:32

Post by Inactive user -1697532064-
subs5 wrote:I am still confused as to where the Exit right/left would be used in the collector/distributor interchange that is shown in the above wazeopedia link.
I think Nagamasa's bolded text is talking about exiting from a collector/distributor ramp onto a cloverleaf, not entering the interchange. So on the image from the linked page, traveling westbound on the freeway to southbound on the mH you would get exit right to the collector/distributor ramp, and then Waze would normally say keep right to the cloverleaf, but if there is an exit sign at the cloverleaf we should make a TIO to say exit right a second time. Here is an example that I have modified in just this way.
Inactive user -1697532064-
Wiki Master
Wiki Master
Posts: 1308
Has thanked: 549 times
Been thanked: 703 times
Send a message
Galaxy S20 FE on Mint
Retired SM Ohio
Then you will know the truth, and the truth will set you free.
-John 8:32

Post by Inactive user -1697532064-
nzahn1 wrote: Though, JBs are preferred by staff for situations (like "H" intersections) where mDLs were used to hack the u-turn prevention mechanism. They prefer we use obvious features rather than trying to craft the map to utilize hidden mechanisms.
If junction boxes are preferred for H intersections, of which there are many, maybe they should not be rank-locked so high, at least not if we change national guidance on how to handle these types of intersections.

In general I think that we should try to limit time-based statements ("we used to do it this way, but here is new guidance; this is how we do it now") in Wazeopedia. Just set out current guidance (including legitimate uses of doglegs), and if older methods need to be explained, that should be kept brief or placed in a mbox. I don't think there's much need to urge caution about removing micro-doglegs; it's just something you do when you see it and get around to it.
Inactive user -1697532064-
Wiki Master
Wiki Master
Posts: 1308
Has thanked: 549 times
Been thanked: 703 times
Send a message
Galaxy S20 FE on Mint
Retired SM Ohio
Then you will know the truth, and the truth will set you free.
-John 8:32

Post by Inactive user -1697532064-
I think we discussed in Discord or somewhere about how the you don't like the Waze default section is somewhat misleading. We do manage thousands of intersections, and sometimes the default is wrong, like an exit instruction from a minor highway to a street. I don't see how this section adds anything. Would anyone object to just taking it out?

Also, since BDP has changed to require name and type continuity for direct routes, I don't think discouraging TIO use in complex wayfinders is correct. Adding alt names in wayfinder stubs (as discussed here) makes pretty much every complex wayfinder require a TIO. I propose taking out the complex wayfinder section, renaming the simple wayfinder to just wayfinder and putting some of the text from the complex wayfinder section there to explain that you need more than just TIOs in many wayfinders to give correct instructions. Even if BDP gets changed again, we have no reason not to keep routes continuous through interchanges.
Inactive user -1697532064-
Wiki Master
Wiki Master
Posts: 1308
Has thanked: 549 times
Been thanked: 703 times
Send a message
Galaxy S20 FE on Mint
Retired SM Ohio
Then you will know the truth, and the truth will set you free.
-John 8:32