David Smiley commented on LUCENE-8126:

bq.  I am not sure that a different projection will help on this case, 
projection distorts the shapes as well as the cells so not sure how much much 
benefit we will get.

An experiment for another day I guess.  I'm more hopeful web-mercator will 
help.  Yes there is always distortion, but if the distortion is just overall 
size, then I think the cell-count shouldn't change.

bq. Healpix

Thanks for the reference; this looks cool!

RE benchmark; you said exactly this, which I can't track down but maybe I just 
don't know what to look for:

bq. I have added the performance test classes on the branch in case you want to 
have a look to check results are not bias.

bq. Anyway, it would be nice to have this SPT commited, so my question is which 
branches should I commit it? Not sure what is the policy here.

+1.  Do so to master & branch_7x.  This is standard practice for the vast 
majority of work.  If you _changed_ something that would break back-compat in 
unacceptable ways then such changes would belong only in master; but it's 

> Spatial prefix tree based on S2 geometry
> ----------------------------------------
>                 Key: LUCENE-8126
>                 URL: https://issues.apache.org/jira/browse/LUCENE-8126
>             Project: Lucene - Core
>          Issue Type: New Feature
>          Components: modules/spatial-extras
>            Reporter: Ignacio Vera
>            Assignee: Ignacio Vera
>            Priority: Major
>         Attachments: SPT-cell.pdf, SPT-query.jpeg
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
> Hi [~dsmiley],
> I have been working on a prefix tree based on goggle S2 geometry 
> (https://s2geometry.io/) to be used mainly with Geo3d shapes with very 
> promising results, in particular for complex shapes (e.g polygons). Using 
> this pixelization scheme reduces the size of the index, improves the 
> performance of the queries and reduces the loading time for non-point shapes. 
> If you are ok with this contribution and before providing any code I would 
> like to understand what is the correct/prefered approach:
> 1) Add new depency to the S2 library 
> (https://mvnrepository.com/artifact/io.sgr/s2-geometry-library-java). It has 
> Apache 2.0 license so it should be ok.
> 2) Create a utility class with all methods necessary to navigate the S2 tree 
> and create shapes from S2 cells (basically port what we need from the library 
> into Lucene).
> What do you think?

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to