lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <>
Subject [jira] [Updated] (LUCENE-7150) geo3d public APIs should match the 2D apis?
Date Wed, 30 Mar 2016 00:49:25 GMT


Karl Wright updated LUCENE-7150:
    Attachment: LUCENE-7150.patch

Second version of patch.

Can't hook up Robert's check because I don't know how to set up a cross-project dependency
in Lucene, but include commented out code for somebody else to enable. Also, FWIW, the constructors
in Geo3D all have range checks as well.

> geo3d public APIs should match the 2D apis?
> -------------------------------------------
>                 Key: LUCENE-7150
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>         Attachments: LUCENE-7150.patch, LUCENE-7150.patch
> I'm struggling to benchmark the equivalent to {{LatLonPoint.newDistanceQuery}} in the
geo3d world.
> Ideally, I think we'd have a {{Geo3DPoint.newDistanceQuery}}?  And it would take degrees,
not radians, and radiusMeters, not an angle?
> And if I index and search using {{PlanetModel.SPHERE}} I think it should ideally give
the same results as {{LatLonPoint.newDistanceQuery}}, which uses haversin.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message