Open Route Service Directions returns unrealistic travel duration (inflated travel time for car profile)

I am building a simple tool to query the distance and travel time between to points using the car profile ORS API . Am able to successfully get both but the travel duration always seems too much inflated. For Example the travel time from Irving, Texas to Laredo,Texas is over 11hrs in ORS compared to just over 6hrs in Google Maps. What could be the issue. I tested the same issue in the API playground and with diffrent locations to make sure its not an error in my local configuration but duration still seems way too off.
What could be the issue?

What’s your exact request? I’m getting 07:01hr duration for that trip ( 736.5 km, avg speed 104.86 Kmh).

I suspect you chose shortest route, that gets me 10:32 hrs. Try recommended.

1 Like

Thank you for your reply… in deed the problem was the preference parameter i had set to shortest, setting to recommended seems ok. I had wrongfully assumed that the shortest route would be the faster.

One more thing, does ORS put in to consideration the current traffic situations when calculating a route in directions API?

1 Like

Shortest route will take you straight through the middle of towns and cities for example, where the highway going around that town or city would be much faster if you’re just passing through. So in miles such a route would be (much) longer, but in actual travel time much faster - because you’re not limited by traffic lights, city speed limits, etc. Shortest refers to mileage in this case, not travel time.

No, ORS does not take traffic into account, and it is only aware of roadworks for example if you explicitly tell it to, or of the roadworks are so long lasting that the local OSM Mapper added it, and is added to OSM long enough ago that ORS starts to see it. Changes in OSM are not replicated in ORS straight away. See the documentation about travel speeds for more info.