[
https://issues.apache.org/jira/browse/LUCENE-7392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006640#comment-16006640
]
Adrien Grand commented on LUCENE-7392:
--------------------------------------
Regarding which branches it should go into, both options work for me. The
benefit of not putting new features in 6.x is that it reduces the likeliness of
us having to do a bugfix release once 7.0 is out (which is always problematic
because we need to make sure the index format is forward-compatible), so I
think your plan to only put it in 7.0 makes sense.
> 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]
