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 suspect that this issue is due to a loss of precision in the no-go area implementation, so maybe this issue rather belongs at https://github.com/abrensch/brouter/issues.
The points of the route are all outside the defined distance. So I would think at the moment, it belongs more to the use of a simple circle around the center.
If you create a route north of the circle, the boundaries are treated very precisely. Please have a look here.
May be it helps to generate a polyline, something like defined in CircleGoArea
https://brouter.de/brouter-web/#map=16/50.9542/11.9992/osm-mapnik-german_style&lonlats=11.998077,50.950385;11.994902,50.958213&nogos=11.75532,50.918538,17302&profile=fastbike
My expectation was that the route would not intersect the no-go area.
The text was updated successfully, but these errors were encountered: