I don't have the beta version, but the changelog for LM 4.1.0 states, among other things: "More precise ETA values in the LoRouter". So I checked this yesterday and today.
For me, a reasonable ETA is important when walking and hiking. Often we want to reach a rarely running train or bus at the end of the tour, and there it is important to know if you have to hurry or not.
I usually use track navigation with a route created with the route planner. With V 4.0 this worked well last time, the ETA always predicted the arrival time quite accurately.
Now with LM 4.1.0 (and 4.1.1) this no longer works.
A track with e.g. 10 km is estimated with 1h:46m at the beginning. (walking)
A track with e.g. 5 km is estimated with 57m:48s at the beginning. (walking)
This corresponds to a speed of approx. 5.65 km/h or approx. 5.15 km/h. That is clearly too fast for walking (I am not in the army). You can try this out on all kinds of tracks, it is never correct and the time is always calculated far too close!
Even worse: There is also no proper adjustment to the actual speed during the tour.
Yesterday I let myself navigate along a test route of 12.4 km created with the route planner. At the beginning, Locus estimated 2h:15m! (corresponds to approx. 5.51 km/h).
I then took a leisurely walk, a few short breaks, met a familiar person on the way and chatted for 10 minutes. The route was recorded for comparison:
Track time 3h:04m, in motion 2h:44. (so about 20 minutes breaks).
Speed (total): 3.9 km/h
Speed (in motion): 4.4 km/h
Every 1km I took screenshots and logged the displayed values (ETA and remaining time). The ETA continuously shifted backwards, but only reached the realistic time very shortly before the finish.
Excerpts from the logging:
Start 17:16, remaining distance 12.4 km, time to finish 2:15, arrival time 19:31.
(Here you can see immediately that you can't do this!)
Check 18:37, remaining distance 7.2 km, time to finish 1:22, arrival time 19:59
(Here you can see immediately that you can't do this!)
Check 19:27, remaining distance 4,1 km, time to finish 0:47, arrival time 20:13
Actual arrival 20:20.
For the full log, see the attached excel sheet.
Locus calculates with an assumed speed of approx. 5.2 - 5.6 km/h over the entire distance and does not take into account that the actual speed is significantly slower!
In my opinion, the ETA calculation does not work properly at the moment and is therefore unusable. Then I can and must calculate a realistic arrival time in my head based on the remaining distance.
What do you mean?
*** Translated with
www.DeepL.com/Translator (free version) ***