Walking profile with walkway/alleyBias=1 create 3x longer routes than expected
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 438
- Forks
- 117
- PR merge metrics
- No merged PRs in 30d
Description
Hi all-
I am using turn-by-turn navigation with the Mapbox DirectionsAPI on Android and explore strange routing behavior when selecting the "walking" profile. Some routes are 3x longer than a comparable cycling route, especially highway=path and =footway seem to be avoided at all cost. I also pass walkwaybias=1 and alleybias=1 but it does not change the behavior.
An example here:
- Walking Route: https://codepen.io/ulnn/pen/RwrYbja
- Cycling Route (better route, but still mediocre): https://codepen.io/ulnn/pen/eYJLOKb
- Best Route (desired outcome): https://www.openstreetmap.org/directions?engine=graphhopper_foot&route=50.13981%2C8.69852%3B50.13825%2C8.69507#map=18/50.13921/8.69745
Any idea?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the walking and cycling examples from the linked CodePen pages with the Mapbox Directions API on Android. Compare the behavior with the linked OpenStreetMap route and verify whether walkwaybias=1 and alleybias=1 are being applied. Done means identifying an actionable cause or confirmed limitation and documenting the expected routing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- api, mobile
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100