Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Fri, 11 May 2012 19:36:51 +0000 (UTC)
From: "David Smiley (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <317322587.55860.1336765011137.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (SOLR-2155) Geospatial search using geohash
 prefixes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

David Smiley commented on SOLR-2155:
------------------------------------

Hi Oleg.  No, it was stripped out a long while ago.  But come to think of it, now that this issue isn't going to get committed and is also hosted somewhere outside Apache (it's on GitHub), I can re-introduce the polygon support that was formerly there.  It's not a priority for me right now but if you find the last .patch file on this issue that includes the JTS support (which in some comment above I mentioned stripping it out so you could grab the version prior to that), then you could resurrect it.  There was just one source file, plus a small hook into my query parser above.  JTS did all the work, really.  If you want to try and bring it back, then do so and send me a pull-request on github.  All said and done, it's a very small amount of work; the integration was done it just needs to be brought back.
                
> Geospatial search using geohash prefixes
> ----------------------------------------
>
>                 Key: SOLR-2155
>                 URL: https://issues.apache.org/jira/browse/SOLR-2155
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: David Smiley
>            Assignee: David Smiley
>         Attachments: GeoHashPrefixFilter.patch, GeoHashPrefixFilter.patch, GeoHashPrefixFilter.patch, SOLR-2155_GeoHashPrefixFilter_with_sorting_no_poly.patch, SOLR.2155.p3.patch, SOLR.2155.p3tests.patch, Solr2155-1.0.2-project.zip, Solr2155-1.0.3-project.zip, Solr2155-1.0.4-project.zip, Solr2155-for-1.0.2-3.x-port.patch
>
>
> {panel:title=NOTICE} The status of this issue is a plugin for Solr 3.x located here: https://github.com/dsmiley/SOLR-2155.  Look at the introductory readme and download the plugin .jar file.  Lucene 4's new spatial module is largely based on this code.  The Solr 4 glue for it should come very soon but as of this writing it's hosted temporarily at https://github.com/spatial4j.  For more information on using SOLR-2155 with Solr 3, see http://wiki.apache.org/solr/SpatialSearch#SOLR-2155  This JIRA issue is closed because it won't be committed in its current form.
> {panel}
> There currently isn't a solution in Solr for doing geospatial filtering on documents that have a variable number of points.  This scenario occurs when there is location extraction (i.e. via a "gazateer") occurring on free text.  None, one, or many geospatial locations might be extracted from any given document and users want to limit their search results to those occurring in a user-specified area.
> I've implemented this by furthering the GeoHash based work in Lucene/Solr with a geohash prefix based filter.  A geohash refers to a lat-lon box on the earth.  Each successive character added further subdivides the box into a 4x8 (or 8x4 depending on the even/odd length of the geohash) grid.  The first step in this scheme is figuring out which geohash grid squares cover the user's search query.  I've added various extra methods to GeoHashUtils (and added tests) to assist in this purpose.  The next step is an actual Lucene Filter, GeoHashPrefixFilter, that uses these geohash prefixes in TermsEnum.seek() to skip to relevant grid squares in the index.  Once a matching geohash grid is found, the points therein are compared against the user's query to see if it matches.  I created an abstraction GeoShape extended by subclasses named PointDistance... and CartesianBox.... to support different queried shapes so that the filter need not care about these details.
> This work was presented at LuceneRevolution in Boston on October 8th.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org