This object is in archive!
Different drive-times with BRouter Client and LocusMaps with identical profiles (car-fast)
Closed
Using car routing with BRouter Client and LocusMaps with identical profiles (car-fast) I get with BRouter for instance one hour drive time and with LocusMaps two houres drive time on the same road with the same distance. One hour is real, two houres not.
What could be the reason for such a difference?
Kurt Pfahl
The same problem 
Good day Kurt,
where I may see exact times computed by BRouter itself? I'm asking because I'm not aware of the fact, that BRouter compute times.
In case of missing times, Locus Map computes own time estimates based on your average speed during latest rides.
Menion
Good day Kurt,
where I may see exact times computed by BRouter itself? I'm asking because I'm not aware of the fact, that BRouter compute times.
In case of missing times, Locus Map computes own time estimates based on your average speed during latest rides.
Menion
Hi MenionIf you use the BRouter Web Client (with your browser) you get all the results like Android with Locus Map.
Kurt
Hi MenionIf you use the BRouter Web Client (with your browser) you get all the results like Android with Locus Map.
Kurt
Hello Kurt,
thanks for information not known to me. I'm checking communication on Android between Locus Map and Brouter and unfortunately no information about "times" are send from BRouter to Locus Map. So this feature is not yet implemented on the Android side.
Times you see in the Locus Map are computed based on your history as I mentioned. Usually is considered around 1 hour of the last movement of a certain type. Also even if starting time estimate may not be precise, when you start navigation, it should improve based on your new speed.
I'll watch the progress on BRouter side and update code in Locus Map once this functionality will be supported.
Thanks for understanding.
Hello Kurt,
thanks for information not known to me. I'm checking communication on Android between Locus Map and Brouter and unfortunately no information about "times" are send from BRouter to Locus Map. So this feature is not yet implemented on the Android side.
Times you see in the Locus Map are computed based on your history as I mentioned. Usually is considered around 1 hour of the last movement of a certain type. Also even if starting time estimate may not be precise, when you start navigation, it should improve based on your new speed.
I'll watch the progress on BRouter side and update code in Locus Map once this functionality will be supported.
Thanks for understanding.
Hello Menion,
I still think the problem is not the missing information between BRouter and Locus Map. BRouter does the routing and delivers the result to Locus Map. The estimated driving time ist certanly calculatet bei Locus Map itself. I compared the driving times (Locus Map) with the BRouter web client running on my PC under WIN 10 for the same route and distance.
My concern is, that the estimatet driving time is so different. For example Koblenz to Dresden:
BRouter 512 km / 4 houres. Average Speed about > 120 km/h (this is OK)
Locus Map 515 km / 10 ! houres. Average Speed about > 50 km/h (this ist not real)
Both BRouter and Locus Map are supposed to use the same car-fast profile where the max Speed ist 160 km/h
The expected improvement of the estimated Driving Time bei Locus Map is no explanation for the Problem.
Wit friendly regards
Kurt
Hello Menion,
I still think the problem is not the missing information between BRouter and Locus Map. BRouter does the routing and delivers the result to Locus Map. The estimated driving time ist certanly calculatet bei Locus Map itself. I compared the driving times (Locus Map) with the BRouter web client running on my PC under WIN 10 for the same route and distance.
My concern is, that the estimatet driving time is so different. For example Koblenz to Dresden:
BRouter 512 km / 4 houres. Average Speed about > 120 km/h (this is OK)
Locus Map 515 km / 10 ! houres. Average Speed about > 50 km/h (this ist not real)
Both BRouter and Locus Map are supposed to use the same car-fast profile where the max Speed ist 160 km/h
The expected improvement of the estimated Driving Time bei Locus Map is no explanation for the Problem.
Wit friendly regards
Kurt
Good day Kurt,
let me explain it a little better. I'm not saying that the problem is not on Locus Map side. It is. There is currently no better solution.
Imagine that BRouter computes route and send it's shape into Locus Map. Locus Map, unfortunately, have absolutely no idea if your route is completely over the city or completely over the highway. Both give huge differences in time estimate.
For the car navigation may be more useful online GraphHopper routing system. It gives precise times so no problem like this happens.
I'll discuss this with BRouter developer later because agree, that exact time values are really missing in Locus Map app.
Thanks for understanding.
Good day Kurt,
let me explain it a little better. I'm not saying that the problem is not on Locus Map side. It is. There is currently no better solution.
Imagine that BRouter computes route and send it's shape into Locus Map. Locus Map, unfortunately, have absolutely no idea if your route is completely over the city or completely over the highway. Both give huge differences in time estimate.
For the car navigation may be more useful online GraphHopper routing system. It gives precise times so no problem like this happens.
I'll discuss this with BRouter developer later because agree, that exact time values are really missing in Locus Map app.
Thanks for understanding.
Thank You, Menion. I understand and wait for a better solution.
Thank You, Menion. I understand and wait for a better solution.
Replies have been locked on this page!