+1

I was just thinking how nice a script like this would be.

Thanks for the detailed response taco99. You are correct, unfortunately there are way to many parameters that come into play. I was simply looking for a 90 degree script for intersections, but now you have brought up valid points as to why it wouldn't work and how some may become over zealous in using it and ruing junctions and how Waze interprets those.

I asked for this a few months ago.
The problem is that no script can intelligently determine what needs to be done to adjust the angles.

Do you need to move the junction itself (and are there any hidden doglegs that will be damaged by this)?
Do you need to slip a dogleg?
Do you need to add a dogleg?
Do you need to go to the middle of one of the feeders and make the adjustment from there?


I know we all have our OCD side, that's one reason we do this, but this is something that simply does not matter. Anything greater than 45 degrees is treated the same way.

There are only a few angles that are important:

Minimum 20 degree inside angle (160 degree "turn") so users can tap arrows to report closures. This is not a functional "rule"... Waze will work with the inside angle at 1 degree, but users will not be able to isolate the segment to report a closure.

Under 45 degrees produces "stay/exit", or no instruction for BC
Over 45 degrees produces "Turn" even for BC, unless it is the only available option.
(I personally avoid anything between 40 and 50, as we don't want something on 44 getting bumped to 46 by accident)

Divided highway u-turn penalty is added when the crossover segment is under 15m and the sum of the approach and departure angles is between 176 and 184 degrees (note, a pair of 90 are not required, a skewed intersection will properly penalize with a 70 degree entry and 110 degree exit)

Conversely, divided highway u-turn will be routed when the crossover segment is under 15m the sum of the approach and departure angles is less than 175 or greater than 185 degrees, and it is allowed by the turn restrictions.
If the crossover segment is over 15m, then only the 20<45< rule applies, the u-turn will be routed if allowed by the turn restrictions.

Beyond that, it's simply not important. The app does not display the aerial imagery, the app does not render segment separations of much under 15-20m, the app "smooths" curves so we do not need 50 geonodes on a curve to have the road appear "nice" to the driver.

Especially on a divided highway where the U-turn is allowed in one direction and prohibited in the other.
This can be done without AGC by making the crossover segment 14m, and on the prohibited side, the sum of the angles is 176-184, and on the permitted side, doglegs are added to set the angles to 170 or 190.