otis_gospodnetic at yahoo
Jun 23, 2009, 9:16 PM
Post #2 of 3
(309 views)
Permalink
|
|
Re: Using Lucene to index OSM nodes (400M latitude/longitude points)
[In reply to]
|
|
Hi Kelly,
I think you want to look at LocalLucene (or LocalSolr). I haven't played with Local*, so I can't provide more than this tip. Actually, I can also suggest to dump Plucene - it's a dead project, and even when it was alive it was quite slow. If you really need to be able to search from a Perl application, your best bet may be using a Perl Solr client.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
----- Original Message ----
> From: Kelly Jones <kelly.terry.jones[at]gmail.com>
> To: general[at]lucene.apache.org
> Sent: Tuesday, June 23, 2009 11:52:48 PM
> Subject: Using Lucene to index OSM nodes (400M latitude/longitude points)
>
> Can Lucene index the openstreetmap.org (OSM) node db (400M
> latitude/longitude pairs), and then find the 20 nodes closest to a
> given latitude/longitude?
>
> More specifically:
>
> % Can Lucene index numerical data and understand that 16 is close to
> 15, but far away from 160000?
>
> % Is Lucene reasonably fast indexing 400M floating point pairs?
>
> % After Lucene creates the 400M index, can it return search results
> reasonably fast?
>
> % Is there a guide/tutorial that shows how to use Lucene to index
> numerical data (I'm using Plucene, but I'll settle for any sort of
> guide)?
>
> I tried to index OSM data w/ SQLite3, but it took forever.
>
> I realize I could use MySQL/PostgreSQL, but I'm looking for an
> embedded/serverless solution.
>
> --
> We're just a Bunch Of Regular Guys, a collective group that's trying
> to understand and assimilate technology. We feel that resistance to
> new ideas and technology is unwise and ultimately futile.
|
