I’m trying to use the maps.openrouteservice.org web interface to map a route between a place in the Baltics and western Europe. This routes me through Kaliningrad by default. I don’t want that, since it means requesting a visa and customs checks.
When I try to check “Avoid borders”-> “Country borders”-> “Russia”, I get the below error message:
“Code 2004: Request parameters exceed the server configuration limits. By dynamic weighting, the approximated distance of a route segment must not be greater than 300000.0 meters”
I checked for similar issues, but couldn’t immediately find any, so I hope you will appreciate me reporting this issue.
Apologies if this is not the right place to mention this. In that case, please do point me in the right direction if there is any!
Thank you very much for your work on open route service!
currently we have to restrict the length of routes that use “dynamic weightings” (i.e. avoiding countries) to 300km due to processing requirements. We should be implementing a new algorithm within the next few weeks that makes it possible to use such restrictions on longer routes, so after the next release you should be able to request this route.
I’m having the same trouble with shortest routes (±500Km) in a single country, but with the avoid ferry parameter.
Are you plannnig to allow this option soon?
Hi @pablopardoz ,
generally we have to restrict anything that is not a basic route request to 300km as using the restrictions (borders, ferries etc.) takes a lot longer and uses up a lot of resources. Unfortunately the new algorithm we were going to be using which would have got around this problem has had some teething issues and so we have had to postpone the release of that for the time being. Hopefully we will be able to get these issues resolved soon so we can release the new algorithm, but until then there is unfortunately no way around the 300km restriction.
I was excited to hear you are working on a new algorithm as I am facing similar problems (related to a border) to the two posters above. Thank you!
Can I ask when you expect it to be released/fully implemented (roughly - i.e. in half a year, two months)?
we are aiming to have it deployed by the end of August
Sorry to re-open the topic. I was wondering whether the new algorithm to overcome the challenge of imposing restrictions for longer routes is still on the agenda or whether the project had to be abandoned/postponed indefinitely.