[
https://issues.apache.org/jira/browse/SOLR-8636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17268632#comment-17268632
]
Karl Wright commented on SOLR-8636:
-----------------------------------
[~dsmiley], there is an "outside distance", which is the distance from a point
to a shape. There is no optimal way of computing distances from shapes to each
other, however. For polygons, especially large polygons, it would be
computationally prohibitive to do it the naive way.
Not all shapes support outside distance, by the way. Only a subset do. This
functionality is described (as usual) in Geo3D by an independent interface -
see GeoDistanceShape to see how it is derived.
If you want full generality, therefore, you would need general solutions even
for some of the weirder shapes for which this is not currently implemented. I
would therefore ask what the use case is for such a feature before going down
this route?
> Incorrect distance returned for indexed polygon shapes
> ------------------------------------------------------
>
> Key: SOLR-8636
> URL: https://issues.apache.org/jira/browse/SOLR-8636
> Project: Solr
> Issue Type: Bug
> Components: spatial
> Affects Versions: 5.2.1
> Reporter: Rahul Jain
> Assignee: David Smiley
> Priority: Major
>
> We have a location_rpt field with multivalued=true and we are indexing
> multiple shapes of type LINESTRING() in a single spatial field per document.
> We are using JTS for spatial and polygon indexing and filtering.
> Solr query:
> q={!geofilt sfield=geo pt=-27,153 score=distance d=50}&fl=*,score
> For above query, we get the results perfectly fine (i.e. documents with at
> least one intersecting shape is returned) but the returned distance has
> following behavior:
> 1. When only shapes (LINESTRING(), LINESTRING()) are indexed then the
> distance returned is 180 degrees or 20015.115 kms.
> 2. When only points are indexed then the distance to nearest point is
> returned.
> 3. When both points and shapes are indexed, distance to nearest point is
> returned.
> Using above distance in sorting causes sorting to go haywire.
> Does Solr not return the distance it used during document filtering? Is there
> a workaround or am I doing something wrong?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
