I’ve seen a couple of these now and in a way it makes sense. Looking at it, you’re going from the right side of a split road, turning left onto the segment that stretched between the two, then turning left again onto the other side of the split road. Surely though this isn’t expected behavior…
Is there a way to prevent this? I’ve read about “bow ties” and seen how they look, but these seem to be fairly rare. What could / should be done to solve this?
There are ways - but for a divided road intersection, for the most part, they will have the double left turn. Going back and forth will damage the timings across the nodes.
There’s a history to this however. But basically the double left turns are the way around Waze dealing with a divided road as there is inherent U-Turn prevention.
Okay. I get that a double left turn is a band-aid to the problem. But I feel like the experience of the end user is paramount. When you’re driving along an expressway that’s been split in Waze but is for all purposes a two-way road to the driver, why should a driver have to worry about u-turn prevention – why can’t it just say “Make a u turn” …
Help me wrap my head around the documentation (I’m not being resistant - I’m truly trying to understand ) :
Why is the reason to prevent U-turns at H intersections (if that’s the correct way to get to the destination) and what circumstances would warrant a denial of U turn?
For what it’s worth, U turns are explicitly allowed at that intersection.
Essentially yes, but this might be a little more diplomatic:
Hello, I am a fellow Wazer and local volunteer Map Editor. Waze recently implemented u-turn navigation commands; however, it is not fully effective on divided highways. For the meantime it will route you in two left turns, to effectively create a U-turn. This is a programming issue that cannot be changed by the volunteer map editors. We understand that Waze is working on a fix. Since no map changes were made, I am closing this report as not identified. Thanks!
Well, obviously I wasn’t going to literally be short with a user =P … but I appreciate your explanation. So far it’s been the explanation that’s made the most sense to me so thank you for posting it!