Problems with navigating a route

[menion]

Willy, exactly this I've found during the last weekend and made a bigger update in just published 3.27.2.11 Beta version, so please give it a try. Will do too during the weekend .

EDIT: damn, found one more issue after publishing a new version. Seems that app does not merge two tracks correctly ... yet. So the next version will be needed.

[poutnikl]

Hmm, I guess I have asked @Menion by other words about this possible undesired tailing recently as well. :-) ( not having opportunity to test it yet.)

Odesláno z mého Mi A2 pomocí Tapatalk

[poutnikl]

The new beta route priority recalculation seems working fine, doing deviations along a precalculated city walking route.

For both GPX based and directly calculated routes.

Odesláno z mého Mi A2 pomocí Tapatalk

[menion]

Surprised it works correctly to you . Anyway, new version just published.

And now it seems to be working well ...

[0709]

A 5.1.1 Locus 3.37.2.12

Report.

- Main track is a (B)router design inclusive nav orders.
- The connect track is by (B)router.
Picture > Connect track Brouter meets Main track B-router.png
Result > No nav order  generated at the  meeting point.

[menion]

Thanks for tests. If you in the first case get some navigation order on "meeting points", it should be more an accident then intent. I was thinking if the app should generate some navigation command on this crossing, but in the end, I've decided to left it rather "empty" then generate incorrect command just based on shape.

In the second case, there seems to be missing single trackpoint on the crossing. It may probably happen. We will see in terrain . But generally, it seems to work correctly, fine.

[jonny.blue]

Did some (couch-  )testing too ... and in many cases it works pretty good.

Only one time it leads me directly back to my starting point  ... but I couldn't repeat this ...

I think it's time for field test ... (when rain stops  )

[jonny.blue]

PS: can I change the value (30 sec) for delay time of recalculation  in config file?

Would be good for testing ... and maybe even in field ... because:
If Locus doesn't lead back I'm normaly back on route after recalculation. In other case my setting 'distance for recalculate' would prevent from immediately calculation.

[menion]

And raining and raining ... which is fine, nature was really dry.

30sec refresh is hardcoded in the app. If you want to trigger it earlier, you may simply over navigation menu manually, so I believe there is no need for customization here.
30 seconds is from my point of view optimal limit to prevent too frequent recalculation. And years of usage confirmed this .

[0709]

- The tail cutter is too agressive as ALL tails inclusive the planned ones in the main route_track are cut away by both route priority and point priority mode !

- By Route Priority. Detect and remove only those paths where the connecting track toward the meeting point covers the main track.
- By Point Priority.  Skip a Via Point at operation ?

- Locus Pro 3.37.2_route and point priority.gif

[menion]

Hello Willy,
thanks for the tests.

Point-priority: are there any changes in Beta version? Should not. Via-points are really must-pass points.
Option to skip via-point is really missing as well as the option to add via-point during navigation. I've well aware of it and it's planned.

Route-priority: what happens to you should really not happen . Send me please your route as GPX, I'll test it, thanks.

[jonny.blue]

30 seconds is from my point of view optimal limit to prevent too frequent recalculation. And years of usage confirmed this .

No problem  ... 

[menion]

@0709
Heh, same as in my answer 11 days ago on the help desk, I mix two cases, sorry .

We talk here about recalculation, so I again wanted to say that for point-priority, via-points are must-pass.

Anyway, new version 3.37.2.13 just published and it should solve
a) issue with via points & route-priority as in attach file (thanks for help)
b) added hopefully nice tool that should prevent recalculation back if user ignore "turn back" 2 times. So if you ride forward, app two times recalculate back and you still ride forward, 3rd recompute should be forward and not backward.

[0709]

Results in attachment.

[menion]

uff, both issue should be fixed, thanks. The whole system is quite sensitive on indexes, so I'm sure there will be a situation when the result won't be perfect. Step by step to victory .
Thanks Willy!