[LUCENE-7150] geo3d public APIs should match the 2D apis?

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 6.1, 7.0
• Lucene Fields: New
• Assignee: Karl Wright
• Reporter: Michael McCandless
• Created: 29/Mar/16 20:54
• Updated: 28/Aug/22 14:53
• Resolved: 31/Mar/16 15:53

Description

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.