Bad time to finish in navigation !?

Waldemar Wawoczny shared this problem 2 days ago
In Progress

Hi,
Recently I've been taking the train to interesting places, I do a loop (about 60 km) and return by train.
These are usually forested places with hills.
The exact arrival time becomes important because I know the train schedule and what time I should be leaving.
And here comes the problem.
The app gives the wrong arrival time again, unless I go through the forest at 56 km/h.
I've already raised this issue, on long routes (from 100 to 130 km) in hilly terrain, as well as in the forest.
Unfortunately, I was turned away, despite the screenshots I posted.
If there is a problem with the algorithm, maybe another simpler approach to the topic: giving the time of arrival at the finish calculated using a weighted average would be better than the one that is now.
Just don't tell me that the route, for example, wasn't marked in Locus Web, because that will already look like mockery of the User (and that's already a permanent element of your answer).

Please give me some positive answer
waldek

Replies (2)

photo
1

Hi Waldek,

an immediate solution to his problem is using Locus Map app route planner with LoRouter profiles. All biking and hiking profiles offer setting up custom average speed on a flat surface which signifficantly helps with the ETA calculation:

9f27a94f87eabd15860d7694544bb3f0

Unfortunately, the Locus Map has certain problems with calculating the ETA from routes imported from outside of the app. We've been struggling with the issue for some time and still we are looking for the best solution. We apologize for any inconvenience.

photo
1

Hi,
I understand that there may be issues, but looking back, I had no issues with the finish time. The imported routes into the library displayed the total route time quite well (now it displays zero).
And that's what puzzles me.

waldek

Leave a Comment
 
Attach a file