How long is it before an update to OSM data is found in ORS?

I made some changes to OSM nodes near me over a week ago and the changes still aren’t visible from ORS.

I just did a random call to see what the metadata says and got this:

"engine" : {
"version" : "6.7.0",
"build_date" : "2022-02-18T19:37:41Z",
"graph_date" : "2022-08-01T23:22:36Z"

Not sure what build and graph are, but even graph is >2wks old.

1 Like

Hey,

yes, that is rather usual. Have a look here for some details on that matter :slight_smile:

Best regards

Thank you for the quick response. The most relevant part for me is near the bottom:

If everything aligns as it should, changes should be reflected in the openrouteservice within two to three weeks.

If, however, anything goes wrong anywhere, this will usually mean a delay of at least a week, assuming it gets noticed and fixed immediately. It is no sign of concern, if changes are not reflected within a month.

The TL;DR (for future readers) from the link:

Within 2-3 weeks, potentially >1 month. :skull:

1 Like

Well we are hosting a global service free for everyone to use …
If you want more up to date data, you could host your own ors instance and use the newest OSM data with it.

Best regards

1 Like

I found this api has not been updated since 2022-06-23.
https://api.openrouteservice.org/v2/directions/foot-hiking/geojson.
Could you help update data for foot hiking directions API?

“engine”: {
“version”: “6.7.0”,
“build_date”: “2022-01-17T08:23:53Z”,
“graph_date”: “2022-06-23T11:42:57Z”
}

Hey,

have a look at the link above for details on the update process - this will explain why the car-profile was already updated while the hiking-profile only updated today.

Best regards

2 Likes

It’s unfortunate there aren’t any paid options. $5 or $10 for a month of higher daily/minutely limits might be popular.