[
https://issues.apache.org/jira/browse/LUCENE-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693500#comment-14693500
]
Michael McCandless commented on LUCENE-6699:
--------------------------------------------
On the module dependencies, I think it's fine if we have some small code dup
for now across modules. We will sort this out over time: maybe sandbox depends
on spatial3d, or vice versa, or we "graduate" the postings-based and 2D BKD
implementations from sandbox into spatial3d (and rename it), or move them into
core/util, or ... something. I think we shouldn't fret about it at this point:
things are moving quickly and it's a little too early to figure out where
things will eventually land.
bq. I've got two masters here.
This is fine.
We all (necessarily: capitalism) have our own sometimes conflicting motives for
improving Lucene (and other open-source projects), but it works out that when
you sum up all those motives across all players what emerges is something that
benefits many, many people.
bq. moving it to Apache SIS
I think the Apache SIS project should feel free to poach geo3d at any time, but
...
Selfishly (for Lucene) I think we should also keep it here as we iterate on the
"unique" requirements we have for efficient searching. E.g. here in this issue
we already see that we need new APIs in geo3d for the BKD integration, maybe
future issues require more such iterating.
> 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: [email protected]
For additional commands, e-mail: [email protected]
