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

Parameter for Polygon-Based Area Avoidance in OSRM table Method #6953

Open
TiagoDelatorre opened this issue Jun 16, 2024 · 1 comment
Open

Comments

@TiagoDelatorre
Copy link

Description:
I am interested in using the OSRM API's table method to calculate distance or time matrices. Currently, I need to exclude specific areas defined by polygons from these calculations. However, I couldn't find a parameter that allows me to do this directly.

Request:
Could you consider adding a parameter to the table method that allows specifying polygons to exclude from the calculations? This would enable users to define complex geographic restrictions more effectively, enhancing the utility of the OSRM API for diverse routing scenarios.

Use Case:
For instance, I would like to calculate travel matrices between multiple points while excluding areas such as parks or construction sites. Being able to define exclusion zones using polygons would greatly benefit my application's routing capabilities.

Expected Outcome:
The ability to specify exclusion areas via polygons in the table method would streamline routing calculations, making the OSRM API more versatile and applicable to a wider range of spatial analysis tasks.

Thank you for considering this feature request. Please let me know if further clarification or examples would be helpful.

@jcoupey
Copy link

jcoupey commented Jun 17, 2024

This is essentially a duplicate of #892 (still open). Several other tickets touching on that subject have been closed in favor of the later. Following links to those will also provide some good insights on why that topic is far from trivial given the routing algorithms implemented in OSRM: targeting efficiency and very fast response times often comes with the price of a lower flexibility.

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

No branches or pull requests

2 participants