I faced the same problem when i used locallucene 1.5 and localsolr 1.5.
Now I am using localsolr 2.0 and locallucene 2.0 and I dont see that issue.
You need to upgrade the binaries.
--
View this message in context:
http://n3.nabble.com/Spatial-Local-Solr-radius-tp487813p705744.html
Sent from
an isolated
> problem, though my test datasets were also sparse and geographically distant.
>
> -Sean
>
> -- Forwarded Message
> From: Michael
> Reply-To:
> Date: Wed, 31 Mar 2010 13:33:39 -0700
> To:
> Subject: Re: Spatial / Local Solr radius
>
> Mauric
lem, though my
test datasets were also sparse and geographically distant.
-Sean
-- Forwarded Message
From: Michael
Reply-To:
Date: Wed, 31 Mar 2010 13:33:39 -0700
To:
Subject: Re: Spatial / Local Solr radius
Mauricio,
I hooked up the spatial solr plugin to the Eclipse debugger and
narrowed
Mauricio,
I hooked up the spatial solr plugin to the Eclipse debugger and
narrowed the problem down to CartesianShapeFilter.getBoxShape(). The
algorithm used in the method can produce values of startX that are
greater than endX depending on the tier level returned by
CartesianTierPlotter.bestFit()
Hi Michael
I exchanged a few mails with jteam, ultimately I realized my longitudes'
signs were inverted so I was mapping to China instead of U.S. Still a bug,
but inverting those longitudes "fixed" the problem in my case since I'm not
running world-wide searches.
Before that I ran a test to determ
Mauricio,
I was wondering whether you had heard anything back from jteam
regarding this issue. I have also noticed it and was wondering why It
was happening.
One thing I noticed is that this problem only appears for "sparse"
datasets as compared to "dense" ones. For example, I have two datasets
I
It's jteam's plugin ( http://www.jteam.nl/news/spatialsolr ) which AFAIK is
just the latest patch for SOLR-773 packaged as a stand-alone plugin.
I'll try to contact jteam directly.
Thanks
Mauricio
On Mon, Dec 28, 2009 at 8:02 PM, Grant Ingersoll wrote:
>
> On Dec 28, 2009, at 11:47 AM, Mauricio
On Dec 28, 2009, at 11:47 AM, Mauricio Scheffer wrote:
> q={!spatial lat=43.705 long=116.3635 radius=100}*:*
What's QParser is the "spatial" plugin? I don't know of any such QParser in
Solr. Is this a third party tool? If so, I'd suggest asking on that list.
>
> with no other parameters.
>
q={!spatial lat=43.705 long=116.3635 radius=100}*:*
with no other parameters.
When changing the radius to 250 I get no results.
In my config I have startTier = 9 and endTier = 17 (default values)
On Mon, Dec 28, 2009 at 1:24 PM, Grant Ingersoll wrote:
> What do your queries look like?
>
> On
What do your queries look like?
On Dec 28, 2009, at 9:30 AM, Mauricio Scheffer wrote:
> Hi everyone,
> I'm getting inconsistent behavior from Spatial Solr when searching with
> different radii. For the same lat/long I get:
>
> radius=1 -> 1 result
> radius=10 -> 0 result
> radius=25 -> 2 results
Hi everyone,
I'm getting inconsistent behavior from Spatial Solr when searching with
different radii. For the same lat/long I get:
radius=1 -> 1 result
radius=10 -> 0 result
radius=25 -> 2 results
radius=100 -> 2 results
radius=250 -> 0 results
I don't understand why radius=10 and 250 return no r
11 matches
Mail list logo
