[
https://issues.apache.org/jira/browse/SOLR-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114726#comment-13114726
]
geert-jan brits edited comment on SOLR-2155 at 9/26/11 3:45 PM:
----------------------------------------------------------------
Great thanks, I believe you interpretation of my use-case is correct .
I will go the Multi-point route first, without the polygons.
Just to clarify: I realize I added to the confusion by bringing polygons to the
table where they aren't necessary for the problem I described.
I did this because I thought that perhaps "distance of point to polygon' was
implemented in LSP, while 'distance of point to collection of points' was not.
In that case 'transforming the problem space' by representing a 'collection of
points' as a polygon and querying for "distance of point to polygon" instead
would have given me what I wanted. This is all superfluous now, because doing
'distance of point to collection of points' IS possible.
I will check out the code, thanks again!
was (Author: gbrits):
Great thanks, I believe you interpretation of my use-case is correct .
I will go the Multi-point route first, without the polygons.
Just to clarify: I realize I added to the confusion by bringing polygons to the
table where they aren't necessary for the problem I described.
I did this because I thought that perhaps "distance of point to polygon' was
implemented in LSP, while 'point to collection of points' was not.
In that case 'transforming the problem space' by representing a 'collection of
points' as a polygon and querying for "distance of point to polygon" instead
would have given me what I wanted. This is all superfluous now, because doing
'point to collection of points' IS possible.
I will check out the code, thanks again!
> 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: Grant Ingersoll
> Attachments: GeoHashPrefixFilter.patch, GeoHashPrefixFilter.patch,
> GeoHashPrefixFilter.patch,
> SOLR-2155_GeoHashPrefixFilter_with_sorting_no_poly.patch, SOLR.2155.p3.patch,
> SOLR.2155.p3tests.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
