Dave Kor [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 28, 2005 10:44 AM
To: java-user@lucene.apache.org; Andrew Boyd
Subject: Re: Lucene vs Derby (vs MySQL) for spatial indexing
Quoting Andrew Boyd <[EMAIL PROTECTED]>:
> I did a small demonstration application using lucene
Quoting Andrew Boyd <[EMAIL PROTECTED]>:
> I did a small demonstration application using lucene's range query and it
> worked fine.
> I didn't use a DB at all
>
>
> "Mosul_Iraq.html", "E043.13535"
> "Mosul_Iraq.html", "N36.33608"
>
> Having the directional (E, W, N, S) worked out well
>
> Andrew
I did a small demonstration application using lucene's range query and it
worked fine.
I didn't use a DB at all
"Mosul_Iraq.html", "E043.13535"
"Mosul_Iraq.html", "N36.33608"
Having the directional (E, W, N, S) worked out well
Andrew
-Original Message-
From: Barry Carter <[EMAIL PRO
MySQL has spatial extensions now too.
Your queries lack any free-text criteria so are probably best handled by
a database, not Lucene..
>>In case anyone's interested, I'm writing a zoomable/pannable world map
Save yourself some time. Just use the Google maps API. :-)
__
Barry,
You may also want to consider PostgreSQL for a few reasons: 1) it's
historically known to work well for geo-spatial data, 2) has
GIS/geo-spatial data types and such, and 3) it seems that the new
versions let you embed Java directly into the database (perhaps
something like Oracle's Java-emb
