-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Add crossing encoded values for accessible pedestrian routing. #2932
Comments
Totally aggree with this issue. |
natedx
changed the title
Add crossing encoded values.
Add crossing encoded values for accessible routing.
Feb 3, 2024
natedx
changed the title
Add crossing encoded values for accessible routing.
Add crossing encoded values for accessible pedestrian routing.
Feb 3, 2024
There is already a basic crossing encoded value: #2706 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Crossings have additional keys in OpenStreetMap which indicate a number of features from appearance to accessibility : https://wiki.openstreetmap.org/wiki/Key:crossing
In the SonarVision app, we have been using the results of PR #2707 for a bit over a year now, allowing us to automatically display crossings to our users ! It's quite amazing ! However, crossings vary a lot in their level of accessibility, making additional crossing keys invaluable for accessible routing.
For example, our blind and visually impaired users typically prefer to be routed through crossings tagged with
I imagine adding these values to Graphhopper implies creating a number of new encoded values. The main ones I believe are important for a wide range of accessible routing use cases are :
Finally, adding these encoded values might also help solve the problems raised in issue #2809. Pedestrians have wildly different expectations when it comes to routing. A hurried sighted person might want the shortest path in terms of length, as crossings aren't a problem for them (they might even cross without stopping at red lights...), however a blind pedestrian will want to minimize the overall number of crossings to a certain extent while maximizing the number of crossings equipped with audio traffic signals for obvious safety reasons. A wheelchair user might want to avoid all crossings where kerbs are not lowered or flush.
Thank you for this amazing piece of software !
The text was updated successfully, but these errors were encountered: