[
https://issues.apache.org/jira/browse/LUCENE-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218503#comment-15218503
]
Karl Wright edited comment on LUCENE-7150 at 3/30/16 6:21 PM:
--------------------------------------------------------------
[~mikemccand] Thanks!
FWIW, polygons do not have the same issues with approximation in geo3d as
circles. They are in fact exact. Are the 2D implementations doing real
great-circle polygons, or a 2D linear interpolation?
was (Author: [email protected]):
[~mikemccand] Thanks!
FWIW, polygons do not have the same issues with approximation in geo3d as
circles. They are in fact exact. Are the 2D implementations doing real
polygons, or a 2D linear interpolation?
> 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-sphere.patch, LUCENE-7150.patch,
> LUCENE-7150.patch, 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]
