Deconflict GeoPointField and BKD LatLonField Encoding, Decoding, and Tolerance [LUCENE-6996]
Open
legacy-jira-priority:Major
module:spatial
type:enhancement
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
Follow up to #8013, BKD based `LatLonField` and postings based `GeoPointField` should use a consistent lat/lon encoding/decoding method to ensure consistent round-off error.
---
Migrated from [LUCENE-6996](https://issues.apache.org/jira/browse/LUCENE-6996) by Nick Knize (@nknize), updated Feb 01 2016
Contributor guide
Research direction
Start by comparing the GeoPointField and BKD LatLonField encoding, decoding, and tolerance behavior, then review follow-up issue #8013 and the linked LUCENE-6996 context. No source file or test is named; done means both field implementations use a consistent lat/lon encoding and decoding method with consistent round-off error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100