I would like to get this completed and understand all I can and move on.
https://help.locusmap.eu/topic/27390-time-to-target-is-always-wrong-not-even-close
can someone explain fully this strangeness?
So do I have to create a navigation, set to car profile, brouter, run it at highway speeds 60 mph. THEN....the next time I load a "TRACK" it will display the correct time???
I know locus does not know the roads, but brouter does and if I set it to car the time to target should be closer shouldn't it???
Somehow Michael got my track to display properly but I never heard back from him how exactly he did it. Hopefully someone else can shed some light on how this works...or point me to some links that better explain it...TIA
The same question
Hi Morgan,
1) estimated travel time - Locus Map is primarily a navigation app for hiking, biking and other outdoor activities. Therefore, only hiking/biking/XC skiing is in this feature
2) long estimated time for navigated route - Locus calculates the ETA according to the speed of the previously navigated routes in the selected routing profile. Most probably, you planned a route with a car profile and then you walked along it. See how it estimated the route in my phone - both navigation and guidance have the same ETT:
Hi Morgan,
1) estimated travel time - Locus Map is primarily a navigation app for hiking, biking and other outdoor activities. Therefore, only hiking/biking/XC skiing is in this feature
2) long estimated time for navigated route - Locus calculates the ETA according to the speed of the previously navigated routes in the selected routing profile. Most probably, you planned a route with a car profile and then you walked along it. See how it estimated the route in my phone - both navigation and guidance have the same ETT:
Hello morgan,
Michal does not write the answer because he wasn't sure why this happens. So he forwarded this task to me as the main app developer. I'm currently a little buried by many tasks, so I wasn't able to look at it deeper yet, sorry. Will look at it in the next few days and let you know here. Thanks for understanding.
Hello morgan,
Michal does not write the answer because he wasn't sure why this happens. So he forwarded this task to me as the main app developer. I'm currently a little buried by many tasks, so I wasn't able to look at it deeper yet, sorry. Will look at it in the next few days and let you know here. Thanks for understanding.
great...thanks
great...thanks
Hi,
I'm investigating what's happening to you and have to say, that current system in the app is really stupid. In your case, track does not have any info whether it was created for the car or bike (etc) and app does not allow to choose which navigation type should be used because it expect, everything is already included in the track. In case, you create the route directly in the app, this should not happen because all is correctly set during creation and times should really be quite accurate.
Isn't using app internal or the web route planner an option?
If not, there is currently option to include manually required info into every GPX file by any text editor, that may fix this issue. Let me know if you wants to know more.
Because should be of course to improve this directly in the app. It anyway needs a lot bigger change to make this work correctly. I'll definitelly want to do something with it soon ...
Hi,
I'm investigating what's happening to you and have to say, that current system in the app is really stupid. In your case, track does not have any info whether it was created for the car or bike (etc) and app does not allow to choose which navigation type should be used because it expect, everything is already included in the track. In case, you create the route directly in the app, this should not happen because all is correctly set during creation and times should really be quite accurate.
Isn't using app internal or the web route planner an option?
If not, there is currently option to include manually required info into every GPX file by any text editor, that may fix this issue. Let me know if you wants to know more.
Because should be of course to improve this directly in the app. It anyway needs a lot bigger change to make this work correctly. I'll definitelly want to do something with it soon ...
WORKFLOW: I use locus to follow tracks that I get online. If you Google “MABDR” or “ NEBDR” you can download these examples. BRD=Back Country Discovery Route”. These are single gpx files with many sections. Locus does a superb job importing these correctly as many other apps do not.
These are multi day motorcycle tracks with a preference to off-road.
Since I do not create these I have no control over what’s embedded in them. I do believe they are tracks not routes.
I would prefer to run these tracks using navigation because I prefer the next turn symbol, strong pink line and strong cursor over what guidance does.
So all of this workflow is perfect except for the time to target being so far off…AND… having the ability to eventually navigate to a waypoint (not endpoint) using only the track no recalculation would be nice…but more important is getting time to target to actually follow the “car” profile of speed and have a closer time to target. I know when running the track it will become more accurate.
Yes I would like to know how to fix the gpx files in the interim while you resolve this in v4. I suspect it is editing with a text editor and replacing embedded tags.
Ps… can you link to a part of the user manual that explains the functions of the attached icons which show up in track point. Click on 1 then click on 2 and it actually recalculates to that trackpoint which is almost what I want ...ie... "intermediate trackpoint" but it recalculates the route and does not just remove the end. Where is this in the manual???
thanks,
WORKFLOW: I use locus to follow tracks that I get online. If you Google “MABDR” or “ NEBDR” you can download these examples. BRD=Back Country Discovery Route”. These are single gpx files with many sections. Locus does a superb job importing these correctly as many other apps do not.
These are multi day motorcycle tracks with a preference to off-road.
Since I do not create these I have no control over what’s embedded in them. I do believe they are tracks not routes.
I would prefer to run these tracks using navigation because I prefer the next turn symbol, strong pink line and strong cursor over what guidance does.
So all of this workflow is perfect except for the time to target being so far off…AND… having the ability to eventually navigate to a waypoint (not endpoint) using only the track no recalculation would be nice…but more important is getting time to target to actually follow the “car” profile of speed and have a closer time to target. I know when running the track it will become more accurate.
Yes I would like to know how to fix the gpx files in the interim while you resolve this in v4. I suspect it is editing with a text editor and replacing embedded tags.
Ps… can you link to a part of the user manual that explains the functions of the attached icons which show up in track point. Click on 1 then click on 2 and it actually recalculates to that trackpoint which is almost what I want ...ie... "intermediate trackpoint" but it recalculates the route and does not just remove the end. Where is this in the manual???
thanks,
Locus Planner & expected (arrival) time (by avg speed) to the navigation target point(s).
Have a test pse. Locus trackrecord activated.
A. Jump on the motorbike and have a fast drive around. Save track record.
Load your navigation track > start navigate > observe time to finish.
B. Have a walk with the dog. Save track record.
Load your navigation track > start navigate > observe time to finish.
Locus Planner & expected (arrival) time (by avg speed) to the navigation target point(s).
Have a test pse. Locus trackrecord activated.
A. Jump on the motorbike and have a fast drive around. Save track record.
Load your navigation track > start navigate > observe time to finish.
B. Have a walk with the dog. Save track record.
Load your navigation track > start navigate > observe time to finish.
Thanks 0709! I guess this is what Michael was noting and I just did not understand. So the most recent RECORDED TRACK's average speed it what determines how the next navigation time to target displays???
I drove @8 miles 50-70mph and then loaded and began navigating my 310 mile track linked in this thread and it noted roughly 6 hrs which is at least close. I then drove the last .5 miles home at @3-5mph and loaded the same 310 mile track and it said almost 48 hrs. I never knew this...thank you both. It would be good if one could select car profile and have it just automatically come close...or run the track (in my case from another app...most likely basecamp) through an "analysis pass" in locus using lorouter/broutser which can see the roads and speeds and therefore give a very accurate time estimate/. This analysis pass should not recalculate the actual track in any way.
Thanks 0709! I guess this is what Michael was noting and I just did not understand. So the most recent RECORDED TRACK's average speed it what determines how the next navigation time to target displays???
I drove @8 miles 50-70mph and then loaded and began navigating my 310 mile track linked in this thread and it noted roughly 6 hrs which is at least close. I then drove the last .5 miles home at @3-5mph and loaded the same 310 mile track and it said almost 48 hrs. I never knew this...thank you both. It would be good if one could select car profile and have it just automatically come close...or run the track (in my case from another app...most likely basecamp) through an "analysis pass" in locus using lorouter/broutser which can see the roads and speeds and therefore give a very accurate time estimate/. This analysis pass should not recalculate the actual track in any way.
Thanks for this. It's good to know others want this too. Thanks. Hopefully devs will improve this.
Thanks for this. It's good to know others want this too. Thanks. Hopefully devs will improve this.
Replies have been locked on this page!