Planner trackglitch detector

[0709]

Hi Menion.

The trackglitch indicator by the Locus_app_BRouter (offline) planner is sure very usefull
The indication is by a red circle "alert" indication at the end of the relevant (short) trackglitch section.
But when using the Locus_GH online router some trackglitches are surprisingly not indicated.

It seems GH generates a simplified track so there is not always that expected perfect 180° overlap track backfold. But as GH produces the U-turn commands in the export file by the -98 sign such should trigger a Locus  U-turn command by rtePointAction>12 or <sym>U-turn.

By actual Locus planner if no perfect 180° track backfolds means no visual red alert !

Suggestion.
Keep the usefull trackfold track line indication as is now.
Put the visual red circle alert onto those Shaping Points that do trigger.
- Or trackglitches by perfect 180° track back folds as detected by Locus_BRouter
- Or the unexpected U-turn instruction commands produced by GraphHopper.

This indication should do the job this for both routers GH and BRouter.
As only repositioning of the corresponding Planner Point solves a trackglitch issue. 
Reposition the Planner Points until the red circle alarm is gone = trackglitch gone.

U-turns both the unwanted and desired ones are triggered by either a Shaping or a Via Planner point.
If you need to correct U-turns, you must therefore have both types of Planner Points available.
It is therefore important that both Planner Points types remain available at all times, even by file transfers.

Actual Locus Version.
Locus supports U-turns commands at import by the sym U-turn. 
Route You web generates U-turns commands by the sym U-turn. 
Locus_GraphHopper nor Locus_Brouter generates sym U-turn.

If there is U-turn support, you can still "accentuate" suspicious u-turn elements with a circle, also later in the normal map display used for navigation. The standard turns get the usual discrete "blue" small dot. And the U-turns get that extra "alert circle". In this case, they will not escape special attention so quickly.

[Menion]

Hi Willy,
hmm this simplification is quite stupid, thanks for the info about it.

You wrote "If there is U-turn support, you can still "accentuate" suspicious u-turn elements with a circle, also later in the normal map display used for navigation. The standard turns get the usual discrete "blue" small dot. And the U-turns get that extra "alert circle". In this case, they will not escape special attention so quickly." > in the app already is U-turn support. Question is if problem you found is rare or happens really often. If it is rare, then I do not think it is necessary to solve. GraphHopper is no longer a primary app router engine and this small feature is a not a core feature ...

[0709]

In the first post I added a picture of a non 180° trackfold created by Locus_GH.
That instruction "Straight" shown in the image is very strange. No ?
In the attachment find a file converted by the GH to Locus tool by Liskin.
https://github.com/liskin/locus-graphhopper-gpx