- Right turn needs to be allowed. Can verify with SV and a UR. PL:
- Should consider allowing U-turns as well. PL:
Thanks!
I enabled the right turn. The U-turn is an interesting question, I’m discussing it with Orbitc. I suspect we won’t support them.
-
Perfect
-
Please let me know if I should respond to the URs?
Thanks
Go ahead and respond to URs.
We are not going to honor the U-turn requests?
What’s effectively being asked for is a dual roadway, one road for each direction. We have rules for where those should be used and where those should not, and this doesn’t meet them.
The reason we don’t like dual roadways is because they come with their own problem. They tend to cause display issues, unwanted U-turns (less of an issue here, bt not entirely), and they often need short segments that themselves cause routing problems for Waze.
The benefit does not outweigh these costs.
That said, I would have been kind of OK with it myself.
Thanks for keeping me updated.
U turn support brings very limited value to the map and navigation. The overwhelming majority of trips do not have planned u-turns in the middle of the trip. Because of all the potential side-effect problems enabling them would cause, it’s not unreasonable to expect drivers to be savvy enough to make any necessary u-turns on their own to either get on course at the beginning of a trip or to reach their destination at the end. I just don’t see the benefit of dropping work on many much more pressing issues (like getting a TTS announcement at all with this new update) than getting a TTS announcement to turn around on Park Ave when you drove past your turn (btw, most drivers hate when navigation does that anyway).
I agree with not being particularly beneficial, but some of your logic otherwise bewilders me.