navigation gets confused for track which starts/finishes at same location
Below I have created a simple track that starts (green dot) and finishes (red dot) at about the the same location. A common situation.
When I start navigation, if I am closer to the finish trackpoint than the start trackpoint (both of which are logically same location) then navigation thinks I have already completed the navigation even before I have started. Note below the track is already marked as being traveled, and displays the "big question mark" icon:
I now ensure when creating the track that the finishing point stops a little further back along the track, and when I start navigating, make sure I am also closer to the starting point than finishing point. If I notice the "big question mark" icon, I know I have cancel/restart the navigation.
I can alternatively set "strict route navigation" but then I loose the advantage/ features of "loose route navigation".
Once navigation has started properly there are no further issues, so I feel Locus could be a little smarter to detect this common situation and make a better initial guess instead of the more drastic option of "strict route navigation".
The same problem 
Hello Andrew,
I guess based on your screenshots:
1. you use just testing simulation mode, not a real navigation (GPS is disabled)
2. you have defined "maximum allowed deviation" less then 53 metres, that's why Locus display question mark and not correct order (navigation is switched to guidance because you are too far away from track).
Try you issue during real navigation and we will see. When GPS is enabled, Locus consider also your current azimuth, so during ride, such issue should not happen.
Hello Andrew,
I guess based on your screenshots:
1. you use just testing simulation mode, not a real navigation (GPS is disabled)
2. you have defined "maximum allowed deviation" less then 53 metres, that's why Locus display question mark and not correct order (navigation is switched to guidance because you are too far away from track).
Try you issue during real navigation and we will see. When GPS is enabled, Locus consider also your current azimuth, so during ride, such issue should not happen.
1. No - this is with GPS enabled.
2. No - as I ride along the track in the correct direction for outward section, directly on the track, passing navpoints, the question mark never changes, navigation never commences. It is quite easy to reproduce.
So do I have to be within 50m of the track before I should commence navigation, or should Locus automatically switch from guidance to navigation within 50m?
1. No - this is with GPS enabled.
2. No - as I ride along the track in the correct direction for outward section, directly on the track, passing navpoints, the question mark never changes, navigation never commences. It is quite easy to reproduce.
So do I have to be within 50m of the track before I should commence navigation, or should Locus automatically switch from guidance to navigation within 50m?
Locus switch automatically.
Anyway 1. cannot be correct. In case you have enabled GPS, visible line "53 m" have to be between current active trackpoint on track and you current GPS position (blue or green circle), not between your center cross.
This seems to be still repeating same problem. Track that lies on exactly same path in two directions. I'll try to simulate and check it during a week ...
Locus switch automatically.
Anyway 1. cannot be correct. In case you have enabled GPS, visible line "53 m" have to be between current active trackpoint on track and you current GPS position (blue or green circle), not between your center cross.
This seems to be still repeating same problem. Track that lies on exactly same path in two directions. I'll try to simulate and check it during a week ...
It didn't happen today. Same path in two directions, with start/finish at same point. I started navigating >50m from start but it worked OK.
It didn't happen today. Same path in two directions, with start/finish at same point. I started navigating >50m from start but it worked OK.
Just a little update on this topic. When I switched the Map Icon setting from dots to icons for the start/stop I think I found the problem - when I created a new copy of the track (with reverse route) the stop point (which had been further away) now becomes closer than new start point. So when I start navigating the stop point is closer, and without strict navigation, Locus correctly assumes I have finished the navigation. So close this topic. Lesson learnt.
Just a little update on this topic. When I switched the Map Icon setting from dots to icons for the start/stop I think I found the problem - when I created a new copy of the track (with reverse route) the stop point (which had been further away) now becomes closer than new start point. So when I start navigating the stop point is closer, and without strict navigation, Locus correctly assumes I have finished the navigation. So close this topic. Lesson learnt.
Ah ok, good to hear. These "start-stop on same place" and also "criss-cross" navigation tracks will be my death. :)
Ah ok, good to hear. These "start-stop on same place" and also "criss-cross" navigation tracks will be my death. :)
Everything has been greatly improved in the latest releases - track editing/ navigation/ time to target - all working perfectly for non-strict navigation.
Everything has been greatly improved in the latest releases - track editing/ navigation/ time to target - all working perfectly for non-strict navigation.
Glad to hear it. Also mainly because of "start/stop" (rounds) trips, I've created support for "via points". Thanks to this, "recalculate" is also usable and with GraphHopper (probably also a BRouter), it is a deadly combination :).
Glad to hear it. Also mainly because of "start/stop" (rounds) trips, I've created support for "via points". Thanks to this, "recalculate" is also usable and with GraphHopper (probably also a BRouter), it is a deadly combination :).
I would love to use GraphHopper but unlike BRouter it doesn't support profile scripting and hence can't be adapted to country-specific customs. For example motorways in Tasmania can be cycled (unless signed) but GH creates track 20km long to avoid going through 100m motorway roundabout; with BRouter I can easily adapt these rules and tweak the elevation costs to suit my style of riding.
I would love to use GraphHopper but unlike BRouter it doesn't support profile scripting and hence can't be adapted to country-specific customs. For example motorways in Tasmania can be cycled (unless signed) but GH creates track 20km long to avoid going through 100m motorway roundabout; with BRouter I can easily adapt these rules and tweak the elevation costs to suit my style of riding.
Replies have been locked on this page!