[
https://issues.apache.org/jira/browse/LUCENE-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216884#comment-15216884
]
Karl Wright commented on LUCENE-7150:
-------------------------------------
Another interesting question this begs is what exactly *is* the public API of
geo3d?
I would claim it consists of the following:
- Construction of shapes
- Construction of points
- Evaluating intersection/overlap/etc between shapes (GeoShape interface)
- Evaluating relationship between shapes and points (Membership interface)
- Computing "inside" distances (as represented by the GeoDistance interface)
- Computing "outside" distances (as represented by GeoOutsideDistance interface)
[~mikemccand], would you agree?
> 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]
