This object is in archive! 

Time to target incorrect for recording profile

Bob Hawkins shared this problem 6 years ago
Closed

I have GraphHopper installed with LocusMap Pro 3.18.6. 'Time to target' using 'Foot' for walking from my current location is quite incorrect. For example: 2.8mi/12m:34s or 5.1mi/23m:00s. The routes taken and distances, giving priority to footpaths where available, are quite correct. I have used GraphHopper successfully for several years and am unaware, historically, of this error. I wonder if one of my settings is incorrect?

Replies (5)

photo
1

Good day Bob,

in most cases, "Time to target" values are computed from current average speed during a navigation. Is same incorrect value visible also during navigation or is after a while of walk improved to correct value?


I see an known issue here. Almost all navigation sources in Locus Map (except online MapQuest) , does not give Locus time information, so it's almost impossible to correctly estimate these time values. Sorry for a complications.

photo
1

Menion


I thank you for your reply and explanation. I must have used the facility previously while on my walks, only - not at home as now. I am guilty of attempting to use it as a route planner.

photo
1

Hello Bob,

I believe that Locus Map is really usable as route planner, well expect these times. Also partially because of this, we created function "Travel time" ( available in bottom of track screen and also bottom "tools menu" of track planner ), where you may better compute expected time on trips. Hope this will be useful for you.

photo
1

Menion


Is what you describe - function "Travel time" - an introduction since 3.18.6 version? I cannot locate it from your description.

photo
1

Hello,

yep, check this

Replies have been locked on this page!