[ https://issues.apache.org/jira/browse/LUCENE-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218349#comment-15218349 ]
Michael McCandless commented on LUCENE-7150: -------------------------------------------- Ahh OK phew :) Yes, I think (?) the 2D APIs require this. Can you fix the geo3d api to also require it (check it, then I guess remove it when forwarding to the geom impls)? > 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 > > > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org