[
https://issues.apache.org/jira/browse/SOLR-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988401#action_12988401
]
David Smiley commented on SOLR-2155:
------------------------------------
Hi Bill.
You simply throw this in your solrconfig.xml:
{code:xml}
<queryParser name="geo" class="solr.SpatialGeohashFilterQParser$Plugin" />
{code}
The parameters are different than the SpatialFilterQParser that's in trunk
already. Take a look at the javadocs I wrote.
By the way, there's a stupid bug in SpatialGeohashFilterQParser.parseBox() I
found an hour ago; the array indexes should go 0,1,2,3 not 0,1,3,4. I have
test code from my project I forgot to port to this patch that would have caught
that.
I have yet to make the polygon work at the poles or dateline. I nearly got a
headache trying to figure out how to make that work :P In the app that I'm
doing this for, our map viewing window doesn't wrap around at those boundaries
and so it hasn't been an issue. If you have any suggestions or pointers on how
to approach the problem then I'm interested.
> 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
> Attachments: GeoHashPrefixFilter.patch, GeoHashPrefixFilter.patch,
> GeoHashPrefixFilter.patch
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
