Hi there,
Thanks both for the question and the answer.
Taking real-time traffic into account is obsiously a tricky feature, but
what about using some kind of "average known speeds" on specific
portions, perhaps depending of the time of day (those might be collected
from gps traces or maybe infered on some portions of the network). This
approach would provide more realistic timing estimations while only
requiring point 1. of your development roadmap.
Also, it would really make sense to rely on average timings when
planning routes ahead (this is what I use OSRM for), as no real-time
information can be accessed anyway.
Best,
Julien
Le 28/08/2015 11:29, Patrick Niklaus a écrit :
Our approach to support traffic in the future is two-fold:
1. Make CH pre-processing fast enough so that you can do traffic on
smaller extracts.
2. Change the routing algorithm to a technique that supports fast updates.
1. is currently being worked on. You can try the
`feature/traffic_data` branch. This is very much WIP. For one there is
no documentation of how to use it yet and I doubt you have data in a
suitable format lying around.
2. is a big push. ETA on a first candidate is some time next year.
Hope this helps,
Patrick
On Fri, Aug 28, 2015 at 10:42 AM, <[email protected]> wrote:
Hello,
Do you plan to include traffic in OSRM ?
I was wondering if it was possible, because of your use of CH algorithm,
which seems not to be the most suitable for traffic.
_______________________________________________
OSRM-talk mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/osrm-talk
_______________________________________________
OSRM-talk mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/osrm-talk
_______________________________________________
OSRM-talk mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/osrm-talk
