[ https://issues.apache.org/jira/browse/LUCENE-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14682501#comment-14682501 ]
Karl Wright commented on LUCENE-6699: ------------------------------------- One other question: what should I return for the four cases listed below? {code} @Override public BKD3DTreeReader.Relation compare(int xMin, int xMax, int yMin, int yMax, int zMin, int zMax) { final GeoArea xyzSolid = new XYZSolid(planetModel, xMin, xMax, yMin, yMax, zMin, zMax); final int relationship = xyzSolid.getRelationship(shape); switch (relationship) { case GeoArea.WITHIN: // nocommit: shape is within xyzsolid return BKD3DTreeReader.Relation.INSIDE; case GeoArea.CONTAINS: // nocommit: shape contains xyzsolid return BKD3DTreeReader.Relation.INSIDE; case GeoArea.OVERLAPS: // nocommit: shape overlaps xyzsolid return BKD3DTreeReader.Relation.INSIDE; case GeoArea.DISJOINT: // nocommit: shape has nothing to do with xyzsolid return BKD3DTreeReader.Relation.INSIDE; default: throw new RuntimeException("Unexpected result value from getRelationship(): "+relationship); } } }); {code} > Integrate lat/lon BKD and spatial3d > ----------------------------------- > > Key: LUCENE-6699 > URL: https://issues.apache.org/jira/browse/LUCENE-6699 > Project: Lucene - Core > Issue Type: New Feature > Reporter: Michael McCandless > Assignee: Michael McCandless > Attachments: Geo3DPacking.java, LUCENE-6699.patch, LUCENE-6699.patch, > LUCENE-6699.patch > > > I'm opening this for discussion, because I'm not yet sure how to do > this integration, because of my ignorance about spatial in general and > spatial3d in particular :) > Our BKD tree impl is very fast at doing lat/lon shape intersection > (bbox, polygon, soon distance: LUCENE-6698) against previously indexed > points. > I think to integrate with spatial3d, we would first need to record > lat/lon/z into doc values. Somewhere I saw discussion about how we > could stuff all 3 into a single long value with acceptable precision > loss? Or, we could use BinaryDocValues? We need all 3 dims available > to do the fast per-hit query time filtering. > But, second: what do we index into the BKD tree? Can we "just" index > earth surface lat/lon, and then at query time is spatial3d able to > give me an enclosing "surface lat/lon" bbox for a 3d shape? Or > ... must we index all 3 dimensions into the BKD tree (seems like this > could be somewhat wasteful)? -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org