New Topic

Locus Map - help desk Topic Question Locus Map (Android)

This object is in archive!

Category Locus Map (Android)

Tags Route planner

Comments 10

Subscribers 4

Votes 1

Unrealistic time estimate on route planner.

Tomas SVK shared this question ago

Answered

Is it possible to set different rates for walking uphill and downhill so it reflects more realistic time estimate for route planner in hiking and running? As of now estimations for longer tracks are unrealistic.

The same question

Replies (1)

Michal Stupka ●

Hi Tomas,

ETA in the bottom bar of the route planner is just approximate. For more accurate ETA, please go to the planner menu > Travel time and select what type of activity you plan the route for. Custom setting of different rates for walking uphill and downhill is not possible.

best regards

Michal

URL

Dmitrii Kochergin ●

Is it possible to update the way ETA in the bottom bar of the Route Planner being calculated - aligned with the option chosen in Menu > "Estimated Travel Time" pop-up? 'cause I e.g. chose Type as "Road racer", get there 1h:30m for 43,5 km trip, but still 6h:14m remains in the bar when I return to main Route Planner view.

URL

Michal Stupka ●

Hi Dmitrii,

6h:14m with road racing profile? What profile do you use in the route planner? What router?

URL

Dmitrii Kochergin ●

Hi Michal,

Profile = "Racing", Router = GraphHopper.

I re-checked it now, and for 5,3 km I got 45 minutes (which is ok for walking I believe).

URL

Michal Stupka ●

I'm sorry but I can't replicate your problem. GraphHopper, road racing profile, 40,2km, 1:58 hours - that seems quite normal (ETA from the menu is 1:36)

/dda617675b29e5efa021da8eeff09f27

URL

Dmitrii Kochergin ●

There seems to be a bug I believe. 7e8d0d3aaf9b48a167937f3c034ab827

URL

Michal Stupka ●

Hi Dmitrii,

this is not a bug - there is a personal factor as well. The calculation of the ETA in the graph counts in also the history of the speed of your previous usage of the profile. Not that you rode your bike so slowly but maybe you accidentally planned a route with the road bike profile and then you navigated it on foot. The calculation takes into account cca an hour of the speed history so after a few more bike trips the ETA will be more accurate.

URL

freischneider ●

You notice that this system is not optimal. It would be better if you could save the speed yourself in the profile. The previous speed of use can be displayed as a suggestion. But the user should determine it himself.

URL

freischneider ●

There is already a suggestion for improvement. If you are interested, please vote.

https://help.locusmap.eu/topic/estimated-travel-time

https://help.locusmap.eu/topic/make-profile-for-estimated-travel-time-choosable

URL

Dmitrii Kochergin ●

>> The calculation takes into account cca an hour of the speed history so after a few more bike trips the ETA will be more accurate.

The only problem with this - I use Locus in biking as a route planning tool (cycling tracking is performed by Garmin Edge), as a tracker Locus is used only for hiking. So I seem have no chance to improve my ETA accuracy :)

URL