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

David Smiley commented on SOLR-14802:
-------------------------------------

the spatial-search.adoc page already documents geodist and refers to these 
parameters it takes. 
{noformat}
`geodist` is a distance function that takes three optional parameters: 
`(sfield,latitude,longitude)`. You can use the `geodist` function to sort 
results by distance or score return results.
{noformat}
The issue here addresses a shortcoming so that it actually works with basically 
most spatial fields today.  That one line mentioning these parameters had 
become somewhat obsolete for a number of years, and is now more accurate again 
:-). I suspect the latitude & longitude aspect part may be outdated; you're 
expected to use the "pt" param like all the examples show.

> Sorting by min of two geodist functions
> ---------------------------------------
>
>                 Key: SOLR-14802
>                 URL: https://issues.apache.org/jira/browse/SOLR-14802
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: spatial
>            Reporter: Shaun Storey
>            Assignee: David Smiley
>            Priority: Major
>             Fix For: 8.7
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Previously using geo field with type LatLonType you could implement a query 
> like
> {code:java}
> /select?q=*:*&fl=ID&fq={!geofilt}&d=50&pt=53.4721936,-2.24703&sfield=MAIN_LOCATION&sort=min(geodist(),
>  geodist(ALT_LOCATION,53.4721936,-2.24703)) asc{code}
> to sort results on minium distance from multiple different locations. Moving 
> the fields to advised LatLonPointSpatialField gives
> "geodist() does not support field names in its arguments when stated fields 
> are solr.LatLonPointSpatialField spatial type, requires sfield param instead"
> This has been reviewed before SOLR-11601 but not for my actual actual 
> use-case so it seems the choice was to just change the error message rather 
> than to implement the previous functionality. Can this be re-reviewed or let 
> me know if there is another way to achieve the same result.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to