Don't use guiding mode if user wants navigation mode (with BRouter)
When navigation mode is commenced with offline BRouter as the data source, but there are no turns (waypoints/ navigation commands) along the way, Locus decides it knows better than the user and enters guiding mode instead of navigation mode.
Note it appears (in my limited testing) this behavior only affects navigation when using BRouter as the navigation data source.
This feature? has caught out many users, myself many times, wasted lots of online discussion, chasing tails, going around in circles.
A workaround for an otherwise problematic track is that one single waypoint/ turn at road junction/ navigation command is required for correct operation. Any point will do! So, my suggestion is simple: if the user wants navigation, then use the navigation mode. Maybe internally, Locus can create a hidden point at the beginning or end of the track to be followed if need be, but the user shouldn't need to know or care about these details.
Or the question arises: Who has to generate that starting Nav point ? B-router or Locus ?
If track generated by B-router (Compute instructions = SET) starts by a "Straight" Navpoint, problem solved.
EDIT:
So I see by these very fast replys:
Your preferred solution = a solution by Locus. And so keep a cleanest generated track. (= trkpt points only)
As any Navpoint = An extra generated point in the Waypoint list ?
Attention ! If you ask Locus to Navigate on empty track = Generate navpoints based on the trackshape !
hmmm...only Brouter has the correct answer:
As I Brouter says: At Start Go straigth and further I have no instructions for you = a clear message.
Anyway= most important = idea is launched...and now waiting for that 3e vote. and more.
;-) 10u07 actual time.
Or the question arises: Who has to generate that starting Nav point ? B-router or Locus ?
If track generated by B-router (Compute instructions = SET) starts by a "Straight" Navpoint, problem solved.
EDIT:
So I see by these very fast replys:
Your preferred solution = a solution by Locus. And so keep a cleanest generated track. (= trkpt points only)
As any Navpoint = An extra generated point in the Waypoint list ?
Attention ! If you ask Locus to Navigate on empty track = Generate navpoints based on the trackshape !
hmmm...only Brouter has the correct answer:
As I Brouter says: At Start Go straigth and further I have no instructions for you = a clear message.
Anyway= most important = idea is launched...and now waiting for that 3e vote. and more.
;-) 10u07 actual time.
Rather, such a point should not be needed. There are legitimate cases, where BRouter is not expected to raise ANY navigation hint. Putting an extra point is rather a workaround to bypass the problem than a problem solution.
Rather, such a point should not be needed. There are legitimate cases, where BRouter is not expected to raise ANY navigation hint. Putting an extra point is rather a workaround to bypass the problem than a problem solution.
hate discussions on helpdesk because there is a mess with reply childs.
What ever...
'have 4 good arguments:
- If i select "guiding", I don't expect "navigation".
- If i select "navigation", I don't expect "guiding".
- If i select "guiding", I expect "guiding".
- If i select "navigation", I expect "navigation".
:)
and
...I need the "navigation" for my personal tts "arrivied" message/sound.
Possible?
hate discussions on helpdesk because there is a mess with reply childs.
What ever...
'have 4 good arguments:
- If i select "guiding", I don't expect "navigation".
- If i select "navigation", I don't expect "guiding".
- If i select "guiding", I expect "guiding".
- If i select "navigation", I expect "navigation".
:)
and
...I need the "navigation" for my personal tts "arrivied" message/sound.
Possible?
Ok Andrew,
well I think we agree it is not always that simple to find ALL possible issue's even when performing A LOT OF tests.
I still have to look at your last example, but sorry now I (must) have some garden work to do. (Large garden at my parents home +/- 90 years old both so.....)
My actual conclusion so far was:
In the title: Guiding, Navigation,Brouter.
1. Starts up in Guiding instead of Navigation is yes probably a (small) Locus bug. Found by tests: Only on very special (gpx) tracks without any corner, so long time not a discovered issue.
2. Brouter: A Report: Brouter output is not the explicit cause of that previous problem.
3. Brouter: A Suggestion: The Navigation user experience can be improved by a very small addition and optimalisation in the BRouter output file feed towards the Locus app.
Regards my friend,
Willy.
Ok Andrew,
well I think we agree it is not always that simple to find ALL possible issue's even when performing A LOT OF tests.
I still have to look at your last example, but sorry now I (must) have some garden work to do. (Large garden at my parents home +/- 90 years old both so.....)
My actual conclusion so far was:
In the title: Guiding, Navigation,Brouter.
1. Starts up in Guiding instead of Navigation is yes probably a (small) Locus bug. Found by tests: Only on very special (gpx) tracks without any corner, so long time not a discovered issue.
2. Brouter: A Report: Brouter output is not the explicit cause of that previous problem.
3. Brouter: A Suggestion: The Navigation user experience can be improved by a very small addition and optimalisation in the BRouter output file feed towards the Locus app.
Regards my friend,
Willy.
@Menion
I see your smiling face, but i'm missing your comment B)
@Menion
I see your smiling face, but i'm missing your comment B)
Hello guys,
seems that 3 day long vacation is too long to leave you all alone here :).
My opinion is probably same as gyntas and it's only logical opinion I think. User wants "navigation", he have to get navigation. User wants "guidance", he have to get "guidance". No other options are possible, simple.
Where is a problem? Definitely on Locus side. BRouter computes routing correctly. Probably same behavior may happen with GraphHopper or any other routing service.
Solution? I believe it will work. After every routing, before track is used, Locus do something like "validation". All waypoints and trackpoints are tested and to waypoints is attached/set correct index of trackpoint with same coordinates. And here I've added function that check if last trackpoint has valid waypoint with "destination" command. If not, it's added. Of course only in case, user wants "computed instructions".
I believe this will work.
Because current public version seems to be quite stable, there is no need for another bug-fix version, so there will be enough time to test it in one of next Beta versions.
Thanks all for opinions!
Hello guys,
seems that 3 day long vacation is too long to leave you all alone here :).
My opinion is probably same as gyntas and it's only logical opinion I think. User wants "navigation", he have to get navigation. User wants "guidance", he have to get "guidance". No other options are possible, simple.
Where is a problem? Definitely on Locus side. BRouter computes routing correctly. Probably same behavior may happen with GraphHopper or any other routing service.
Solution? I believe it will work. After every routing, before track is used, Locus do something like "validation". All waypoints and trackpoints are tested and to waypoints is attached/set correct index of trackpoint with same coordinates. And here I've added function that check if last trackpoint has valid waypoint with "destination" command. If not, it's added. Of course only in case, user wants "computed instructions".
I believe this will work.
Because current public version seems to be quite stable, there is no need for another bug-fix version, so there will be enough time to test it in one of next Beta versions.
Thanks all for opinions!
In the end, it won't be so simple. Too much features in connected in Locus.
My important question: is is useful for anyone settings "Compute instructions" in "Navigate to" function? If so, what expect from it?
Because "Navigate to" should logically start navigation in all cases (not guidance). And navigation without navigation instructions does not make sense. For more complex planning should serve "Add new route" function. So from my point of view, this settings should be removed, isn't it? Only what should be interesting here, may be a small warning for older BRouter and Yours services, that navigation instructions will be generated by Locus from shape of track.
In the end, it won't be so simple. Too much features in connected in Locus.
My important question: is is useful for anyone settings "Compute instructions" in "Navigate to" function? If so, what expect from it?
Because "Navigate to" should logically start navigation in all cases (not guidance). And navigation without navigation instructions does not make sense. For more complex planning should serve "Add new route" function. So from my point of view, this settings should be removed, isn't it? Only what should be interesting here, may be a small warning for older BRouter and Yours services, that navigation instructions will be generated by Locus from shape of track.
By the way, latest (current) BRouter profiles has
> assign turnInstructionMode = 1
in every profile, except shortest.brf (Locus use this profile for foot navigation).
So, now Locus (release version) can't start navigation for foot. It start only guidance.
But you can add this line ("assign turnInstructionMode = 1") into shortest.brf to solve this.
By the way, latest (current) BRouter profiles has
> assign turnInstructionMode = 1
in every profile, except shortest.brf (Locus use this profile for foot navigation).
So, now Locus (release version) can't start navigation for foot. It start only guidance.
But you can add this line ("assign turnInstructionMode = 1") into shortest.brf to solve this.
Tests ? Reports ?
A (single) navigation waypoint(s) confirms navtrack generated by intelligent system.
A (single) navpoint(s) prevent Locus to use internal navgenerator based on trackshape.
Locus trackstart not (audio) announced, or autoadding a navpoint Straight is harmless.
Best not at trackend to * prevent a conflict with personal tts "arrived" message or sound.
* If exported to tcx: <Name>Finish <PointType>Generic !
* If exported as gpx 1.1 no such conflict problem, by <locus:rtePointAction>24</locus:rtePointAction>
Actual situation in Locus testversion 3.17.2.4.
"Navigation to" function: Navpoints auto added at trackstart AND at trackend.
"Route and Measure" function: No navpoint(s) added ?
Suggest: Autoadd a single navpoint at trackstart ONLY.
Attachment: Navigateto and routeandmeasure example.
Tests ? Reports ?
A (single) navigation waypoint(s) confirms navtrack generated by intelligent system.
A (single) navpoint(s) prevent Locus to use internal navgenerator based on trackshape.
Locus trackstart not (audio) announced, or autoadding a navpoint Straight is harmless.
Best not at trackend to * prevent a conflict with personal tts "arrived" message or sound.
* If exported to tcx: <Name>Finish <PointType>Generic !
* If exported as gpx 1.1 no such conflict problem, by <locus:rtePointAction>24</locus:rtePointAction>
Actual situation in Locus testversion 3.17.2.4.
"Navigation to" function: Navpoints auto added at trackstart AND at trackend.
"Route and Measure" function: No navpoint(s) added ?
Suggest: Autoadd a single navpoint at trackstart ONLY.
Attachment: Navigateto and routeandmeasure example.
Replies have been locked on this page!