locationtech / locationtech/spatial4j
Optionally tweak geohash encoding to not split extreme longitudes
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 961
- Forks
- 172
- PR merge metrics
- No merged PRs in 30d
Description
A geohash grid square becomes increasingly skinny as it gets closer to a pole. When geohashes used as an encoding for shape coverage (e.g. Lucene spatial's Geohash based SpatialPrefixTree), this is a problem because it doesn't scale. We could add a boolean flag to GeohashUtils when it encodes a point such that certain extreme longitudes don't get split in half like they normally would.
https://issues.apache.org/jira/browse/LUCENE-5056
(and see attached pic too)
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 GeohashUtils and review the linked LUCENE-5056 discussion for the intended handling of extreme longitudes. Trace the point-encoding path and any existing geohash tests. Done means an optional boolean changes the relevant encoding behavior without altering the default behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100