mapbox / mapbox/mapbox-gl-directions
Existing route not found
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 255
- Forks
- 130
- PR merge metrics
- No merged PRs in 30d
Description
A colleague of mine found a route destination that seems to fail on mapbox (but not on OSM).
Here are the test coordinates you can use: [135.74777571420464,35.01420094203681;135.7554090854838,35.01742191794678](https://api.mapbox.com/directions/v5/mapbox/walking/135.74777571420464%2C35.01420094203681%3B135.7554090854838%2C35.01742191794678?alternatives=true&geometries=geojson&steps=true).
And here is [a similar route on OSM](http://map.project-osrm.org/?z=16¢er=35.016396%2C135.762906&loc=35.014006%2C135.748036&loc=35.017551%2C135.755295&hl=fr&alt=0&srv=2).
It only seems to happen on foot (both driving and cycling profiles allow to find a route for these coordinates), we also tried to change the "radiuses" but this happens even with unlimited radiuses. Any idea what is going on?
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 linked Mapbox walking request with the provided coordinates, then compare it with the linked OSM route and the driving and cycling results. Trace how the directions plugin handles this walking response; done means identifying the cause of the missing route and defining the corresponding fix or documented limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100