You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Karl Wright (JIRA)" <ji...@apache.org> on 2015/07/01 05:27:05 UTC

[jira] [Comment Edited] (LUCENE-6607) Move geo3d to Lucene's sandbox module

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

Karl Wright edited comment on LUCENE-6607 at 7/1/15 3:26 AM:
-------------------------------------------------------------

As I understand it, the idea is to construct a field type that represents a geo3d point.  In order to be able to use BKD to search for objects in geo3d shapes, you'd obviously need geo3d math.

Nicholas has gone to some lengths to, in essence, create a minimal 2-D geo implementation sufficient to support GeoPoint field types and BKD.  Mike has built the support intended for this.  It seemed reasonable to do the same thing with geo3d as well.

So either: (1) we build true geo types into core, and accept modest new core dependencies to achieve that, or (2) we add geo field types to modules/spatial.  I don't know if (2) is in fact a reasonable thing to do, however.


was (Author: kwright@metacarta.com):
As I understand it, the idea is to construct a field type that represents a geo3d point.  In order to be able to use BKD to search for objects in geo3d shapes, you'd obviously need geo3d math.

Nicholas has gone to some lengths to, in essence, create a minimal 2-D geo implementation sufficient to support GeoPoint field types and BKD.  Mike has built the support intended for this.  It seemed reasonable to do the same thing with geo3d as well.

So either: (1) we build true geo types into core, and accept modest dependencies to achieve that, or (2) we add geo field types to modules/spatial.  I don't know if (2) is in fact a reasonable thing to do, however.

> 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