Persistent storage and reuse of Matrix API duration results

openrouteservice
1

Hello,

We are considering using the hosted openrouteservice Matrix API for a small public travel-planning website.

We would make a Matrix request for approximately 38 driving locations (about 1,444 origin×destination cells) and store the returned drive-duration values in our website backend. The stored values would be used as approximate planning estimates between known destinations rather than queried live for every visitor. We expect to refresh the matrix roughly annually and whenever a destination or access point changes.

Could you please confirm whether results returned by the hosted openrouteservice Matrix API may be:

  • stored persistently in our backend,
  • reused indefinitely between API refreshes,
  • displayed/used on a public commercial website,
  • and incorporated into our own precomputed travel-time matrix?

We would retain the required openrouteservice/HeiGIT and OpenStreetMap attribution.

If persistent storage is permitted, are there any required deletion/expiration periods or other conditions beyond CC-BY 4.0 attribution?

Thank you.

2

Hey,

as far as the openrouteservice is concerned, as long as you stick to our Terms of Service, you may do with your results as you please.

I am a bit unsure about what you mean by “API refreshes”.
Be aware that the results of the same query may change if the openrouteservice is updated or the underlying data changes.

Best regards