WEll, this is the query that USED to work, before we massaged the schema, (*I* 
did).

solr/select?wt=json&indent=true&start=0&rows=20&q={!spatial lat=37.221293 
long=-121.979192 radius=1000 unit=km threadCount=3} *:*

WHOOPS!!!

Just for fun, after spending HOURS screwing around with exceptions, after 
following some bad directions on the web to just delete the index directory 
first to do a new data import, i tried the query above and now it works.

I don't know enough to know why.

To get it working, I copied an index directory from another instance with an 
incorrect schema, issued a delete all command *:*, then did the data import and 
optimize, and voila! Along the way, I had to change the owner and group of the 
replaced ../index directory and files back to tomcat6.

I THINK that I had one of the 'lng' fields in one of the three config files of 
interest as 'long'. 


I'll ask some questons about that in the next email.





 Dennis Gearon


Signature Warning
----------------
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'


EARTH has a Right To Life,
otherwise we all die.



----- Original Message ----
From: Estrada Groups <estrada.adam.gro...@gmail.com>
To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org>
Cc: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org>
Sent: Sat, January 29, 2011 9:35:56 PM
Subject: Re: get SOMETHING out of an index

It would be really helpful to send along your schem.XML file so we can see how 
you are indexing these points. Polygons and linestrings are not supported yet. 
Another good way to test is using the Solr/admin tool or hand jamming your 
params in manually. Type *:* as your query in the admin tool. And see what it 
returns. It should return all indexed fields and their values.

Keep in mind that your radius search as to be done on the field type 
solr.LatLong so check out the field called stores in the example config file.  
From there you cam start to build out the rest of your queries starting with 
{!type=geofilt} I have example code that I can send along tomorrow. 


For the Solr/Lucene contributors out there, was it the point of storing lats 
and 
longs in individual fields if they can't really be used for anything? I they 
can 
please gimme an example that uses solr.point type.

Adam 

Sent from my iPhone

On Jan 29, 2011, at 11:09 PM, Dennis Gearon <gear...@sbcglobal.net> wrote:

> I indexed my whole database (only 52k records).
> 
> It has some geospatioal on it. I set the geospatial to 1000km radius to 
>centered 
>
> on the town where they all are, and NADA comes out.
> 
> How can I find out what's in the index and get at least ONE document out?
> 
> Dennis Gearon
> 
> 
> Signature Warning
> ----------------
> 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'
> 
> 
> EARTH has a Right To Life,
> otherwise we all die.
> 

Reply via email to