lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3795) Replace spatial contrib module with LSP's spatial-lucene module
Date Thu, 16 Feb 2012 18:06:59 GMT


David Smiley commented on LUCENE-3795:

The spatial-lucene module of LSP has 3 main packages: 'base', 'strategies', and 'benchmark'.
It also has a fair amount of tests.

h3. Base
Major pieces in 'base':
* SpatialContext interface and simple implementation
* Distance math code
* Shapes interface and implementations
* PrefixTree/Trie (grid) interface and implementations (e.g. geohash)

h3. Strategies
The "strategies" portion of this module contains spatial indexing/search implementations using
Major interfaces (just one):
* SpatialStrategy (including abstract PrefixGridStrategy)
Major implementations:
** *RecursivePrefixTreeStrategy*
*** This is the main strategy, based on SOLR-2155. It uses an abstract class SpatialPrefixTree
which has geohash and quadtree implementations.
** TermQueryPrefixTreeStrategy
** TwoDoubleStrategy
*** Akin to Solr's LatLonType, although some edge cases not yet implemented.

h3. Benchmarking
Benchmarking is a TBD; there's the start of some code there but nothing real. 1 year ago I
did benchmark SOLR-2155 (with great results) and posted my benchmark code here LUCENE-2844
in the interest of transparency.

h3. Testing
Testing so far hasn't been aimed directly at increasing code coverage, it's been aimed at
finding nasty corner cases in spatial. Spatial code is highly prone to edge cases.
> Replace spatial contrib module with LSP's spatial-lucene module
> ---------------------------------------------------------------
>                 Key: LUCENE-3795
>                 URL:
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: modules/spatial
>            Reporter: David Smiley
>            Assignee: David Smiley
>             Fix For: 4.0
> I propose that Lucene's spatial contrib module be replaced with the spatial-lucene module
within Lucene Spatial Playground (LSP).  LSP has been in development for approximately 1 year
by David Smiley, Ryan McKinley, and Chris Male and we feel it is ready.  LSP is here:
 and the spatial-lucene module is intuitively in svn/trunk/spatial-lucene/.
> I'll add more comments to prevent the issue description from being too long.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message