[
https://issues.apache.org/jira/browse/LUCENE-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647584#comment-14647584
]
Karl Wright commented on LUCENE-6699:
-------------------------------------
If the decision is made to use (x,y,z) encoding rather than (lat,lon), then
FWIW I think the right way forward with spatial3d would be to extend the
current Bounds infrastructure to allow the finding of x,y,z bounds for a shape,
rather than just lat/lon. I've thought about this for a day and have concluded
it would be far and away the fastest solution, since computing the Bounds for
any shape would need to be done only once.
Once x, y, and z bounds are known for a shape, the BKD code itself can make
most of its decisions itself, without much computation at all, for most of the
recursive steps. Only when descending *within* the computed bounds would it be
necessary to construct a GeoArea XYZArea object to determine the exact
relationship between a 3d rectangle and the specified GeoShape.
> 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
>
>
> 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
