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
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
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
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
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. I've skimmed through some of the geospatial
jira issues, and read
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,
It is always a good idea to learn from your own mistakes. It is usually
> a
> > > better idea to learn from others’ mistakes, so you do not have to make
> > > them yourself. from
> > > 'http://blogs.techrepublic.com.com/security/?p=4501&tag=nl.e036'
> &
s.techrepublic.com.com/security/?p=4501&tag=nl.e036'
> >
> >
> > EARTH has a Right To Life,
> > otherwise we all die.
> >
> >
> >
> > - Original Message
> > From: George Anthony
> > To: solr-user@lucene.apache.or
> otherwise we all die.
>
>
>
> - Original Message ----
> From: George Anthony
> To: solr-user@lucene.apache.org
> Sent: Fri, December 10, 2010 9:23:18 AM
> Subject: SOLR geospatial
>
> In looking at some of the docs support for geospatial search.
>
> I s
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: George Anthony
To: solr-user@lucene.apache.org
Sent: Fri, December 10, 2010 9:23:18 AM
Subject: SOLR geospatial
In looking at
In looking at some of the docs support for geospatial search.
I see this functionality is mostly scheduled for upcoming release 4.0 (with
some
playing around with backported code).
I note the support for the bounding box filter, but will "bounding box" be one
of the supported *data* types fo
19 matches
Mail list logo
