iainhouse wrote:

doctorkb wrote:It depends on your jurisdiction.

+1

In the UK, the vast majority of currently enabled u-turns appear on single segment streets at junctions where u-turns are physically impossible. I suspect that they have all been created by users effectively doing a 3-point turn at the junction using one of the connected segments - all within too small a space for GPS resolution to see what's happened. Waze then soft-enables a u-turn.

The result is that the client will (if it wants to turn the driver around), try to route them to do a u-turn where none is possible. Of course another issue is that the client can't actually give a u-turn instruction yet, but that's a whole other discussion.

At the few junctions (compared to the total number of them) where u-turns might be possible, they're specifically forbidden more often than not. That's simply because our ancient UK roads don't normally have wide enough carriageways or dividers to make it easy to do. From a UK perspective (and I fully understand that this does not apply worldwide), I would far rather JNF removed u-turns and I had to put them back afterwards - it would be the most efficient way to work here.

I'm sure we'd miss enabling some u-turns that are OK, but MPs and URs will help to alert us to the realistically small number that are actually legal here.

bgodette wrote:
Hooks into replaces 'q' (Disable All Turns) and does these actions on the selected node:

• Enables U-Turn and locks all turns at dead-end nodes. Changed Behavior
• Fixes any self and reverse connectivity issues
• Converts single node roundabouts (lollipops) and loops into a three segment loop. Any existing house numbers will be associated with the middle segment and MUST BE EDITED after save to update their stop point.
• If two or more segments are connected to the same two segments, it will split one of them. Same rules as SameNode.js bookmarklet.
• Terminates dead-ends
• Makes dead-ends two-way (only if both ends of the segment are visible)
• Sets the Type of a roundabouts using lowest of two highest rule and sets country/state if needed
• For UK sets Type of roundabouts using highest type excluding Freeway rule.
• Removes revcon (turns into wrong-direction of one-way), and selfcon (U-Turns at non-dead ends). Once the app has real support for U-Turns selfconf will be left alone
• Locks all turns at selected node.

bgodette wrote:

vectorspace wrote:The only determent I have found is that one could go wild just squashing red arrows, or perhaps forget and use it in the wrong place, and many times around divided roads, highway ramps, and the like, those red arrows are really necessary to impose valid turn restrictions.

Well since it doesn't change existing turn restrictions, I don't see how that's a problem.

AlanOfTheBerg wrote:

esochan wrote:There seems to be an issue with JNF0.0.7.5 today. With it on, I cannot enable/disable individual turn restrictions. With it off, I have no problems doing so.

Is anyone else having this problem?

Nope. I was editing on both infrastructures this morning with no problems. I'll clear cache and check again later.