[Clarify/Update Page] U-turn policy?

Moderator: Unholy

Re: [Clarify/Update Page] U-turn policy?

Postby purposeguy » Thu Jul 10, 2014 4:49 am

I think the issue is the very complex problem that this thread is about, and can't be solved by a local editor! Sadly, it was in the middle of a long and complex drive, so I can't remember the specific street. Unless there's a way for Waze to show me my steps from a specific, historical journey precisely.
Image High Plains Area Manager
purposeguy
Map Raider
Map Raider
 
Posts: 248
Joined: Fri Jun 27, 2014 2:04 am
Location: Berkeley, California, USA
Has thanked: 116 times
Been thanked: 29 times

Re: [Clarify/Update Page] U-turn policy?

Postby purposeguy » Wed Jul 09, 2014 8:33 pm

FYI, I was routed down a dead end street with a U-turn at the end two days ago. I'm running a V3.7.8.0 client. There was no U-turn symbol on the screen and no voice prompt for a turn at the end of the street. It was definitely looking ahead to the next turn.
Image High Plains Area Manager
purposeguy
Map Raider
Map Raider
 
Posts: 248
Joined: Fri Jun 27, 2014 2:04 am
Location: Berkeley, California, USA
Has thanked: 116 times
Been thanked: 29 times

Re: [Clarify/Update Page] U-turn policy?

Postby PesachZ » Fri Feb 06, 2015 4:45 pm

dmcrandall wrote:Ran into a UR about Waze directing a driver into a dead end street to make a U-turn. I closed it before remembering this thread (courtesy of Otto).

Here's the link to the UR. Hopefully you can get something from it before it closes out completely.

https://www.waze.com/editor/?zoom=5&lat ... st=3910028

This thread is specifically discussion the penalty preventing u-turns as they apply to 3 segment u-turns on divided roads.

Sent using Tapatalk for Android 4.4.2
ImageImageImageImageNYImageImageImageImageImageImage
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
PesachZ
Wiki Master
Wiki Master
 
Posts: 4486
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1993 times
Been thanked: 2319 times

Re: [Clarify/Update Page] U-turn policy?

Postby ottonomy » Wed Nov 19, 2014 10:16 pm

I would say that in recent months, the only two-way segment U-turns I've seen (or heard reported) have been upon route recalculations, which backs up the idea that Waze has effectively penalized them out of the usual routing server options. Having said that, one of the reasons I may be seeing SO few U-turns lately is the simple fact that almost ALL of them have been disabled in greater Los Angeles. When the time comes that Waze supports these, I will happily make it part of my routine to allow the U's where appropriate. I don't mind the general guidance being permissive on enabling U-turns, but some kind of a clause suggesting that in urban areas there should be consultation with local AMs before actively enabling U-turns would be much appreciated by me.
Country Manager & Global Champ - United States
Regional Coordinator - Southwest
Assistant Regional Coordinator - South Atlantic
Area Manager - Southern California
ottonomy
Global Champ Mentor
Global Champ Mentor
 
Posts: 762
Joined: Thu Oct 11, 2012 6:31 am
Location: Los Angeles CA
Has thanked: 1469 times
Been thanked: 646 times

Re: [Clarify/Update Page] U-turn policy?

Postby ottonomy » Mon Jul 14, 2014 4:41 pm

redviper26 wrote:Hey guys,

Can you send permalinks of routes affected by this issue?

Thanks,

Noam

Hi Noam,

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)?

Thanks,

Otto
Country Manager & Global Champ - United States
Regional Coordinator - Southwest
Assistant Regional Coordinator - South Atlantic
Area Manager - Southern California
ottonomy
Global Champ Mentor
Global Champ Mentor
 
Posts: 762
Joined: Thu Oct 11, 2012 6:31 am
Location: Los Angeles CA
Has thanked: 1469 times
Been thanked: 646 times

Re: [Clarify/Update Page] U-turn policy?

Postby ottonomy » Sun Jul 06, 2014 11:15 pm

sketch wrote:It seems rare.

Spend a week driving the afternoon rush in LA, and no odd Waze behavior will seem all that rare anymore ;-)

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..

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"?

U-turns under other conditions are more frequent for me. Not common, but not exactly rare. I speculated in my previous post that Waze may assess a penalty when considering a U-turn (on an un-split road), such that the routing server will consider other options first. Let me explain what makes me think this. The likelihood that I will be given a U-turn in my route goes up exponentially with the heaviness of the traffic around me. I never get them when driving in the late evening, or in more remote, less crowded areas.

Between 4 and 6PM, there are parts of LA where streets in close proximity to the freeways become so gridlocked that it can literally take 15 to 30 minutes to traverse a single city block, and it's times and places like these when Waze is most likely to throw me a U-turn, rather than sending me around the block, like it usually would. in other words, instances which might overcome penalties.

Take the situation in my screenshot, for example. Here's a view from before I approached the turn. I panned ahead, to see why Waze was having me turn the "wrong" way on 120th St.
U-Turn-2.jpg
U-Turn-2.jpg (87.81 KiB) Viewed 1010 times

You can see what Waze was up to here. The normal route is to take a right at 120th, and then another right onto the ramp for I-105 E, the tail of which can be seen in bright scarlet red on the right. It was stacked with a line of cars waiting for the meter to enter the freeway. Because that ramp was jammed, it made more sense to Waze for me to turn the other way, make a U, and get on the ramp from NB Crenshaw instead. This wasn't a situation where there was no other practical way to route me. The U was just a faster way. But in my experience, Waze would never suggest this if the other on-ramp were only half as jammed. I know, because this is a regular route for me.

sketch wrote:The screenshots uploaded by davielde and ottonomy

When did those occur? Because something has changed. It used to do this...

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:Bowties

I am of the opinion that bowties should never be used where U turns are permitted.


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.

My own dislike for bow-ties is what led me, in my earlier editing days, to make much heavier use of at-grade connectors for left turns. They can effectively allow or disallow U-turns, but don't fit every situation. I still use them occasionally, but have had so many of mine deleted by the CM clutter police, I resort more often to bow-ties, because they're more likely to stick around.

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.


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.

But in any of these bow-tie or regular-split intersection cases, a quick look down at the screen will show you a highlighted route with a clear turn-around point ahead. It's an understandable visual cue.

I'm not sure how you can say that a bow-tie prompt is "utterly confusing", but in the next breath more or less dismiss the far more baffling (lack of) instructions for an un-split road U-turn. I don't think you are considering just how confusing that can be, and how frustrating it is when it happens at a time and place where a mistake and recalculation can cost all the time savings for which you were using Waze in the first place.
Country Manager & Global Champ - United States
Regional Coordinator - Southwest
Assistant Regional Coordinator - South Atlantic
Area Manager - Southern California
ottonomy
Global Champ Mentor
Global Champ Mentor
 
Posts: 762
Joined: Thu Oct 11, 2012 6:31 am
Location: Los Angeles CA
Has thanked: 1469 times
Been thanked: 646 times

Re: [Clarify/Update Page] U-turn policy?

Postby ottonomy » Thu Jul 03, 2014 6:44 am

It sounds as if some of you commenting on this thread may never have experienced the current U-turn behavior in the app. I find this surprising, but not impossible to believe. I thought that davielde's post and screenshot made it all clear, but let me try to very clearly elucidate my own experience with this.

First, there is no doubt that Waze does occasionally include U-turns at the ends of single two-way segments in its routing, when the turns are enabled in WME, and it has a compelling reason to do so. It seems to me almost as if there is some light penalty attached to this, because of the relative rarity of the occurrences.

Second, routing is not to be confused with on-screen turn instructions or TTS in this context. Waze routes the U-turn, but it gives no visual or audible indication of the turn whatsoever.

This is what you will see/hear when Waze routes a U-turn on an un-split road. Your highlighted route will appear to terminate abruptly in front of you, at whatever junction the routing server has chosen for the turn. What it's actually doing is doubling back upon itself, and going back under you, but there's nothing about the graphic which suggests that this is the case.

At the top of the screen, the turn instruction you see is what will be the next turn, after the U, which could be anything from feet to miles away. If the next turn is in very close proximity, the displayed distance-to-turn may be an accurate count of the number of feet to the U-turn, even though the displayed turn is not the U. In others cases, it will be the distance to the next turn.

If the next turn is distant, there will probably be no audible prompt at all as you approach the U. If the next turn is more or less immediate after the U, its prompt may be heard at the point where you would expect to hear the prompt for the U instead.

All of this is mind-bending even for an experienced driver and Wazer. It's utterly baffling, and throw-your-phone-out-the-window stupid for someone who needs a real helping hand from a navigation app.

See and hear:
https://dl.dropbox.com/s/v64gssa07phrin ... Prompt.m4v

U-Turn.jpg
U-Turn.jpg (103.96 KiB) Viewed 1108 times
Country Manager & Global Champ - United States
Regional Coordinator - Southwest
Assistant Regional Coordinator - South Atlantic
Area Manager - Southern California
ottonomy
Global Champ Mentor
Global Champ Mentor
 
Posts: 762
Joined: Thu Oct 11, 2012 6:31 am
Location: Los Angeles CA
Has thanked: 1469 times
Been thanked: 646 times

Re: [Clarify/Update Page] U-turn policy?

Postby Machete808 » Mon Jul 28, 2014 11:34 pm

I will also look for these examples, though it's less common in my area.

But here's my question (though it may be better placed in the "feature request" category): Wouldn't it help if when Waze routes through a U-turn, that the nav trace be altered so that the actual "U" is visible? So you'd end up with the purple line doubling around at the turn and displaying as two lines next to each other, with the "U-turn at X St" announced via TTS and in the top navigation menu bar?

It would be unfortunate to disallow all those U-turns currently (and accurately) enabled.
Aloha,
Vicki
Hawaii State Manager
Area manager, Los Angeles, NYC
Country manager, U.S.,Thailand
Image Image
Need support?
support.google.com/waze > Popular topics > FAQs > Other > Open a ticket
Welcome, new editors:
Here's a good place to start!
Machete808
Country Manager
Country Manager
 
Posts: 1459
Joined: Mon May 28, 2012 12:36 am
Location: Kaneohe, HI
Has thanked: 252 times
Been thanked: 297 times

Re: [Clarify/Update Page] U-turn policy?

Postby kentsmith9 » Thu Nov 20, 2014 12:07 am

I have only personally see the 2-way U-turn on segments during a real-time route recalc because I turned a different direction than originally advised. I have reported it in the past and saw it again just two weeks ago on a different segment with the same conditions.

Since it is not that typical and I presume Waze currently classifies it as a routing bug for now, I would not propose changing away from keeping the U-arrow if allowed in advance of the feature working. Either way there is work to be done since it is enabled in most of northern CA after the feature was made available.
USA: Now Idaho; previously California (Northern, SF/SJ)

ImageImageImageImageImageImage
PLEASE READ: Waze Map Editor (Start Here) | Editing Quick-start | Best Practices | Junctions
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 5578
Joined: Mon Apr 23, 2012 3:33 pm
Location: Boise ID and SF/SJ Bay Area of Northern California
Has thanked: 1507 times
Been thanked: 1711 times

Re: [Clarify/Update Page] U-turn policy?

Postby kentsmith9 » Wed Jul 16, 2014 4:57 am

Today this segment showed a U-Turn on my client app when I was coming from the SW on that road. It was trying to get me to turn around. Funny thing is it could have simply turned left at the intersection, but at the moment it happened, I had taken the wrong turn (wasn't paying attention) and it automatically recalculated the route trying to get me back to the road to the SW. The map shows no U-Turn is even possible there. I can send a screenshot of my client if required.

Like the prior entries the route comes to a point on the screen, but the next turn indicated was the turn I would have taken "after" the U-Turn would be executed.
USA: Now Idaho; previously California (Northern, SF/SJ)

ImageImageImageImageImageImage
PLEASE READ: Waze Map Editor (Start Here) | Editing Quick-start | Best Practices | Junctions
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 5578
Joined: Mon Apr 23, 2012 3:33 pm
Location: Boise ID and SF/SJ Bay Area of Northern California
Has thanked: 1507 times
Been thanked: 1711 times

PreviousNext

Return to Wiki Updates and Discussion

Who is online

Users browsing this forum: Baidu [Spider]