[
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
Updated patch to include the following:
* Fixed rewrite methods to use new BQ Builder API changes
* Removed computeBBox duplicate code
* Updated randomized test to include larger ranges (this should include the
occasional dateline wrapping but I'll add some randomization for explicit
dateline wrap testing)
* Split tolerateIgnorance into two explicit methods for PointDistance and BBox
* Added geohash string utility methods to GeoUtils to support use-cases using
geohash string representations (converts to/from geohash)
* Added getter utility methods to all three query classes to support
third-party refactoring to new GeoPointField type (e.g., elasticsearch)
> 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, LUCENE-6547.patch,
> LUCENE-6547.patch, 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]
