On Tue, Mar 23, 2021 at 08:14:54AM -0500, Bob Gambrel wrote:
On Tue, Mar 23, 2021 at 7:13 AM [email protected] <[email protected]>
wrote:
with a very small experience as a rookie user, i have to say the follow
- let wa say that we spend a lot of time into a navigation system,
small or big, powerful or light, no matter the operating system or
the running application. The user with experience or not, draw
after a lot of effort a route and at the end export this route as
gpx file ....... "t*his is our choice*"
after this action, we or someone else,* MUST* have the opportunity
to import into his navigation system this gpx file and make "follow
the route" at 100% . For me this is the logical action. It seems
that other users or companies disagree with this action.
It sure sounds nice to follow the route at 100%. What happens if the
human trying to follow the route gets off the route as planned? What
should the navigation software do?
Give up? Human made a mistake. If he can make it back to the route HE/SHE
planned I will carry on.
Try to give human directions to get to the finish the easiest/shortest
possible way?
Try to give the human directions to get to the start the easiest/shortest
possible way?
Try to give the human directions to get to the route (anywhere) the
shortest/easiest way?
There is another possible option:
5) Try to return the human back to the exact point where they deviated
from the planned gpx route.
For the last one, what if the easiest to get to is closer to the finish
than the start and by doing so the human (who made the mistake in the first
place) ends up bypassing a lot of the route he/she carefully planned?
There are probably other possible things the navigation tool can do.
Yes, and this means that a different one of the five options will be
best in different senarios, and to different users. If the route was
merely meant to get to the destination, then your #2 is likely the best
choice. If the route was meant as a sight-seeing tour, then my option
#5 might be best, lest the human miss the sights along the route.
To satisify every possible use case, each time the human deviated from
the route, the navigator would have to ask which method it should use
to rejoin the route -- because the choice might be different each time
a deviation occurs. And asking "how do you want me to rejoin the
route" each time would, for many, quickly become very irritating.
One of the problems with trying to use gpx files for route sharing is
that this was never the intent of a gpx file, so it is a poor container
for the necessary data for storing a route that is intended to be
navigated in the future. GPX was meant to record where one had been
(i.e., record history), not instruct you how to get to a destination.
Yet gpx is generally the only data format that multiple different
navigation systems can commonly consume. So it has become the defacto
route sharing file format, even though that was never meant to be its
usecase.
--
You received this message because you are subscribed to the Google Groups
"OsmAnd" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/osmand/20210323133603.GW1397%40d820.dp100.com.
