[ 
https://issues.apache.org/jira/browse/LUCENE-6196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289257#comment-14289257
 ] 

David Smiley commented on LUCENE-6196:
--------------------------------------

bq. With geo3d, the cost of determining membership in the shape is so low that 
I think you do better by just doing it, rather than trying to avoid doing it. 
In a way that was the whole point behind the development of geo3d.

It's awesome the code your contributing does this so fast!  But even if it were 
theoretically 0-cost, what isn't 0-cost is getting the points to test in the 
first place, wether it be from DocValues or turning the terms scanned 
in-progress into points.  There's no telling how many points lie within the 
shape in the general case because the circle (or whatever shape) could be large 
and there could be a ton of data within it.  Granted for _your_ specific 
application which may have constraints on how big a shape is permitted to be 
and knowledge of _your_ data density, it could very well be a non-issue for you.

> Include geo3d package, along with Lucene integration to make it useful
> ----------------------------------------------------------------------
>
>                 Key: LUCENE-6196
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6196
>             Project: Lucene - Core
>          Issue Type: New Feature
>          Components: modules/spatial
>            Reporter: Karl Wright
>            Assignee: David Smiley
>         Attachments: ShapeImpl.java, geo3d.zip
>
>
> I would like to explore contributing a geo3d package to Lucene.  This can be 
> used in conjunction with Lucene search, both for generating geohashes (via 
> spatial4j) for complex geographic shapes, as well as limiting results 
> resulting from those queries to those results within the exact shape in 
> highly performant ways.
> The package uses 3d planar geometry to do its magic, which basically limits 
> computation necessary to determine membership (once a shape has been 
> initialized, of course) to only multiplications and additions, which makes it 
> feasible to construct a performant BoostSource-based filter for geographic 
> shapes.  The math is somewhat more involved when generating geohashes, but is 
> still more than fast enough to do a good job.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to