Re: Solr Geospatial Polygon Indexing/Querying Issue

2019-07-30 Thread David Smiley
On Tue, Jul 30, 2019 at 4:41 PM Sanders, Marshall (CAI - Atlanta) < marshall.sande...@coxautoinc.com> wrote: > I’ll explain the context around the use case we’re trying to solve and > then attempt to respond as best I can to each of your points. What we have > is a list of documents that in our c

Re: Solr Geospatial Polygon Indexing/Querying Issue

2019-07-30 Thread Sanders, Marshall (CAI - Atlanta)
David, Firstly, thanks for putting together such a thorough email it helps a lot to understand some of the things we were just guessing at because (as you mentioned a few times) the documentation around all of this is rather sparse. I’ll explain the context around the use case we’re trying to s

Re: Solr Geospatial Polygon Indexing/Querying Issue

2019-07-25 Thread David Smiley
Hello Marshall, I worked on a lot of this functionality. I have lots to say: * Personally, I find it highly confusing to have a field named "latlng" and have it be anything other than a simple point -- it's all you have if given a single latitude longitude pair. If you intend for the data to be

Re: Solr Geospatial Polygon Indexing/Querying Issue

2019-07-25 Thread Sanders, Marshall (CAI - Atlanta)
That didn't seem to work either. I think there must be something wrong with how we're indexing/storing the polygon and/or how we've configured the field/querying it. The docs are so sparse on this ( Here's the response: { "responseHeader":{ "status":0, "QTime":1, "params":{

Re: Solr Geospatial Polygon Indexing/Querying Issue

2019-07-24 Thread Ere Maijala
Oops, sorry! Don't know how I missed that. Have you tested if it makes any difference if you put the sfield parameter inside the fq like in the example (https://lucene.apache.org/solr/guide/8_1/spatial-search.html#geofilt)? We actually put pt and d in there too, e.g. {!geofilt+sfield%3Dlocation_g

Re: Solr Geospatial Polygon Indexing/Querying Issue

2019-07-24 Thread Sanders, Marshall (CAI - Atlanta)
My example query has d=1 as the first parameter, so none of the results should be coming back, but they are which makes it seem like it's not doing any geofiltering for some reason. On 7/24/19, 2:06 AM, "Ere Maijala" wrote: I think you might be missing the d parameter in geofilt. I'm not

Re: Solr Geospatial Polygon Indexing/Querying Issue

2019-07-23 Thread Ere Maijala
I think you might be missing the d parameter in geofilt. I'm not sure if geofilt actually does anything useful without it. Regards, Ere Sanders, Marshall (CAI - Atlanta) kirjoitti 23.7.2019 klo 21.32: > We’re trying to index a polygon into solr and then filter/calculate geodist > on the polygon

Solr Geospatial Polygon Indexing/Querying Issue

2019-07-23 Thread Sanders, Marshall (CAI - Atlanta)
We’re trying to index a polygon into solr and then filter/calculate geodist on the polygon (ideally we actually want a circle, but it looks like that’s not really supported officially by wkt/geojson and instead you have to switch format=”legacy” which seems like something that might be removed i

Solr Geospatial Polygon Indexing/Querying Issue

2019-07-23 Thread Sanders, Marshall (CAI - Atlanta)
We’re trying to index a polygon into solr and then filter/calculate geodist on the polygon (ideally we actually want a circle, but it looks like that’s not really supported officially by wkt/geojson and instead you have to switch format=”legacy” which seems like something that might be removed i