[
https://issues.apache.org/jira/browse/LUCENE-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15217980#comment-15217980
]
Robert Muir commented on LUCENE-7150:
-------------------------------------
{quote}
Turns out that Mike's problem was that he was incorrectly converting degrees to
radians.
I didn't think this was hard – after all, there is a java.lang.Math method
toRadians(double degrees) which just does it. But...
{quote}
That is one way to see it.
Another way is: Mike has struggled to try to benchmark 2D vs 3D for a long time
without success. As soon as we add sugar methods to take
latitude/longitude/kilometers, things suddenly appear to be working!!!! So the
less error-prone API is a great improvement...
> 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
> Attachments: LUCENE-7150.patch, 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
