[
https://issues.apache.org/jira/browse/LUCENE-7392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006634#comment-16006634
]
Adrien Grand commented on LUCENE-7392:
--------------------------------------
This is an exciting feature!
* I'm wondering whether we should stick to 2 dimensions to be symmetric with
LatLonPoint? Maybe also call it something like LatLonBox ("LatLon" prefix to
indicate it works similarly to "LatLonPoint" and removing the "Field" suffix
like we did for ranges).
* The impl of {{newXDLQuery}} is a bit suspicious, the west builder is not
useful since it wraps a single query, which means the queryType is mostly
ignored? I haven't thought much about it but I'm wondering it could just do
{{return bboxQuery(field, minLat, minLon, minAlt, maxLat, 360.0D + maxLon,
maxAlt, queryType);}} given how we index?
* It looks like toString does not read bytes at the correct offsets,
especially for the longitude.
[~mikemccand] and/or [~rcmuir]: you might be interested to have a look since
you worked on LatLonPoint?
> 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]