[jira] [Comment Edited] (LUCENE-6699) Integrate lat/lon BKD and spatial3d

["Karl Wright (JIRA)" <ji...@apache.org>]

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

Karl Wright edited comment on LUCENE-6699 at 8/11/15 11:20 PM:
---------------------------------------------------------------

Ok, did not understand that.  We don't yet have the ability to get a Bounds result for a shape that is x,y,z instead of lat/lon.  (That was the optimization we discussed but decided to do as a second step).  But I presume you *do* want the ability to know, for a given planet model, the actual bounds of the planet. ;-)  That's gotta go somewhere.


was (Author: kwright@metacarta.com):
Ok, did not understand that.  We don't yet have the ability to get a Bounds result for a shape that is x,y,z instead of lat/lon.  But I presume you *do* want the ability to know, for a given planet model, the actual bounds of the planet. ;-)  That's gotta go somewhere.

> 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, 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org