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

Routing error with custom matrix and -g #561

Closed
jcoupey opened this issue Sep 2, 2021 · 0 comments
Closed

Routing error with custom matrix and -g #561

jcoupey opened this issue Sep 2, 2021 · 0 comments

Comments

@jcoupey
Copy link
Collaborator

jcoupey commented Sep 2, 2021

With v1.9.0, it used to be possible to provide a custom matrix and yet use calls to a routing engine to get additional information, namely geometry and distance values.

As of v1.10.0, this results in an error:

$vroom -i input_with_custom_matrix.json -g
[Error] Route geometry request with non-routable profile car.
{"code":2,"error":"Route geometry request with non-routable profile car."}

The worst part is that the whole optimization work is carried out without any trouble, only trying the routing calls after optimization triggers the failure.

This is a regression that slipped through the changes in routing wrappers when introducing multiple profiles back in #450.

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

No branches or pull requests

1 participant