[
https://issues.apache.org/jira/browse/SOLR-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254257#comment-13254257
]
Bill Bell commented on SOLR-2155:
---------------------------------
I am getting weird results on sort=geodist() asc when using the latest version
1.0.4....
&sfield=store_geohash&pt=39.740112,-104.984856&sort=geodist() asc
Notice I am getting Denver, Texas and then Denver again?
<doc>
<float name="score">1.526444</float>
<str name="city_state">Denver, CO</str>
<str name="display_name">Shawna M. D</str>
<str name="store_lat_lon">39.740009,-104.992264</str>
</doc>
<doc>
<float name="score">2.9680724</float>
<str name="city_state">Denver, CO</str>
<str name="display_name">Meghan F. N, PA</str>
<str name="store_lat_lon">39.728024,-104.990250</str>
</doc>
<doc>
<float name="score">1.526444</float>
<str name="city_state">San Antonio, TX</str>
<str name="display_name">Dr. Shawn K. F, DO</str>
<str name="store_lat_lon">31.436729,-99.306923</str>
</doc>
<doc>
<float name="score">1.526444</float>
<str name="city_state">Denver, CO</str>
<str name="display_name">Dr. Shawn A. N, DO</str>
<str name="store_lat_lon">39.718670,-104.988907</str>
</doc>
> 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-1.0.4-project.zip,
> Solr2155-for-1.0.2-3.x-port.patch
>
>
> {panel:title=NOTICE} There is a .zip attached to the issue with a .jar you
> can drop in to Solr 3.x. 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 Spatial4j.com. 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: [email protected]
For additional commands, e-mail: [email protected]
