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
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
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
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":{
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
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
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
On Wed, Mar 7, 2012 at 7:25 AM, Matt Mitchell wrote:
> Hi,
>
> I'm researching options for handling a better geospatial solution. I'm
> currently using Solr 3.5 for a read-only "database", and the
> point/radius searches work great. But I'd like to start doing point in
> polygon searches as well.
Yes, there are trunk nightly builds, see:
https://builds.apache.org//view/S-Z/view/Solr/job/Solr-trunk/
But I don't think LSP is in trunk at this point, so that's not useful. The
code branch is on (I think)
http://svn.apache.org/repos/asf/lucene/dev/branches/lucene_3795_ls_spatial_playground
but I
36'
>
>
> EARTH has a Right To Life,
> otherwise we all die.
>
>
>
> - Original Message
> From: Erick Erickson
> To: solr-user@lucene.apache.org
> Sent: Sun, December 12, 2010 11:18:03 AM
> Subject: Re: SOLR geospatial
>
> By and large, spatial
ourself.
from 'http://blogs.techrepublic.com.com/security/?p=4501&tag=nl.e036'
EARTH has a Right To Life,
otherwise we all die.
- Original Message
From: Erick Erickson
To: solr-user@lucene.apache.org
Sent: Sun, December 12, 2010 11:18:03 AM
Subject: Re: SOLR geospatial
By and large,
By and large, spatial solr is being replaced by geospatial, see:
http://wiki.apache.org/solr/SpatialSearch. I don't think the old
spatial contrib is still included in the trunk or 3.x code bases, but
I could be wrong
That said, I don't know whether what you want is on the roadmap
there either.
I am particularly interested in storing and querying polygons. That sort of
thing looks like its on their roadmap so does anyone know what the status is
on that? Also, integration with JTS would make this a core component of any
GIS. Again, anyone know what the status is on that?
*What’s on the ro
That smells like: http://www.jteam.nl/news/spatialsolr.html
> My partner is using a publicly available plugin for GeoSpatial. It is used
> both during indexing and during search. It forms some kind of gridding
> system and puts 10 fields per row related to that. Doing a Radius search
> (vs a bound
My partner is using a publicly available plugin for GeoSpatial. It is used both
during indexing and during search. It forms some kind of gridding system and
puts 10 fields per row related to that. Doing a Radius search (vs a bounding
box
search which is faster in almost all cases in all GeoSpat
15 matches
Mail list logo
