lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicholas Knize (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-6607) Move geo3d to Lucene's sandbox module
Date Wed, 01 Jul 2015 03:54:05 GMT

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

Nicholas Knize commented on LUCENE-6607:
----------------------------------------

Not sure I understand what you mean by automatically? Did you mean deliberately? It was intended
to provide a dependency free, lightweight, GeoPointField type for the 90% use-case where people
want simple geopoint search using nothing other than the Core library.  More advanced GIS'ish
capabilities? You'd bring on the spatial module, spatial4j, jts, ejml, sis, etc. it's really
that simple. Not sure what the problem is having a simple geo API in core? Doesn't it just
make core that much more applicable to different application use cases? It's not a highlighter,
not a suggester, it's a data type. BKD is another simple type, but requires a different codec.
 I really want to make both of these 3D capable. Unless I'm mistaken core is to have no dependencies?
If I'm wrong then this issue is moot anyway. 

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


Mime
View raw message