[
https://issues.apache.org/jira/browse/LUCENE-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15184048#comment-15184048
]
Nicholas Knize commented on LUCENE-7056:
----------------------------------------
To keep from further hijacking [~dsmiley] thread I'll open a separate issue to
further investigate this issue. I actually think this can be solved during
segment merge where we have a broader view of the data in bulk as opposed to
inserting point by point. It gives a chance to build a more efficient KD tree.
bq. not rectangles on the surface sphere
That rectangle was from a higher level (I think it was level 2 or 3) internal
BKD node while testing LatLonPoint during a distance query. Since the split
happens along one of the lat lon dimensions those values were taken from the
lat lon rages of the internal node. Any query (bbox, distance, poly) that
intersects that long rectangle recurses into the rectangle. This node was
visited quite often
> Spatial3d/Geo3d should have zero runtime dependencies
> -----------------------------------------------------
>
> Key: LUCENE-7056
> URL: https://issues.apache.org/jira/browse/LUCENE-7056
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/spatial3d
> Reporter: David Smiley
> Assignee: David Smiley
> Fix For: 6.0
>
> Attachments: LUCENE_7056__split_spatial3d_package.patch,
> LUCENE_7056__split_spatial3d_package.patch
>
>
> This is a proposal for the "spatial3d" module to be purely about the
> shape/geometry implementations it has. In Lucene 5 that's actually all it
> has. In Lucene 6 at the moment its ~76 files have 2 classes that I think
> should go elsewhere: Geo3DPoint and PointInGeo3DShapeQuery. Specifically
> lucene-spatial-extras (which doesn't quite exist yet so lucene-spatial) would
> be a suitable place due to the dependency. _Eventually_ I see this module
> migrating elsewhere be it on its own or a part of something else more
> spatial-ish. Even if that never comes to pass, non-Lucene users who want to
> use this module for it's geometry annoyingly have to exclude the Lucene
> dependencies that are there because this module also contains these two
> classes.
> In a comment I'll suggest some specifics.
--
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
