How to Fix Illegal U-Turns?

I am getting a bunch of illegal u-turn URs. The issue is that I cannot change any of the turns restrictions b/c that would also disable legal left turns. This is especially true when two split roads intersect. Has anyone discovered a solution to this problem? See example below, if the segment isn’t highlighted, the illegal u-turn prompted by Waze is heading E on Belt Line, N on Preston and immediately W on Belt Line.

https://www.waze.com/editor/?zoom=5&lat=32.95468&lon=-96.8036&layers=BFTFTTTFTTTTTTTFTTTTFT

At present, the “trick” to enabling/disabling U-turns on a split roadway is in the length of the segment between the two directions. If it is 15m or longer, U-turns are permitted; shorter, and they are not.

It’s an inelegant solution (a charitable way of saying “hack”), presumably because adding explicit U-turn properties for each end of each segment would entail a major redesign of the road database and routing algorithm.

2 split roads to a single intersection node= mapcat bowtie.

Sent from my iPhone using Tapatalk

Ok. Well, I guess I can work on some of those areas where the problem is common. But I am not tempted to do all these intersections unless I see a specific UR I guess. Yucky. I won’t like the way it looks… Perhaps we can just tell people that even if Waze says U-turn, use common sense. :sunglasses:

Not certain that a Mapcat Bowtie would work well in this situation (at a junction of two split roadways) – it would definitely look a tad wonky, especially to Wazers waiting for the light to change … might generate more UR’s than it prevents! :wink:

I think I’d go with Harling’s suggestion on this one – just squeeze the junctions in toward the center a bit to get the cross-segments down to 14 meters, and it should be okay after the next update. :slight_smile:

I had an intersection that had trouble routing through. Mapcat put in a bowtie and I haven’t seen a UR there since. Now it could have been a corrupt node causing the problem and once it was gone, problem fixed.

I thought same about looks, but when it functions right, i can deal with the looks.

Sent from my iPhone using Tapatalk

Unless the road has a really wide median, the bowtie isn’t all that noticeable in the client. Narrowing down to 14 m is completely invisible in the client.

Just remember, you have to remove the street name from the cross segments < 15m to get it to suppress U-turns.

Yup - no name for the intersection segments, it can not be explained WHY but it is important. Currently, I do not use mapcat-bowties anymore. If the crossing is smaller than 10x10m those lanes can most often be unsplit; if smaller than 22x22m it can easily be reduced to 14x14m - you don’t see that in the client. Only the really big ones than need more measures such as an inner cross.

So, even w/o the named segment, will the driver still get prompted to “turn left on Belt Line Rd” for instance for a legal left turn?

Yes, if the route goes thru an unnamed segment the name of the next named segment is shown in directions.

Groovy, thanks a bunch!