This object is in archive!
Navigation: Route priority vs Strict route navigation vs Snap to track
Answered
When navigating, I have to frequently and repeatedly "think deeply" about exact difference between Route priority / Strict route navigation / Snap to track in the Navigation settings manual page .
Could you elaborate it more, here and/or in the manual ? As their meaning seems to be very confusingly similar, each taking the route as the goal, but each by a slightly different way.
The same question
well, the terminology in this area is a bit tricky, we do admit it. Nevertheless, we come out of years of user-based usage no matter if it's scientifically correct. Anyway, you're right with that nautical strict navigation - I was referring to strict guidance. All the same, many users demanded this strict navigation to be implemented years ago so we have to cope with it relating to new features as e.g. two kinds of route recalculation. And we surely expect further discussion about the terminology issue :)
well, the terminology in this area is a bit tricky, we do admit it. Nevertheless, we come out of years of user-based usage no matter if it's scientifically correct. Anyway, you're right with that nautical strict navigation - I was referring to strict guidance. All the same, many users demanded this strict navigation to be implemented years ago so we have to cope with it relating to new features as e.g. two kinds of route recalculation. And we surely expect further discussion about the terminology issue :)
Hi Poutnik,
Route priority - an option of recalculating your navigation route when you deviate from the original line - Locus tries to get back to the original line as soon as possible and on the nearest place - the line (route) matters.
Strict route navigation - each route consists of a chain of routepoints (sort of breadcrumbs). This option navigates strictly from one routepoint to another. When you make a deviation, it tries to get you to the last omitted routepoint. Useful e.g. for nautical navigation where its vital to keep your course.
Snap to track - rather graphic feature. The navigation cursor is always positioned on the route line despite real GPS position can be slightly off the line e.g. due to poor signal. Used mainly in car navigation so that the driver is not disturbed by the fact that he drives a few meters from the line.
Hi Poutnik,
Route priority - an option of recalculating your navigation route when you deviate from the original line - Locus tries to get back to the original line as soon as possible and on the nearest place - the line (route) matters.
Strict route navigation - each route consists of a chain of routepoints (sort of breadcrumbs). This option navigates strictly from one routepoint to another. When you make a deviation, it tries to get you to the last omitted routepoint. Useful e.g. for nautical navigation where its vital to keep your course.
Snap to track - rather graphic feature. The navigation cursor is always positioned on the route line despite real GPS position can be slightly off the line e.g. due to poor signal. Used mainly in car navigation so that the driver is not disturbed by the fact that he drives a few meters from the line.
Hm, good description.
So route priority is like not strict route following*) , returning to the nearest location of the route. I suppose the passing the viapoint still takes preference, if going to the nearest route point would mean missed a viapoint.
In context of nautical navigation, you certainly mean Strict route navigation in Guidance section, not in Navigation section, as I suppose there are no nautical routers. For engine routing, I guess it may be less useful.
* I think Strict route navigation should be renamed to Strict route following, as used in both navigation and guidance context. Navigation should be reserved for routing. Navigation is unluckily used in LocusMaps in 2 meanings, navigation=engine route generation and navigation=giving directions. Many users mix the meanings, complaining about problems.
Hm, good description.
So route priority is like not strict route following*) , returning to the nearest location of the route. I suppose the passing the viapoint still takes preference, if going to the nearest route point would mean missed a viapoint.
In context of nautical navigation, you certainly mean Strict route navigation in Guidance section, not in Navigation section, as I suppose there are no nautical routers. For engine routing, I guess it may be less useful.
* I think Strict route navigation should be renamed to Strict route following, as used in both navigation and guidance context. Navigation should be reserved for routing. Navigation is unluckily used in LocusMaps in 2 meanings, navigation=engine route generation and navigation=giving directions. Many users mix the meanings, complaining about problems.
well, the terminology in this area is a bit tricky, we do admit it. Nevertheless, we come out of years of user-based usage no matter if it's scientifically correct. Anyway, you're right with that nautical strict navigation - I was referring to strict guidance. All the same, many users demanded this strict navigation to be implemented years ago so we have to cope with it relating to new features as e.g. two kinds of route recalculation. And we surely expect further discussion about the terminology issue :)
well, the terminology in this area is a bit tricky, we do admit it. Nevertheless, we come out of years of user-based usage no matter if it's scientifically correct. Anyway, you're right with that nautical strict navigation - I was referring to strict guidance. All the same, many users demanded this strict navigation to be implemented years ago so we have to cope with it relating to new features as e.g. two kinds of route recalculation. And we surely expect further discussion about the terminology issue :)
I am sure LocusMap is result of years of users-developers interaction. And I am sure LocusMap a a top product in this area - and other areas too.
Avoiding confusion makes sense even out of strict scientific terminology ( You guessed right - I am a graduated scientist ;) ). Some term glossary or more verbose manual settings description would help .
BTW, it seems to me, that Strict route navigation in navigation context may not matter either, if no autorecalculation is set.
I am sure LocusMap is result of years of users-developers interaction. And I am sure LocusMap a a top product in this area - and other areas too.
Avoiding confusion makes sense even out of strict scientific terminology ( You guessed right - I am a graduated scientist ;) ). Some term glossary or more verbose manual settings description would help .
BTW, it seems to me, that Strict route navigation in navigation context may not matter either, if no autorecalculation is set.
We'll see to it... and Strict route navigation with no autorecalculation matters - Locus doesn't recalculate but guides to the omitted routepoint. Therefore we can't implement your radiobutton proposal
We'll see to it... and Strict route navigation with no autorecalculation matters - Locus doesn't recalculate but guides to the omitted routepoint. Therefore we can't implement your radiobutton proposal
..Hmm , I see. I was just asking and reviewing my understanding.. :)
So NO autorecalculation with Strict route navigation OFF navigates to the closest routepoint no matter if I missed the previous ones, correct ?
I think the more detailed comment of settings combination could find its place in the manual. :)
Thank a lot for the explanation and your time. You can close it as answered.
..Hmm , I see. I was just asking and reviewing my understanding.. :)
So NO autorecalculation with Strict route navigation OFF navigates to the closest routepoint no matter if I missed the previous ones, correct ?
I think the more detailed comment of settings combination could find its place in the manual. :)
Thank a lot for the explanation and your time. You can close it as answered.
Replies have been locked on this page!