Navigation vs. Guidance On GPX Imported Track?
Hello,
Please note that this question only pertains to the above operation on an imported GPX track. Assume that the GPX track is a bread crumb trail only without any specialy crafted turn directions in the file.
Guidance will pseudo navigate by guessing where the change of directions might be a turn. It does a good job at finding just about all turns but it will also alert you to just curves in the road which is still tolerable.
So what does Navigation do under these same circumstances? Based on other device and apps I would expect nothing since there are no TBT commands in the GPX file. However, looking at the Locus documentation it would seem to suggest that Navigation behaves the same as Guidance under these conditions. Is this correct? I actually haven't tried it yet.
Thanks,
Steve
The same question
Is correct. Pseudo Navigation or pseudo Guiding based on trackshape.
Some users prefer Guiding screen method others (inclusive me) prefer Navigation presentation.
Navigation orders by trackshape = The older primitive pseudo method.
I know, as I was one of the promotors of this method years ago, as at that time there was no other or better alternative.
On CURVY roads however it does generate multiple unnecessary turn commands even when there is no junction. Reports based on many tests by experienced (MTB) users = It is a nightmare, by a too talky navigation result.
Advise: In Navigation > advanced setting > Frequency of orders > Set: NONE !
Better: Redesign a track on a real (B)_router machine or website (knows the junctions) to attach only correct minimal total commands.
Do not use unless you know what and *why you are selecting this mode inclusive the negatives !
* For example : Too lazy to reproduce a design by retracing function over the original to be used as a template.
Is correct. Pseudo Navigation or pseudo Guiding based on trackshape.
Some users prefer Guiding screen method others (inclusive me) prefer Navigation presentation.
Navigation orders by trackshape = The older primitive pseudo method.
I know, as I was one of the promotors of this method years ago, as at that time there was no other or better alternative.
On CURVY roads however it does generate multiple unnecessary turn commands even when there is no junction. Reports based on many tests by experienced (MTB) users = It is a nightmare, by a too talky navigation result.
Advise: In Navigation > advanced setting > Frequency of orders > Set: NONE !
Better: Redesign a track on a real (B)_router machine or website (knows the junctions) to attach only correct minimal total commands.
Do not use unless you know what and *why you are selecting this mode inclusive the negatives !
* For example : Too lazy to reproduce a design by retracing function over the original to be used as a template.
What precisely does happen ?
Locus puts a pseudo track inclusive the generated navigation points based on the trackshape on top of the display.
Find out by a tap onto the newly presented navigation track.
Find by a zoom in : Locus shows 2 tracks instead of only the imported one.
1. (Bottom track )The original imported original 'naked" one. (no navwaypoints)
2. (Top track) This new ( The track name = Navigation) pseudo generated track inclusive the generated pseudo navwaypoints.
After a zoom in and you will notice that the pseudo track is not perfectly aligned with the original track.
Track 2 is used for the navigation function!
Navigation command generation is by this Pseudo track inclusive pseudo navigationwaypoints.
Track 2 can even be exported inclusive the pseudo navigation waypoints !
By the actual 3.44.x version !
The pseudo track color is defined by by the Locus default track color setting.
Find the Locus track default setting in General settings > Points and Tracks >
After new locus install:
Default original is by blue line, but users can change the default track color !
Complex ? Yes. Sorry. It is what it is.
What precisely does happen ?
Locus puts a pseudo track inclusive the generated navigation points based on the trackshape on top of the display.
Find out by a tap onto the newly presented navigation track.
Find by a zoom in : Locus shows 2 tracks instead of only the imported one.
1. (Bottom track )The original imported original 'naked" one. (no navwaypoints)
2. (Top track) This new ( The track name = Navigation) pseudo generated track inclusive the generated pseudo navwaypoints.
After a zoom in and you will notice that the pseudo track is not perfectly aligned with the original track.
Track 2 is used for the navigation function!
Navigation command generation is by this Pseudo track inclusive pseudo navigationwaypoints.
Track 2 can even be exported inclusive the pseudo navigation waypoints !
By the actual 3.44.x version !
The pseudo track color is defined by by the Locus default track color setting.
Find the Locus track default setting in General settings > Points and Tracks >
After new locus install:
Default original is by blue line, but users can change the default track color !
Complex ? Yes. Sorry. It is what it is.
Ha! This is EXACTLY what I am seeing with the incorrect line style in Guidance. There are indeed TWO tracks nearly one on top of each other. The issue is that UNLIKE your zoom in track above BOTH tracks are the SAME line style. Neither line style matches the original OR the solid blue above.
Similar thing happens with Navigation both tracks have the SAME track style but different than expected based on track style settings.
I bet MOST users don't even realize that this is happening. The only reason that I noticed and didn't like it was that the dark blue hides the small black dot rest stop waypoints when using RWGPS generated GPX files.
Ha! This is EXACTLY what I am seeing with the incorrect line style in Guidance. There are indeed TWO tracks nearly one on top of each other. The issue is that UNLIKE your zoom in track above BOTH tracks are the SAME line style. Neither line style matches the original OR the solid blue above.
Similar thing happens with Navigation both tracks have the SAME track style but different than expected based on track style settings.
I bet MOST users don't even realize that this is happening. The only reason that I noticed and didn't like it was that the dark blue hides the small black dot rest stop waypoints when using RWGPS generated GPX files.
Replies have been locked on this page!