[
https://issues.apache.org/jira/browse/LUCENE-7392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicholas Knize updated LUCENE-7392:
-----------------------------------
Attachment: LUCENE-7392.patch
Finally got around to getting the patch together for this feature. It includes
the following:
* new {{GeoBoundingBoxField}} type in sandbox for indexing two-dimension and
three-dimension geo bounding boxes. Like the other {{POINT}} based fields there
are static helper methods for creating the {{INTERSECTS}}, {{WITHIN}},
{{CONTAINS}}, and {{CROSSES}} queries.
* new {{TestGeoBoundingBoxQueries}} class that randomly tests indexing and
search for both 2d and 3d {{GeoBoundingBoxField}}
* javadocs updated
I think this is pretty close. I've beasted it a few nights without failure. I'd
also like to get some thoughts on whether or not this should go into {{6.x}} or
{{7.0}}. My inclination is to add it as a new feature for {{7.0}} since we're
already so close to release. Thoughts welcome. Thanks!
> Add point based GeoBoundingBoxField as a new RangeField type
> ------------------------------------------------------------
>
> Key: LUCENE-7392
> URL: https://issues.apache.org/jira/browse/LUCENE-7392
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Nicholas Knize
> Attachments: LUCENE-7392.patch
>
>
> This issue will add a new point based {{GeoBoundingBoxField}} type for
> indexing and querying 2D or 3D Geo bounding boxes. The intent is to construct
> this as a RangeField type and limit the first two dimensions to the lat/lon
> geospatial bounds (at 4 bytes each like {{LatLonPoint}}, while allowing an
> optional 8 byte ({{double}}) third dimension to serve as an altitude
> component for indexing 3D geospatial bounding boxes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
