Feature request around navigation
1.When I navigate an imported track(.gpx) and I'm not yet at the actual location(near the track) ...the position of the actual track on the map is not displayed(despite the fact that I marked all to be visible on the map--the eye sign--), only the navigation to the start of the track is displayed. It would be very usefull to also see the actual track form on the map, beside the roads to the start of the track.
2.I have a feature request:
When navigating to a destination, the big arrow in the left displays the distance to the first point where the change in direction is needed. Could you also implement in this same arrow box(smaller font) to be displayed the time needed to reach this first point?You could take into consideration for this,the average moving speed for the last 15 minutes or so..
The same question
Hi,
1. could you please provide a screenshot of the situation? We can't simulate your problem.
2. you can turn the "time to next junction" figure in the field next to the "arrow" box - tap the field and select from the roll-out
Hi,
1. could you please provide a screenshot of the situation? We can't simulate your problem.
2. you can turn the "time to next junction" figure in the field next to the "arrow" box - tap the field and select from the roll-out
This is the video of problem
This is the video of problem
Good day Marius,
thank you for additional videos.
I see one different point of view on track selected for navigation. Locus Map consider selected track as a way, how to get to target. If you enable recalculation and new track is computed (by the way, you have selected really really low distance for recalculation. Because of this, Locus Map compute track for even a 70m! which is not recommended because of GPS accuracy), this new track define new way to your target. Previous track is not needed anymore. If you would like to stick with original track, disable recalculation. If you really need to see original track on map even with enabled recalculation, just create and display copy of this track. I have no better solution for you. Btw. suggested "Route priority" by Michal should work, maybe your track is really just too short. And last note ... in next version, Locus Map will recalculate to start point of track in case, you not yet pass it. It may helps in your case here.
Good day Marius,
thank you for additional videos.
I see one different point of view on track selected for navigation. Locus Map consider selected track as a way, how to get to target. If you enable recalculation and new track is computed (by the way, you have selected really really low distance for recalculation. Because of this, Locus Map compute track for even a 70m! which is not recommended because of GPS accuracy), this new track define new way to your target. Previous track is not needed anymore. If you would like to stick with original track, disable recalculation. If you really need to see original track on map even with enabled recalculation, just create and display copy of this track. I have no better solution for you. Btw. suggested "Route priority" by Michal should work, maybe your track is really just too short. And last note ... in next version, Locus Map will recalculate to start point of track in case, you not yet pass it. It may helps in your case here.
Thanks Menion for the tips.
I want to ask what is wrong with 30 m distance for auto-recalculation of route? If I'm on my bike in a city and I need to navigate to target..and I miss some road., I need Locus to recalculate as soon as possible to the new route(there are cross-roads every 15 meters even).If I set to 150 m recalculation..I will miss many cross-roads and streets till Locus recalculates.What is the best practice?
About "Route priority" I think the problem is not with the lenght of the track.I will post another video to exemplify.
I think that recalculation and disappearing of the track has much to do with the fact that most my tracks are round-circuits where the start point is near the end point of the route, despite the track can have 15 km.
Thanks Menion for the tips.
I want to ask what is wrong with 30 m distance for auto-recalculation of route? If I'm on my bike in a city and I need to navigate to target..and I miss some road., I need Locus to recalculate as soon as possible to the new route(there are cross-roads every 15 meters even).If I set to 150 m recalculation..I will miss many cross-roads and streets till Locus recalculates.What is the best practice?
About "Route priority" I think the problem is not with the lenght of the track.I will post another video to exemplify.
I think that recalculation and disappearing of the track has much to do with the fact that most my tracks are round-circuits where the start point is near the end point of the route, despite the track can have 15 km.
Hello, in city it is even worst. GPS accuracy in city is a lot worst because of buildings, then on open space. So with 30m, you should get recalculation quite often.
Problem with lower values are, that Locus currently detect if recalculation is needed only by change of coordinates. It should be better to also use orientation by sensors to detect current movement, but it do not happen now.
Before some more tests, please wait on next Locus Map version this/maybe start of next week. There were some changes in recalculation system so it may helps. If "route priority" won't work with next version, write me, attach me some sample GPX track and I'll for sure check if more precisely. Thanks for understanding.
Hello, in city it is even worst. GPS accuracy in city is a lot worst because of buildings, then on open space. So with 30m, you should get recalculation quite often.
Problem with lower values are, that Locus currently detect if recalculation is needed only by change of coordinates. It should be better to also use orientation by sensors to detect current movement, but it do not happen now.
Before some more tests, please wait on next Locus Map version this/maybe start of next week. There were some changes in recalculation system so it may helps. If "route priority" won't work with next version, write me, attach me some sample GPX track and I'll for sure check if more precisely. Thanks for understanding.
When navigate the track from proximity(close distance) , situation is OK now ,Locus guides me to the Start of the track.
With the new version of Locus, situation is unchanged when I try to navigate to the track from some distance away (700 meters or 190 km away) . Even if I choose Route priority , or even No automatic recalculation in Navigation options, Locus routes me to the End point of the track to be navigated, and NOT to the Start point of the track.
From my point of view, if i choose to navigate a track(.gpx) , Locus should stick as close as possible to the shape of the track,bringing me to the closest point beginning from the Start point of the track.
If I just wanted to get quick to the End of the track,I can navigate directly to the End point(choose the position on the map --as waypoint-- of the End point of track and locus would bring me there), but if I navigate a track, then I want to follow as close as possible from the Start to the end.
Also when locus says "calculating" there is an error message sometimes : "target island detected for section 0"...
I attach 2 tracks for you to verify
For the last track 09.10.2016 when navigating with route priority , locus says "to-position not mapped in existing datafile" ..What does it mean?
When navigate the track from proximity(close distance) , situation is OK now ,Locus guides me to the Start of the track.
With the new version of Locus, situation is unchanged when I try to navigate to the track from some distance away (700 meters or 190 km away) . Even if I choose Route priority , or even No automatic recalculation in Navigation options, Locus routes me to the End point of the track to be navigated, and NOT to the Start point of the track.
From my point of view, if i choose to navigate a track(.gpx) , Locus should stick as close as possible to the shape of the track,bringing me to the closest point beginning from the Start point of the track.
If I just wanted to get quick to the End of the track,I can navigate directly to the End point(choose the position on the map --as waypoint-- of the End point of track and locus would bring me there), but if I navigate a track, then I want to follow as close as possible from the Start to the end.
Also when locus says "calculating" there is an error message sometimes : "target island detected for section 0"...
I attach 2 tracks for you to verify
For the last track 09.10.2016 when navigating with route priority , locus says "to-position not mapped in existing datafile" ..What does it mean?
Hi,
when you want to be navigated to the START of the route from some distance, don't use navigation along the route but select just the starting point (tap the route, select trackpoint 1, create a new point there and select "navigate to"). Otherwise Locus will calculate your way to the nearest point of the route. When you're on the route and want to be navigated along it, set you autorecalculation on the route priority - this way Locus will try to keep you on the route, i.e. to the nearest available routepoint and not to the target point.
The announcements you mention are related to the used routing engine.
Hi,
when you want to be navigated to the START of the route from some distance, don't use navigation along the route but select just the starting point (tap the route, select trackpoint 1, create a new point there and select "navigate to"). Otherwise Locus will calculate your way to the nearest point of the route. When you're on the route and want to be navigated along it, set you autorecalculation on the route priority - this way Locus will try to keep you on the route, i.e. to the nearest available routepoint and not to the target point.
The announcements you mention are related to the used routing engine.
Thank you 0709 for the time to explain me.
It seems you are wright: I would like the best from the both worlds: Strict Navigation in perfect order to the (Must_Pass) Priority_Points, in cooperation with the auto recalculate function to Priority_Points
But I will not start "New Idea" in Locus help desk because I already know what menion and the rest of the team is thinking about it.
So I think I remain at Michal solution now.
Thank you 0709 for the time to explain me.
It seems you are wright: I would like the best from the both worlds: Strict Navigation in perfect order to the (Must_Pass) Priority_Points, in cooperation with the auto recalculate function to Priority_Points
But I will not start "New Idea" in Locus help desk because I already know what menion and the rest of the team is thinking about it.
So I think I remain at Michal solution now.
Hi Marius,
to sum it up, Locus knows just two kinds of navigation - 1) navigation TO a point (route to the point is calculated by a routing service) and 2) navigation ALONG a route (route is ready-made - clicked/drawn/planned by the user in Locus or imported from somewhere else outside Locus). So if you are 2 kms from your route and tell Locus "navigate me along it", Locus directs you to the nearest routepoint of the route - either by guidance (a simple beeline) or navigation (the way to the nearest routepoint is calculated along available roads in OSM dataset).
Which means:
Locus does not know navigation TO a route - no one (except you) has ever wanted us to implement such a thing. However, Locus is so complex that it offers a whole range of workarounds how to achieve even the strangest wishes of its users ;) I mentioned one of them. Good luck :)
Hi Marius,
to sum it up, Locus knows just two kinds of navigation - 1) navigation TO a point (route to the point is calculated by a routing service) and 2) navigation ALONG a route (route is ready-made - clicked/drawn/planned by the user in Locus or imported from somewhere else outside Locus). So if you are 2 kms from your route and tell Locus "navigate me along it", Locus directs you to the nearest routepoint of the route - either by guidance (a simple beeline) or navigation (the way to the nearest routepoint is calculated along available roads in OSM dataset).
Which means:
Locus does not know navigation TO a route - no one (except you) has ever wanted us to implement such a thing. However, Locus is so complex that it offers a whole range of workarounds how to achieve even the strangest wishes of its users ;) I mentioned one of them. Good luck :)
Replies have been locked on this page!