why no left turn at intersection

[CBenson]

I believe the OP is showing the intersection with shift-Z toggled on. Thus its showing the U-turn restriction for Coursey Blvd.

[CBenson]

The turn to go north on Bluebonnet is and was permitted. That's why waze gave the "correct" route if you had the navigation type set to shortest.

Bowties do not solve this problem as shown in this thread:
viewtopic.php?f=10&t=27801

[CBenson]

Here is another example.

Church.jpg (160.67 KiB) Viewed 2586 times

[CBenson]

Yes, I agree that in you example waze is avoiding the minor highway. But if you are turning onto Baltimore Annapolis Blvd. you have to make the major/minor transition somewhere so I don't see why that would favor the straight/U.

[CBenson]

Here is another example of a user that thinks this is bad routing:

SUBABlvd.jpg (196.22 KiB) Viewed 4889 times

https://www.waze.com/editor/?lon=-76.55 ... TTTTTTTTFT

[CBenson]

So I happened to refresh the tab with the route open and it gave me the U-turn, when it was giving me the simple left earlier.

MacFarland.jpg (39.1 KiB) Viewed 2370 times

[CBenson]

I doubt it. There are occasionally reports that changes in things like name or level affect routing and there may be some minor effects. But in general the level should not affect the route.

On the other hand, there have been a large number of reports, many recent, of waze routing straight/U rather than a simple left. I think the issue is that waze knows that there is an average delay to make the left onto the ramp, but as no one passes the ramp to make the u-turn, waze is not accurately guessing how fast the u-turn is.

Waze seems to able to route correctly. So it seems to me to be more likely to be an issue with the speed data than an issue with the levels. However, the levels don't really do much anymore, so I would go ahead and change them and see what happens.

[CBenson]

STRANGE.

Not too strange, it was a cut and paste error that I saw and corrected.

[CBenson]

I have resolved things like this by rebuilding each junction node (disconnect each segment and create a new junction node (don't drag the old junction back in). After that I never got the u-turn route again...

I suspect you're just destroying the speed data showing the right is significantly faster than the left.
I have one (discussed here) that has been repeatedly torn apart over the past year and put back together by different editors. URs show the intersection will occasionally route right/U again.

[CBenson]

Agreed. Those are the factors to balanced. Although, I don't think waze will route through a parking lot segment to get to an address on the northbound segment. I think waze will just skip the segment and go to the next to make the U-turn. But as you say, we don't really know.