[
https://issues.apache.org/jira/browse/SOLR-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795014#action_12795014
]
patrick o'leary commented on SOLR-1568:
---------------------------------------
I would be concerned that this starts making it more complex for users to
implement.
we're going from
{code}
&lat=49.45&long=-77.33&radius=10
{code}
to :
{code}
&fq={!sfilt p=49.32,-79.0 f=location dist=20}
{code}
What do you get out of it?
I remember FAST tm, a subsidiary of microsoft (think I got all that right),
used have
{code}
geo_location:{-79.0,49.32,10)
{code}
And that was unnecessarily awkward to explain to folks, again because different
folks viewed GIS calculations in different manors
Remember GIS is often like an Abbot and Costello sketch, who's on first, lat or
long?
Keep it simple, and please don't obscure it
--1
> Implement Spatial Filter
> ------------------------
>
> Key: SOLR-1568
> URL: https://issues.apache.org/jira/browse/SOLR-1568
> Project: Solr
> Issue Type: New Feature
> Reporter: Grant Ingersoll
> Assignee: Grant Ingersoll
> Priority: Minor
> Fix For: 1.5
>
> Attachments: CartesianTierQParserPlugin.java
>
>
> Given an index with spatial information (either as a geohash,
> SpatialTileField (see SOLR-1586) or just two lat/lon pairs), we should be
> able to pass in a filter query that takes in the field name, lat, lon and
> distance and produces an appropriate Filter (i.e. one that is aware of the
> underlying field type for use by Solr.
> The interface _could_ look like:
> {code}
> &fq={!sfilt dist=20}location:49.32,-79.0
> {code}
> or it could be:
> {code}
> &fq={!sfilt lat=49.32 lat=-79.0 f=location dist=20}
> {code}
> or:
> {code}
> &fq={!sfilt p=49.32,-79.0 f=location dist=20}
> {code}
> or:
> {code}
> &fq={!sfilt lat=49.32,-79.0 fl=lat,lon dist=20}
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
