Map matching expected input
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 73
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Why is this recommended by Mapbox to clean up the input for the map matching API when this is for GeoJSON but the map matching API does not accept geoJSON. I mean I can transform it but it just seems like an extra step. Translate everything into LineString and then back into what this wants.
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
The issue does not identify a file, test, or entry point. Start by checking the project's documented GeoJSON LineString input against the Mapbox map matching API requirements; done means the accepted input and any required conversion are clearly defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100