OSRM derives speeds and durations from OpenStreetMap tags such as `highway=`, `maxspeed=`, traffic signals, road width, number of lanes, etc.
You can check the profiles for details: https://github.com/Project-OSRM/osrm-backend/tree/master/profiles Here's the demo server's debug map showing derived speeds: http://map.project-osrm.org/debug/#13/37.7960/-122.4536 You will need historic or real-time traffic data for accurate ETAs especially in congested areas such as cities; OSRM has a traffic feature for that: https://github.com/Project-OSRM/osrm-backend/wiki Some hosted services provide real-time and historic traffic integration such as Mapbox (disclaimer: I'm with Mapbox): https://www.mapbox.com/api-documentation/#directions HTH, Daniel J H On Tue, Aug 29, 2017 at 6:13 AM, Richard Saba <rs...@galigeo.com> wrote: > Hi, > > > > I have a problem regarding travel delay computed by OSRM. In some > situations like in big cities, this delay is not realistic. > > For example in Paris, it’s 1 mn per 1km. Google maps estimates it at 5mn. > > > > Therefore, I would like to get answers to the following questions : > > > > 1- What are the criterias (and steps if possible) used by OSRM 5.3.0 > while computing travel delay. > > 2- What are the possibilities provided to enhance the results and > make them precise. > > > > Best Regards, > > > > RSA7 > > > > _______________________________________________ > Routing mailing list > Routing@openstreetmap.org > https://lists.openstreetmap.org/listinfo/routing > >
_______________________________________________ Routing mailing list Routing@openstreetmap.org https://lists.openstreetmap.org/listinfo/routing
