[
https://issues.apache.org/jira/browse/LUCENE-6547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicholas Knize updated LUCENE-6547:
-----------------------------------
Attachment: LUCENE-6547.patch
This turned out to not be as difficult as originally thought. This update is
ready for review and should probably preempt LUCENE-6532. Patch includes:
* Dateline crossing support for GeoPointInBBoxQuery and GeoPointDistanceQuery
(GeoPointDistanceQuery uses ECEF Cartesian System for secant checks)
* Updated unit test to include randomized testing of GeoPointDistanceQuery
* Split GeoUtils into separate GeoDistanceUtils, GeoProjectionUtils, and
GeoUtils class files
* Successfully Beast tested several times using 100 iterations
* Updated javadocs to include known limitations and performance implications
for dateline crossing queries.
All future performance improvements can be done in separate enhancement issues.
> Add dateline crossing support to GeoPointInBBox and GeoPointDistance Queries
> ----------------------------------------------------------------------------
>
> Key: LUCENE-6547
> URL: https://issues.apache.org/jira/browse/LUCENE-6547
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/search
> Reporter: Nicholas Knize
> Attachments: LUCENE-6547.patch, LUCENE-6547.patch
>
>
> The current GeoPointInBBoxQuery only supports bounding boxes that are within
> the standard -180:180 longitudinal bounds. While its perfectly fine to
> require users to split dateline crossing bounding boxes in two,
> GeoPointDistanceQuery should support distance queries that cross the
> dateline. Since morton encoding doesn't support unwinding this issue will
> add dateline crossing to GeoPointInBBoxQuery and GeoPointDistanceQuery
> classes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
