[LUCENE-6450] Add simple encoded GeoPointField type to core

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 6.0
• Fix Version/s: 5.3, 6.0
• Lucene Fields: New, Patch Available
• Assignee: Unassigned
• Reporter: Nick Knize
• Created: 23/Apr/15 21:04
• Updated: 28/Aug/22 14:31
• Resolved: 08/Jun/15 23:21

Description

At the moment all spatial capabilities, including basic point based indexing and querying, require the lucene-spatial module. The spatial module, designed to handle all things geo, requires dependency overhead (s4j, jts) to provide spatial rigor for even the most simplistic spatial search use-cases (e.g., lat/lon bounding box, point in poly, distance search). This feature trims the overhead by adding a new GeoPointField type to core along with GeoBoundingBoxQuery and GeoPolygonQuery classes to the .search package. This field is intended as a straightforward lightweight type for the most basic geo point use-cases without the overhead.

The field uses simple bit twiddling operations (currently morton hashing) to encode lat/lon into a single long term. The queries leverage simple multi-phase filtering that starts by leveraging NumericRangeQuery to reduce candidate terms deferring the more expensive mathematics to the smaller candidate sets.

Issue Links

• is duplicated by: LUCENE-6481 Improve GeoPointField type to only visit high precision boundary terms