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

Karl Wright commented on LUCENE-6699:
-------------------------------------

More analysis:

(1) Your BKD search would need to construct a GeoArea object each time it 
descends a level.
(2) Construction of an XYZ area will definitely involve construction of up to 
six additional objects (all planes), but should otherwise be computationally 
cheap.
(3) To minimize work on both construction and comparison, I'd need to create 
the following new classes, where Dg indicates "degenerate" in that dimension, 
e.g. "DgX" means "degenerate in X":

XYZArea
DgXYZArea
XDgYZArea
XYDgZArea
DgXDgYArea
DgXYDgZArea
XDgYDgZArea
DgXDgYDgZArea

Note: these are not named "Geo" objects, because they do not have anything to 
do with the surface of the world.


> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to