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.
>
