This object is in archive!
Expected time to travel
Answered
Let`s assume I will travel from Praha to Jihlava by car and need to know estimated time. What is the correct way to do it?
I do it this way:
- Navigate to -> End point -> Address: "Jihlava"
- Start point -> Address: "Praha"
- tap Fast
Locus displays the route with navigation screen. Distance to target is 120 km, Time to target is 62h:01m.
The distance is correct but time should be about 1h:20m.
Do I not undestand some Locus logic or it is unable to provide this information?
The same question
I would like to refresh this question....
Can I find out how much time will take travel by car from A to B?
I would like to refresh this question....
Can I find out how much time will take travel by car from A to B?
>Time to target is 62h:01m.
>The distance is correct but time should be about 1h:20m.
Once you start driving the time is beeing made more precise. However, the initial guess is often a total nonsense.
>Time to target is 62h:01m.
>The distance is correct but time should be about 1h:20m.
Once you start driving the time is beeing made more precise. However, the initial guess is often a total nonsense.
OK, but imagine I am at home and want to know how much time will take my travel tomorrow....
I think the time must be known as well. When starting navigation I can choose between Fast and Short route. How can the system suggest faster route if it does not know how fast it is (the travel time)?
OK, but imagine I am at home and want to know how much time will take my travel tomorrow....
I think the time must be known as well. When starting navigation I can choose between Fast and Short route. How can the system suggest faster route if it does not know how fast it is (the travel time)?
"The system" is a web service which assumes driving on highways is faster than on local roads or through villages, towns, etc.
It has nothing to do with Locus.
"The system" is a web service which assumes driving on highways is faster than on local roads or through villages, towns, etc.
It has nothing to do with Locus.
Lupus, in next version this value will be improved. When you compute track by any online service, locus almost always know at least two values from distance/speed/time, so I should compute better values for estimated time. So in next version
Lupus, in next version this value will be improved. When you compute track by any online service, locus almost always know at least two values from distance/speed/time, so I should compute better values for estimated time. So in next version
Replies have been locked on this page!