[
https://issues.apache.org/jira/browse/SOLR-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13228218#comment-13228218
]
Harley Parks edited comment on SOLR-2155 at 3/13/12 5:17 AM:
-------------------------------------------------------------
So, basic question.. perhaps needs to be posted else where.
I'm working with Solr 3.4, using the GeoHash to store multiple locations for a
document.
if geofilt or geodist doesn't work with the GeoHash, is the only way to add
this patch into solr 3.4?
I'm using a tomcat and solr, and jumping to 4.0 might be a while, even if it's
released soon.
I'm not real clear how to apply the patch, as I would need to create the
solr.war file from the source... and compile all of the other sources...
painful, but once setup, perhaps rewarding.
Ideally, I would have a jar file from the patch, that I drop into the solr/lib
and make the needed changes to the config files.
So, I'm real interested in getting something stable, so i'm watching the above
mentioned links.
David Smiley, would you be able to amend your book - Apache Solr 3 ESS, which
mentions solr-2155, to include how to implement this patch? or do I need to get
brave, and build the source?
was (Author: powersparks):
So, basic question.. perhaps needs to be posted else where.
I'm working with Solr 3.4, using the GeoHash to store multiple locations for a
document.
if geofilt or geodist doesn't work with the GeoHash, is the only way to add
this patch into solr 3.4?
I'm using a tomcat and solr, and jumping to 4.0 might be a while, even if it's
released soon.
I'm not real clear how to apply the patch, as I would need basically create the
solr.war file from the source... and compile all of the other sources...
painful, but once setup, perhaps rewarding.
Ideally, I would have a jar file from the patch, that I drop into the solr/lib
and make the needed changes to the config files.
So, I'm real interested in getting something stable, so i'm watching the above
mentioned links.
David Smiley, would you be able to amend your book - Apache Solr 3 ESS, which
mentions solr-2155, to include how to implement this patch? or do I need to get
brave, and build the source?
> 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,
> 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-for-1.0.2-3.x-port.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.
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: [email protected]
For additional commands, e-mail: [email protected]
