Tidying leads to significant losses when applied on a dense track or params are chosen too large
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 73
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
The reason behind it is that the algorithm only compares the current point to the next one, not to the last tidied one.
For simplification, I therefore suggest using `simplify-geojson`
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
No file or test is named in the issue. Start by locating the GeoJSON LineString tidying entry point and the tests for dense tracks or large parameters; compare the current-point logic with simplify-geojson, then confirm that dense tracks no longer lose significant points without breaking existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100