[
https://issues.apache.org/jira/browse/SOLR-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266738#comment-14266738
]
David Smiley commented on SOLR-4242:
------------------------------------
Filtering:
+1 to what Ishan shows...
But please don't show the old/deprecated shape syntax (Circle); I'd like to
remove it: SOLR-6904 for v5. To filter indexed points by a point-radius
circle, preferably use dwithin:
{noformat}
{!st_dwithin sfield=geo pt=54.72,-98.52 d=10}
{noformat}
You _could_ also use {{st_intersects}} with a buffered point in WKT, but
st_dwithin should be more idiomatic as it more directly aligns with the intent
and doesn't use the 'buffer' custom non-standard Spatial4j extension.
If you need to represent a circle in WKT for whatever reason then use
{{BUFFER(POINT(-98.52 54.72),0.089928)}} (note buffer distance in wkt is
degrees, but 'd' Solr param is what we set our distanceUnits to).
> 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: [email protected]
For additional commands, e-mail: [email protected]
