From my point of view it would be better to improve route automatically - if I understand right there is an easy way to identify “wrong” U-Turns.
There was a route example supplied by @llodiers :
Loading that route (app or web) and analyzing it, all “error” U-Turns are related to wapoints:
WP7, WP14, WP15, WP16, WP27, WP37, WP38, WP39, WP40, WP43, WP45, WP48, WP49
All of them besides WP45 and WP48 can be identified by an easy rule: U-Turn conected to a waypoint, with an other turn point less than 15m before / after. WP45 and WP48 have bigger deviations due to snapping next street.
So I would provide a rule, which is executed if a GPX route or track is imported:
- If a U-Turn is connected to a waypoint, and an other turn instruction if less than 15m (to be discussed, if perhaps even 20m or 30m) before / after, shift that waypoint to the position of the turn instruction.
- after shifting all waypoints, do a new route calculation
This would fix most of the “error” U-turns in that route.
If you have further examples of routes with “error” U-turns, please provide that examples here.
Even if stopover waypoints are snapped over 30m to an other turn instruction, from my point of view this will not harm even if user has to ride in an other street for 30m.