You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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, namelygeometry
anddistance
values.As of
v1.10.0
, this results in an error: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.
The text was updated successfully, but these errors were encountered: