If you look at the GPS route and Waze provided route, it’s pretty obvious what happened. Waze routed the user to turn right, then make a U turn, effectively executing a wide left turn.
I can’t figure out what caused this. Any ideas?
If you look at the GPS route and Waze provided route, it’s pretty obvious what happened. Waze routed the user to turn right, then make a U turn, effectively executing a wide left turn.
I can’t figure out what caused this. Any ideas?
That’s pretty funny. Will mark again to try to follow up tonight, but I’d guess that Waze believes it is faster to make a right turn, then a U-Turn, than to just make the left turn =P.
What we talked about this afternoon/morning may actually be a contributing factor.
Ok. I think I’ve figured something out here…
The segment that the user was routed to (east, then UTurn back west) is actually TWO parallel segments. Split road? Why? https://www.waze.com/editor/?env=usa&lon=-122.01426&lat=37.27141&layers=3877&zoom=9&mode=0&mapProblemFilter=0&mapUpdateRequestFilter=0&venueFilter=1&segments=84588553,84588557
Could this be causing the weirdness?
No the split road should not be the cause of the issue. The split road is because that segment is “divided” into 1 right lane going straight and 2 left lanes turn left. This split allows the app to announce earlier so people can get into the proper lanes.
I think what KT says earlier is the most likely answer - turning right and U-Turn is faster than turning left.