Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Store distance matrices #956

Closed
jcoupey opened this issue Jul 26, 2023 · 0 comments · Fixed by #960
Closed

Store distance matrices #956

jcoupey opened this issue Jul 26, 2023 · 0 comments · Fixed by #960

Comments

@jcoupey
Copy link
Collaborator

jcoupey commented Jul 26, 2023

For now we only store (and use) travel time matrices as all distances are computed after optimization with a route request to the routing engine. Storing distances is a technical step required for handling any distance-related stuff during optimization, e.g. #354 or #908.

I think both ORS and Valhalla provide distances out of the box so it would "just" be a matter of parsing them and re-using our internal matrix logic for the additional distance matrices. For (lib)OSRM, we'd have to add the required additional flags to get distances on top of travel times in the initial table request.
We'd also have to adjust the custom matrices logic to allow passing in distances matrices per profile.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant