Re: [Clarify/Update Page] U-turn policy?
Posted: Mon Jun 30, 2014 7:56 am
Just be sure to use the {{As of}} template so we can find this guidance in the future since we know it will eventually change.
Waze: outsmarting traffic together
https://www.waze.com/forum/
Interesting. When U-Turns were enabled in the editor, I set up a bunch in my neighborhood in order to see when they were working in the client, but I have never seen any on-screen navigation show the U-Turn in action with or without the voice navigation. However I am not sure what else would cause your on screen example other than this. If true, this is really sad because so many people have been setting U-Turn instructions in the streets of SF one by one to get them ready when it works. This guidance says to disable all of them and start over when it comes back. Maybe there is a better way on the app side that we can get ways to implement.davielde wrote:As an example, you would not be doing users a favor to have the following behavior on any road, not simply a divided highway that's not split in Waze. As seen in the screenshot, the next turn is in three miles--behind you...?
Based on what was posted earlier in the thread, the Waze route includes the U-Turn in the navigation, but fails to send the instruction to TTS and the display list, so the driver has no idea what happened.DwarfLord wrote:If I follow what others are saying, Waze CANNOT give a voice announcement for a U-turn, but it CAN provide a route that requires one. If both were CANNOT, or both were CAN, everything would be fine.qwaletee wrote:either Waze NEVER gives a U-turn instruction because it can't, in which case, why all the fuss about making sure they are all disabled? Or, Waze CAN give such an instruction, but rarely does (never seen it documented), in which case, why aren't we setting them up correctly?
Based on a PM with Noam, they are looking for more of the second one, but if anyone has any of the first one they can use that as well.ottonomy wrote:Are you referring to occurrences of dead-end U-turns being used in routing as turn-arounds, or the separate issue we've been discussing here about U-turns on two-way segments displaying misleading prompts (for the next turn, rather than for the U)?
Spend a week driving the afternoon rush in LA, and no odd Waze behavior will seem all that rare anymoresketch wrote:It seems rare.
I think I've only been given the dead-end turn-around U-turn route once, and that was in 2012. I have, however, seen URs with suggested routes which appear to have been such turnarounds, and fairly recently. Can you more narrowly define "early 2014"?sketch wrote:According to staff, the old problem where dead-end U turns used to be used erroneously shouldn't occur anymore, because of the small detour prevention mechanism, implemented early 2014. I haven't seen an example of it since then, so maybe it is actually working for this particular case.
Aside from the dead-end problem which I experienced only once..
My screenshot is from March 28, 2014. I don't recall ever having seen an actual U prompt on screen, and believe me, when I get a route with a U in it, I'm staring at my screen and trying to figure out what Waze is doing. I was also wondering whether your shot was from a beta build or production. At least since the beginning of 2013, there have not been any on-screen arrows or instructions which suggest that a U-turn is ahead, where the highlighted route just stops.sketch wrote: The screenshots uploaded by davielde and ottonomy
When did those occur? Because something has changed. It used to do this...
Agreed on generally limiting the use of bow-ties, but I think you are overlooking the best use-case for them, which is the ability to selectively allow U-turns in different directions at a given intersection. In your part of the country, are there few locations where U-turns are only legal in one, two, or three out of four directions? We have that sort of arrangement at every other intersection in LA, it seems, and they are often in areas where the only alternative to a U is a very long and ugly detour. I don't like bow-ties any more than anyone else does, but until we have junction boxes, they serve a purpose, and not exclusively that of disallowing U-turns.sketch wrote:Bowties
I am of the opinion that bowties should never be used where U turns are permitted.
While I do agree with you that "Turn left onto [the road you're on]" is potentially confusing, I don't see how "Turn left onto [something], and then turn left onto [the road you're on]" is really much less confusing. They are both bad prompts, and swinging a U hardly resembles a two-turn maneuver than it does a single turn. Yes, it's nice to hear the name that will be on the sign where you'll be making the initial turn, but that doesn't always happen. Because of issues like street name changes at intersections, we often leave the cross segments un-named. In those cases, the double prompt names the street you're on twice.sketch wrote:Bowties
... "Turn left on [x]" is utterly confusing when what you have to actually do is make a U turn. The entire reason bowties exist is to prevent U turns. Keep the road split like normal so it can say "Turn left on [y] then turn left on [x]".
What should the guidance be?
I would support enabling U turns only on actually-divided highways that are not divided ("split") in Waze, for the time being. In my experience, it only happens very rarely, so I don't think it'll cause a whole lot of confusion. After all, if the driver just drives past that point, they'll get a recalculation. If it gives them another U turn after that, they'll probably figure it out.