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
I want to exclude ferries from my OSRM routing.
Currently there are two ways to do this:
Either tweak my current OSRM settings to always exclude ferries (but maybe I don't always want to do this for my OSRM service).
Or somehow add "&exclude=ferry" in the end of the OSRM query.
The latter isn't possible as I cannot override the query parameters through vroom-express. Might I suggest the possibility to add a suffix parameter here? As in querysuffix = "&exclude=ferry". This would also open up other possibilities for OSRM queries.
The text was updated successfully, but these errors were encountered:
Trollgeir
changed the title
OSRM query parameters
Routing query parameters
Aug 2, 2020
Yes, currently the only way to change the additional parameters is to adjust the hard-coded value upstream.
I think this might be interesting at some point for both OSRM and ORS (see also VROOM-Project/vroom#310), but in order to make this actionable from vroom-express, we'd have to introduce a way to set this upstream in vroom.
Another question would be whether we setup predefined overridable additional parameters, or if we allow arbitrary parameters, which might lead to situations with routing errors (think parameters not available for both route and matrix queries).
I want to exclude ferries from my OSRM routing.
Currently there are two ways to do this:
Either tweak my current OSRM settings to always exclude ferries (but maybe I don't always want to do this for my OSRM service).
Or somehow add
"&exclude=ferry"
in the end of the OSRM query.The latter isn't possible as I cannot override the query parameters through vroom-express. Might I suggest the possibility to add a suffix parameter here? As in
querysuffix = "&exclude=ferry"
. This would also open up other possibilities for OSRM queries.The text was updated successfully, but these errors were encountered: