To me, it is so obvious as to be beyond debate--but as far as I know, it is still an open question. Until it has been settled, I have given up arguing for it. It's just too frustrating that some people still don't get that recalculating, or handling dead-ends, are mere distractions from the real purpose of this feature; i.e., to address those places on the map where correct navigation is impossible otherwise. That is where our focus should be.AlanOfTheBerg wrote:I agree. In my neck-o-the-woods, I'm only enabling them in places where they are necessary due to things like parking lot entrances only available from one side of the road due to barrier/signage, so the next best option (and recommended) is to go ahead one block and u-turn. I'm not enabling them on every 2-way neighborhood street where it is legal, because there's simply no reason to do so.harling wrote:I still think we're setting ourselves up for a huge headache by approaching this in terms of where U-turns are legal (or not prohibited), vs. where they are specifically recommended/provided for routing purposes.
The wiki should definitely have this kind of guidance.
Right: which is why the road in that example is (still) split. But once this new U-turn feature is released, that is the first place I am going to use it.CBenson wrote:My problem is that I have very little confidence that enabling a U-turn on a unsplit road is going to solve this kind of routing issue anytime in the next year or so.harling wrote:Mid-route, as in the example above, becomes a huge detour.
I assume that implies the uturn is not used on other segments yet.AlanOfTheBerg wrote:The engine does use the "uturn" junction at the end of dead ends already and has for a long time.kentsmith9 wrote:Alan, for some reason I was under the impression the U-Turn functionality was not going to be active in the navigation engine immediately. I thought there was going to be time to allow editors to update maps now that they have the controls to change it and the routing was coming sometime in the future.
I'm not clear what we said on dead-end streets. Do we need to set it, or will the routing engine turn you around no matter what? For example you turn down a dead-end street by mistake, won't the routing engine turn you around because the "penalty" for the disabled U-Turn is overridden with no other route possible?Proposed Wiki on U-Turns wrote: 1. The primary purpose for U-Turns is to enable routing where navigation is otherwise not possible to reach the destination; often at the beginning or end of a route.
2. Many locations have different laws on U-Turns with some locations allowing them unless marked as restricted and others restricting them unless marked as allowed; see the table (linking to a separate page) for a quick reference for your state or country.
3. Consider only enabling the U-Turn where it solves a UR or MP.
4. How to set U-Turns through the new UI
5. Dead-end streets...
The page name will be "U-turns" and we will add redirects to this page for:
* U-Turn
* U-turn
* Uturn
* u-turn
* uturn
* U-Turns
* Uturns
* u-turns
* uturns
* U-Turn restriction
* U-turn restriction
* Uturn restriction
* u-turn restriction
* uturn restriction
* U-Turn restrictions
* U-turn restrictions
* Uturn restrictions
* u-turn restrictions
* uturn restrictions
in Italy, someone has already done some experiments.AlanOfTheBerg wrote:Some of us are doing some tests to see if there's a difference in routing with un/locked u-turn at the dead end.twist3r wrote:So on dead-end streets is it better to leave the U-turn soft restricted as it is default now or to turn it on ? Which of the two performs better in terms of routing from a dead-end street ?
Re: U-turn Restrictions?