polyfill fails when longitude points exceed 180 degrees
Open
Nobody has claimed this yet.
documentation
- Dominant language
- C
- Stars
- 6.5k
- Forks
- 627
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 6
Description
I have seen this issue alluded to in several places now, but couldn't find a specific ticket for it (so here it is).
When the bounding points passed into the polyfill function exceed 180 degrees on the longitude, the returned indexes are invalid.
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 polyfill function and the handling of longitude bounds in the H3 source. Reproduce the case where bounding points exceed 180 degrees, then add or update a regression test showing that the returned indexes remain valid for those coordinates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100