[
https://issues.apache.org/jira/browse/LUCENE-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610055#comment-14610055
]
Karl Wright commented on LUCENE-6607:
-------------------------------------
Ah, ok. So I agree that spatial4j *for the moment* cannot be a core
dependency, and may be too heavyweight in any case. (FWIW, earlier versions of
spatial4j did not depend on JTS, so that was the disconnect.) That answers one
of my questions. I take it, then, that the lucene spatial module is therefore
also tarnished? And that is the reason why GeoPointField isn't going to live
there?
I'd rather not have geo3d wind up in a library that everyone is afraid to use
in any case, so if everything above is correct, I'd vote strongly for moving
geo3d to sandbox (for now) and eventually to its own place.
> Move geo3d to Lucene's sandbox module
> -------------------------------------
>
> Key: LUCENE-6607
> URL: https://issues.apache.org/jira/browse/LUCENE-6607
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 5.3, Trunk
>
>
> Geo3d is a powerful low-level geo API, recording places on the earth's
> surface in the index in three dimensions (as 3 separate numbers) and offering
> fast shape intersection/distance testing at search time.
> [~daddywri] originally contributed this in LUCENE-6196, and we put it in
> spatial module, but I think a more natural place for it, for now anyway, is
> Lucene's sandbox module: it's very new, its APIs/abstractions are very much
> in flux (and the higher standards for abstractions in the spatial module
> cause disagreements: LUCENE-6578), [~daddywri] and others could iterate
> faster on changes in sandbox, etc.
> This would also un-block issues like LUCENE-6480, allowing GeoPointField and
> BKD trees to also use geo3d.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
