[jira] [Comment Edited] (SOLR-4242) A better spatial query parser

["Ishan Chattopadhyaya (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266704#comment-14266704 ] 

Ishan Chattopadhyaya edited comment on SOLR-4242 at 1/6/15 8:33 PM:
--------------------------------------------------------------------

*Filtering*:
Something like this, maybe?
fq={!st_intersects sfield="geo" wkt="Circle(54.729696,-98.525391)" d=10}

*Returning distances/boosts*:
Not sure I understood st_distance() being "alias, more or less, to geofilt" part.
Do you mean something like:
st_distance(operation, sfield, wkt/pt, distanceUnits) ?
(Wondering if the spatial operation parameter is needed?)


was (Author: ichattopadhyaya):
*Filtering*:
Something like this, maybe?
fq={!st_intersects sfield="geo" wkt="Circle(54.729696,-98.525391)" d=10}

*Returning distances/boosts*:
Not sure I understood st_distance() being "alias, more or less, to geofilt" part.
Do you mean something like:
st_distance(operation, sfield, wkt/pt, distanceUnits) ?

> A better spatial query parser
> -----------------------------
>
>                 Key: SOLR-4242
>                 URL: https://issues.apache.org/jira/browse/SOLR-4242
>             Project: Solr
>          Issue Type: New Feature
>          Components: spatial
>            Reporter: David Smiley
>             Fix For: 4.9, Trunk
>
>
> I've been thinking about how spatial support is exposed to Solr users. 
> Presently there's the older Solr 3 stuff, most prominently seen via \{!geofilt} and \{!bbox} done by [~gsingers] (I think). and then there's the Solr 4 fields using a special syntax parsed by Lucene 4 spatial that looks like mygeofield:"Intersects(Circle(1 2 d=3))" What's inside the outer parenthesis is parsed by Spatial4j as a shape, and it has a special (non-standard) syntax for points, rects, and circles, and then there's WKT.  I believe this scheme was devised by [~ryantxu].
> I'd like to devise something that is both comprehensive and is aligned with standards to the extent that it's prudent.  The old Solr 3 stuff is not comprehensive and not standardized.  The newer stuff is comprehensive but only a little based on standards. And I think it'd be nicer to implement it as a Solr query parser.  I'll say more in the comments.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org