-
Notifications
You must be signed in to change notification settings - Fork 658
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Turn-by-turn parameter "exclude_polygons" doesn't seem to work, 3.4.0 #4659
Comments
it still works on https://valhalla.openstreetmap.de/ (you can create a polygon with right toolbar). so just do that, look at the network console and compare to your request. the parameters seem fine (list of rings), but you're sure that's how you actually sent it to valhalla? you're on |
@nilsnolde Thanks! I did what you suggested and got a working result with my docker environment. There were 2 main differences I found:
So the param appears double in the request. The API docs kinda suggest that it should live on the top level of the object, but that seems to be redundant. If I remove the one nested under
Thanks again, sorry to bother and I hope my comments are any helpful. Cheers |
Little correction. That doesn't seem to be it. So far, I'm still not sure which combination actually works 😅 |
🙄 man that web app needs a make-over..
it should appear top-level, that's what the code suggests: Lines 1060 to 1083 in 6f9f637
we check the open-ness in valhalla and correct it, so both is fine technically. |
Cheers,
I'm facing an issue with the
exlude_polygons
parameter. No matter what I do, the polygons are just ignored when calculating the route.I tried:
avoid_polygons
as well asexclude_polygons
GET
and andPOST
method.max_exclude_polygons_length
invalhalla.json
: It recognizes that the polygon perimeter is too long, but if set correctly still ignores it.This is my request body as send via POST to
http://localhost:8000/route
:And this is the result, decoded to geojson:
I'm using https://download.geofabrik.de/europe/germany/hamburg-latest.osm.pbf to build the graph.
I thought it might be a version issue. I am using the docker image provided by gis-ops, version 3.4.0, but I couldn't find any related issues with that version. Maybe that fix caused the issue 3907?
Thanks in advance. Probably just stupidity at my part 😅
The text was updated successfully, but these errors were encountered: