Messages

Thanks Menion!

I'm completely fine with this now that I somewhat know how it works.
My problem was, that I was too reliant on the current/avg. speed calculation and I tought that it should be correct. Knowing, that it is calculated beforehand by the activity type's speed that is also different in different services... Yeah, it makes sense that it was missing the mark.

From now on, at the last hour or kilomenters, I'll just do some quick maths in my head and estimate myself.

I think I found the other thread, a support ticket topic:
https://help.locusmap.eu/topic/24639

It seems that the ETA is calculated when the route is planned and saved with the given planner service (LoRouter, BRouter, GraphHopper) and the set speed that is associated with it.
Or if the GPX was imported, it can have already saved data in it that will be used for this ETA calculation process.
Also, if you have a manually planned route or segment, that will also mess up this calculation even more.

Looks like your avg. speed and current speed have no real bearing on this number.

Hi!

I've been using Locus map for hiking and trekking for about a year now on a weekly basis and I really like it, but there's one thing that I can't figure out.

How is the "Estimated time of arrival" is calculated?

I've attached a screenshot and neither the current speed, nor the avg. speed gives a correct-ish estimate.
This ETA often gets me to worry and run for my finish point so that I won't miss the train/bus/whatever to get home in time, so I wouldn't have to wait 2 hours unnecessarily for the next one.

How is this calculated? What's the math behind it?

I would appreciate any guesses and formulas!
Thanks, Steve

You cannot view this attachment.