Hey Marc
LocalLucene has been rewritten since then to use a Cartesian grid for
it's boundary box look ups
http://www.nsshutdown.com/projects/lucene/whitepaper/locallucene_v2.html
GeoHash is method of consistent hashing to produce an id where the
length of the id
gives way to the precision of
guys figured i would pass this along:
http://www.geospatialsemanticweb.com/2008/05/29/geohash-for-spatial-index-and-search
one comment there makes me a little afraid to use geohash for spatial
search:
That doesn't work too well for London, which straddles 0 longitude–either
side of 0 flips the
geohash and the tier systems (local lucene) each have their place.
Geohash is attractive since it simple and could slip into lucene
easily. The tier system is more complex, but supports more accurate
calculations and better behavior around the edges (even in New
Zealand and London)
I
a RangeFilter between the two boundaries hash) ?
In my mind I think using geohash should be better because the comparaison is
done on one field only.
What is your opinion about it ?
Best regards
Marc
--
View this message in context:
http://www.nabble.com/LocalLucene-or-GeoHash-for-spatial-search
