Skip to content
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

Adding nogo-areas prompts more route recalculation than necessary #789

Open
sjakobi opened this issue Feb 3, 2024 · 0 comments
Open

Adding nogo-areas prompts more route recalculation than necessary #789

sjakobi opened this issue Feb 3, 2024 · 0 comments

Comments

@sjakobi
Copy link

sjakobi commented Feb 3, 2024

Sample route: https://brouter.de/brouter-web/#map=6/53.022/9.108/osm-mapnik-german_style&lonlats=13.382694,52.48947;12.34979,51.337476;12.908787,50.840546;11.041492,49.444397;8.625121,49.984782&profile=vm-forum-liegerad-schnell

If I now add a nogo-area that cuts only one of the route segments, say Leipzig–Chemnitz, nevertheless all of the route segments are recalculated.

My suggestion is that the program should first check which segments are cut by the added nogo-area and recalculate only those. This should be much faster, especially if the profile is computationally demanding or when the added nogo-area doesn't intersect with the route at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant