It was possibly a year ago.FokusPokus wrote:P.S. Could you possibly point me to the discussion you mentioned ?
I had brought it up as a suggestion, you might be able to find it if you search my posts. It MAY have even been in this thread, as like you, I felt that it would be a natural for Toolbox.
The main point is and was in the earlier discussion, it really doesn't matter.
The only angles that are important are near 180 (U-Turns), 45 (Turn/Stay-Exit), and the sum of the entry/exit angles on the median of a divided road (U-Turn)
We all tend to be a little OCD, it's one reason that we do this. But just as when sometimes a segment causes incorrect routing when it perfectly matches the aerial imagery and works well when moved closer to the sidewalk, sometimes we need to set aside our desire for something to be "perfect".
The app does not currently display aerial imagery (it will likely never due to data usage) and the vehicle "snaps" to the nearest segment.
The difference in angles between 80 and 110 degrees will not be apparent in the app... you can't even see the empty median on a divided road until there is more than 15m between them.
Smoothing routines in the app round off our sharp turns.
In your example, the junction needs to be looked at closely before application of a script... it's not a major chore to manually make the adjustment if needed, but whether 90 degrees or not, anything over 46 is going to produce a "turn" instruction.
Re: [Script] WME Toolbox (1.6.9)