I should make it clear: geo3d does not do geo hashing by itself -- it simply provides support for determining relationships between shapes and traditional bounding boxes, which is what Spatial4J needs to support Lucene geo hashing.
Karl On Thu, Jan 22, 2015 at 3:36 PM, Karl Wright <daddy...@gmail.com> wrote: > Hi David, > > The package itself is independent of spatial4j, but a GeoShape > implementation of spatial4j Shape is trivial; I can contribute that > separately. > > Karl > > > On Thu, Jan 22, 2015 at 3:27 PM, david.w.smi...@gmail.com < > david.w.smi...@gmail.com> wrote: > >> Nice Karl! I’d love to learn more about this. Does the shapes here >> implement a Spatial4j Shape and thus would work with SpatialPrefixTree & >> friends for index & search? If not, what is the search side of the >> equation here? >> >> ~ David Smiley >> Freelance Apache Lucene/Solr Search Consultant/Developer >> http://www.linkedin.com/in/davidwsmiley >> >> On Thu, Jan 22, 2015 at 3:08 PM, Karl Wright <daddy...@gmail.com> wrote: >> >>> 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. >>> >>> For reasons that are not really technical, the only open-source project >>> that I can contribute this to initially is Lucene. If people believe it >>> would be a valuable addition, and would like me to create a ticket and >>> attach a patch, please respond. >>> >>> Thanks, >>> Karl Wright >>> >>> >> >
