lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <>
Subject [jira] [Commented] (LUCENE-7150) geo3d public APIs should match the 2D apis?
Date Tue, 29 Mar 2016 22:10:25 GMT


Karl Wright commented on LUCENE-7150:

How do you understand that people would use geometric queries?  If your notion of a geometric
query is only all documents within circles with a center then I challenge that -- it's very
very limiting and would not handle polygons, paths, rectangles, or any of the other many variants
of areas somebody may well want to search within.  If you agree that searching for those kinds
of things is important, then 99.9999% of the code that you view as useless becomes 10% rather
quickly, because that *is* what geo3d is about.

> geo3d public APIs should match the 2D apis?
> -------------------------------------------
>                 Key: LUCENE-7150
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message