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
When using ORS requests need to use profile "driving-car" instead of default "car". Otherwise this results in a 400 response with the message that profile "car" doesn't exist which is correct because ORS named it "driving-car".
This fixed the issue for me though it is specific for ORS and fixes all cars to the same profile (which not adding one does as well):
That's correct, we don't have a notion of profile in this frontend, it only works out of the box with OSRM, relying on the fact that car is the default there.
Not sure whether we should do anything about it, except maybe make that default explicit and easy to adjust in a config file somewhere.
When using ORS requests need to use profile "driving-car" instead of default "car". Otherwise this results in a 400 response with the message that profile "car" doesn't exist which is correct because ORS named it "driving-car".
This fixed the issue for me though it is specific for ORS and fixes all cars to the same profile (which not adding one does as well):
The text was updated successfully, but these errors were encountered: