mapbox / mapbox/mapbox-directions.js
Directions error -> OSM improvement flow
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 58
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
We should build in a feedback loop back to OSM when a user gets false results from the geocoder.
In the error message, provide a link to OSM that does two things:
- Based on the error, explain not just what OSM is, but also explain to the user what likely went wrong and how they help can fix it
- Provide a link to OSM with user's location.
It would be cool to do this in a way that was easy for developers to integrate into their own work, or even built in by default. I'm not sure what the best way to build this would be. @jfirebaugh have you thought about this at all?
cc: @lxbarth @gundersen
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 locating the error-message flow and the geocoder and user-location entry points in the JavaScript plugin. Define how an error should explain the likely OSM problem, link to OSM with the user's location, and make the feedback flow easy to integrate or enable by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100