The ETA calculation in LM4 gives nonsensical results and is inconsistent.
The topic has already been discussed in the German-speaking forum and under "Trouble and Questions" with many examples and files:
The ETA calculation does not work properly. First of all, much too low times are estimated for a certain distance. This affects navigation to a destination and, to a worse extent, track navigation. It is unclear when and how Locus uses actual speeds.
I often walk (and cycle) using a route previously created with the route planner and like to be navigated along it. So I use the track navigation. But I don't understand the "system" that calculates the remaining time or estimated time of arrival.
What I expect: I open any route with e.g. 20 km route length and start the navigation in "walking" mode. The arrival time is first calculated with a realistic value, (approx. 4-4.5 km/h). This is a fixed value or ideally an average value of my previous walking speed. After a short walking time, the actual speed is taken into account and the ETA is continuously adjusted accordingly. In my opinion, other navigation systems, e.g. for cars, work like this and many simpler map apps also manage this. Locus does not.
It is absolutely incomprehensible how Logos calculates the times. After several walks, Locus had recently calculated realistic times for me and I thought Locus had now "learned" my actual pace.
This afternoon I went for a walk of aprox. 9 km, navigated several short routes and the ETA times were always correct. Along the way I recorded the entire route. Then I cycled another 4 km, but without navigation.
After that, suddenly completely nonsensical times are calculated again (5 km route - 0:32 h). For the same route created and saved with the route planner, which was still calculated correctly this morning with 1h:04m.
The ETA calculation is an important basic function in navigation and should work reliably. At the moment, this is absolutely not the case.
Furthermore, I noticed that routes created with the web planner get a timestamp for each coordinate (for whatever reason and wherever it comes from).
But not with the app in the route planner. (You can see this when you export the respective route as a gpx file.
The ETA calculated for the route created with the web planner is thus displayed completely differently (in some cases completely unrealistically) than for the exact same route created with the route planner.
In my opinion, a route should always be calculated as I start the navigation.
I.e. in walking mode with my average walking speed, when hiking with my average hiking speed, etc. and not according to any timestamps stored in the track.
How does Locus calculate the ETA? What information and individual parameters are used? How is an individual speed determined? Only during navigation or also during track recording?
The entire ETA calculation is an black box and currently non-transparent, inconclusive and sometimes delivers completely unrealistic results.