Guiding along a track: Distance to next point not computed
In v3.0.2 I manually created a track, saved it, chose "guide on" and Locus did guide me along the track. That worked fine :)
I tried the different settings for the guiding bar, e.g. I set "distance to next waypoint" as shown in https://www.dropbox.com/s/ovwjol0m111euuo/2014-06-20-19-38-01_Locus_Screenshot_SettingForButtonInBar.png
but that did not work: Locus showed "unknown" even tough it must have known it because Locus did switch correctly to the next track point when reaching a track point, and it displayed the distance to the next point at the guiding line (small arrows / 2.4km in https://www.dropbox.com/s/sp0chd7p6nndke7/2014-06-20-19-38-13_Locus_Screenshot_DistanceShownInMapButNotInBar.png) Same applied to "time to next waypoint" etc. All info for the target worked and match the end of the track.
=> Do I have to do/add/set something special? Or is this a bug?
The same problem 
Hello,
here is a small missunderstanding.
Try to manually create a track and use bottom "Navigate" button, so Locus also use online service to compute "real" waypoints (points with navigation orders).
Then this top menu will display correct values (except time, where is known problem with compute) for current waypoint.
What you want is value for a simple "point" on track, but not a waypoint. And this currently do not work as you want. Mainly because usually your track is from few hunderds, maybe thousands of these points that create a shape of track and these points aren't important for you.
Hello,
here is a small missunderstanding.
Try to manually create a track and use bottom "Navigate" button, so Locus also use online service to compute "real" waypoints (points with navigation orders).
Then this top menu will display correct values (except time, where is known problem with compute) for current waypoint.
What you want is value for a simple "point" on track, but not a waypoint. And this currently do not work as you want. Mainly because usually your track is from few hunderds, maybe thousands of these points that create a shape of track and these points aren't important for you.
Menion, if "distance to next waypoint" is only designed to work with navigation, why does Locus offer it also for guiding? ;-) If it's available in the drop down, users expect it will be working under current circumstances (guiding).
I fully agree that "distance to next waypoint" is pretty useless for a recorded track (e.g. every 10m a point). It makes sense for manually created tracks contain only "relevant" points, e.g. where I need to change ways. The computation can probably be done with the same algorithm as to "next navigation point". If it's more work or not fitting the concept, just disable the "forbidden" options in the drop down :-) Cheers, Georg
Menion, if "distance to next waypoint" is only designed to work with navigation, why does Locus offer it also for guiding? ;-) If it's available in the drop down, users expect it will be working under current circumstances (guiding).
I fully agree that "distance to next waypoint" is pretty useless for a recorded track (e.g. every 10m a point). It makes sense for manually created tracks contain only "relevant" points, e.g. where I need to change ways. The computation can probably be done with the same algorithm as to "next navigation point". If it's more work or not fitting the concept, just disable the "forbidden" options in the drop down :-) Cheers, Georg
You are of course right.
On second side, imagine you compute new
track also with navigation orders, but in the end, you do not start
"Navigation", but just "Guiding". In this case, you'll have waypoints on
track (on places where are navigation orders), so this value should
work correctly in this case.ą
It is also possible to show/hide
this option based on current track, but I personally do not like such
hiding when it's not perfectly clear why it's hidden ... it's another of
hard moments in app developing :)
You are of course right.
On second side, imagine you compute new
track also with navigation orders, but in the end, you do not start
"Navigation", but just "Guiding". In this case, you'll have waypoints on
track (on places where are navigation orders), so this value should
work correctly in this case.ą
It is also possible to show/hide
this option based on current track, but I personally do not like such
hiding when it's not perfectly clear why it's hidden ... it's another of
hard moments in app developing :)
Replies have been locked on this page!