We have plans to make the Route Optimization API more flexible in this regard but it will take time.
As a workaround you can use the Routing API with any parameters after you got the location-allocation from the Route Optimization API and you’d have to use the modified ETAs from the Routing API.
We still have this in the pipeline and as top priority. But although we have progressed a lot internally we cannot say when this will go into production. Excluding motorway/toll/ferry is likely to happen sooner, but when exactly is also not defined.
Hi @karussell ,
Are there recent updates on this?
We are using both Routing and Route Optimization, and it would be really useful to be able to set similar restrictions on both.
The car_avoid_toll and car_avoid_motorway profiles are very welcome improvements, but it would be great to have more flexibility.
This is not possible. Still, as written here, we offer the custom_model feature also for the Route Optimization API as an early alpha version. Contact us if you want more information about it and try it out.