xivk
commented
9 years ago It is optimistic. We could change it but there is only so much information available in OSM at the moment. It's improving but that's the way it is. I used to have a metric of about 75% of max speed.
I'm also working on a way to handle historical traffic data in OsmSharp to get more realistic speeds but that's not for the next weeks more like months.
You can also try and use this:
https://github.com/OsmSharp/OsmSharp/blob/master/OsmSharp.Routing/Metrics/Time/TimeCalculator.cs
It tries to calculate times more realistically based on turns and so on...
Hello,
it seemed to me that Route.TotalTime was very optimistic. so i compared it to the results of a internet based routeplanner (http://www.falk.de/).
the middled factor was 1.4. Route.TotalTime * 1.4 led to a TotalTime close to that of falk,de.
one might assume that commercial route planners calculate extra time for stopping at traffic lights, accelerating / decelerating, going slower than permitted in narrow roads...
may i shyly suggest to use a static factor to get results of TotalTime less optimistic and more realistic?-)
asks shyly Lotto2