[
https://issues.apache.org/jira/browse/LUCENE-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216902#comment-15216902
]
Robert Muir commented on LUCENE-7150:
-------------------------------------
{quote}
One problem at the moment is that all of geo3d works against a unit
sphere/ellipsoid, and uses units of radians.
{quote}
But this is an implementation detail. Literally, no user cares about this.
The api should be simple: it should take common stuff that users have like
latitude, longitude, distance in meters. A user could care less what is
happening behind the scenes!
It does not matter about esoteric use cases, it does not matter if this geo3d
can be used to model the earth the shape of an apple or to compute distance on
jupiter’s rings.
We should provide one field: one that works on planet earth, takes
lat,lon,meters, stuff like that. Anything else can be a custom query.
> 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]
