lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (SOLR-1586) Create Spatial Point FieldTypes
Date Tue, 29 Dec 2009 16:06:29 GMT

    [ https://issues.apache.org/jira/browse/SOLR-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795073#action_12795073
] 

Yonik Seeley edited comment on SOLR-1586 at 12/29/09 4:05 PM:
--------------------------------------------------------------

bq. I'm not sure I see how to use a tile for anything other than filtering 

That's the point though - as a casual user, I want a point field.  I want to be able to do
efficient spacial search on that field and not worry about all of the details.  See the example
I gave above... it's doing everything spacial-related on the *same* field.  So a higher level
SpatialTilePoint would be a point field (i.e. it would still have lat/lon separately) that
used tiles under the cover for efficient bounding box / filters.

edit: don't get me wrong, I think it's also good to also enable the use of SpatialTileField
separately (as this issue does).  It's the overall spacial-solr capabilities I'm talking about.

bq. The choice of the data structure is going to depend on the application

There will often be many applications / clients.  One should be able to change the underlying
implementation and use the same requests.  We can do this today with range queries on any
type of numeric field... we should be able to do it with a bounding box or distance filter.


      was (Author: yseeley@gmail.com):
    bq. I'm not sure I see how to use a tile for anything other than filtering 

That's the point though - as a casual user, I want a point field.  I want to be able to do
efficient spacial search on that field and not worry about all of the details.  See the example
I gave above... it's doing everything spacial-related on the *same* field.  So a higher level
SpacialTilePoint would be a point field (i.e. it would still have lat/lon separately) that
used tiles under the cover for efficient bounding box / filters.

bq. The choice of the data structure is going to depend on the application

There will often be many applications / clients.  One should be able to change the underlying
implementation and use the same requests.  We can do this today with range queries on any
type of numeric field... we should be able to do it with a bounding box or distance filter.

  
> Create Spatial Point FieldTypes
> -------------------------------
>
>                 Key: SOLR-1586
>                 URL: https://issues.apache.org/jira/browse/SOLR-1586
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Grant Ingersoll
>            Assignee: Grant Ingersoll
>            Priority: Minor
>             Fix For: 1.5
>
>         Attachments: examplegeopointdoc.patch.txt, SOLR-1586-geohash.patch, SOLR-1586.Mattmann.112209.geopointonly.patch.txt,
SOLR-1586.Mattmann.112209.geopointonly.patch.txt, SOLR-1586.Mattmann.112409.geopointandgeohash.patch.txt,
SOLR-1586.Mattmann.112409.geopointandgeohash.patch.txt, SOLR-1586.Mattmann.112509.geopointandgeohash.patch.txt,
SOLR-1586.Mattmann.120709.geohashonly.patch.txt, SOLR-1586.Mattmann.121209.geohash.outarr.patch.txt,
SOLR-1586.Mattmann.121209.geohash.outstr.patch.txt, SOLR-1586.Mattmann.122609.patch.txt, SOLR-1586.patch,
SOLR-1586.patch
>
>
> Per SOLR-773, create field types that hid the details of creating tiers, geohash and
lat/lon fields.
> Fields should take in lat/lon points in a single form, as in:
> <field name="foo">lat lon</field>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message