[
https://issues.apache.org/jira/browse/LUCENE-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216994#comment-15216994
]
Karl Wright commented on LUCENE-7150:
-------------------------------------
bq. If Mike cannot figure out how to do these things, I think nobody else
stands a chance.
I don't actually know what problem Mike is having. He claims that when he
halves the search radius he gets twice the points. I gave him extremely simple
code to try so I don't understand what is going on either. I'm going to
reserve judgement until we figure out what's actually happening.
I am a bit concerned that you folks may be (a) making a lot out of what is
probably a very simple bug, and (b) trying to oversimplify a rather complex
problem. I don't mind working hard to make API's as consistent as possible,
but there is a risk. Looking at distance measurements as a metaphor, there are
*lots* of ways to measure distance in an ellipsoidal world. And I don't know
if you've picked the best one.
> 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: [email protected]
For additional commands, e-mail: [email protected]
