I drive this route every day to work so it is a pet peeve that Waze always routes me on a worse route.
Heading southbound on Zanker, myself and hundreds of others make a u-turn at Tasman due to the median on Zanker. I went into the map editor a few weeks ago and allowed a u-turn here, but reading on the forum seems to indicate that u-turns are not enabled in the routing engine for unsplit roads. I read the best practices which indicate that one case for splitting a road with a median barrier is to allow u-turns at the intersections where they are allowed.
Should Zanker be split, at least at the intersection with Tasman?
https://www.waze.com/editor/?lon=-121.93725&lat=37.41265&zoom=7&layers=BFTFFTTTTTTTFTTTTTTTTTTFT&segments=70844452
Thanks!
I beg to differ. I have purposely allowed a u-turn at a point on my commute to test it and u-turns do work on the app.
Wm
*i beg to differ with the thread you mentioned…
Not sure who you are differing with here. 
U-Turns are enabled in the editor, but not yet in the routing engine.
Therefore the only solution would be to split the road, but we have been trying to hold off on that with U-turns just about complete. Ultimately split roads adds a lot more complexity to the map and that has been why we try to prevent (and often unsplit roads).
Kent,
Perhaps I’m not following what you mean by routing engine. Could you clarify?
Wm
The Waze back-end servers that compute the navigation and send it to your client app when you ask it to route you from point A to B. That work is not done on the client app in contrast to how a stand-alone GPS unit would work in your car.
Ok thanks for clarifying.