lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <j...@apache.org>
Subject [jira] [Created] (LUCENE-7150) geo3d public APIs should match the 2D apis?
Date Tue, 29 Mar 2016 20:54:25 GMT
Michael McCandless created LUCENE-7150:
------------------------------------------

             Summary: geo3d public APIs should match the 2D apis?
                 Key: LUCENE-7150
                 URL: https://issues.apache.org/jira/browse/LUCENE-7150
             Project: Lucene - Core
          Issue Type: Improvement
            Reporter: Michael McCandless


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
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message