Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change 
notification.

The "SolrAdaptersForLuceneSpatial4" page has been changed by DavidSmiley:
http://wiki.apache.org/solr/SolrAdaptersForLuceneSpatial4?action=diff&rev1=22&rev2=23

Comment:
Removed note about indexing non-point needing tests -- it has now been tested 
and bugs were fixed (v4.1).

  
   * Polygon, LineString and other new shapes.  All shapes are supported as 
indexed shapes and query shapes.  Shapes other than point, rectangle and circle 
are supported via JTS -- an otherwise optional dependency.  See JTS caveats 
below for more information.
   * Multi-valued indexed fields.  This is critical for storing the results of 
automatic place extraction from text using natural language processing 
techniques with a gazetteer (a variant of "geocoding"), since a variable number 
of locations will be found.
-  * Index non-point shapes as well as points.  Non-point shapes are 
essentially pixelated (i.e. gridded) to a configured resolution per shape -- an 
approximation.  By default that resolution is defined by a percentage of the 
overall shape size, and it applies to query shapes too.  Note: If extremely 
high precision of shape edges needs to be retained for accurate indexing, then 
this solution probably won't scale too well at indexing time (big indexes, slow 
indexing).  On the other hand, ''query'' shapes generally scale well to the 
maximum configured precision regardless of shape size.  Note: indexing shapes 
with area sorely [[https://issues.apache.org/jira/browse/LUCENE-4419|needs 
testing]].
+  * Index non-point shapes as well as points.  Non-point shapes are 
essentially pixelated (i.e. gridded) to a configured resolution per shape -- an 
approximation.  By default that resolution is defined by a percentage of the 
overall shape size, and it applies to query shapes too.  Note: If extremely 
high precision of shape edges needs to be retained for accurate indexing, then 
this solution probably won't scale too well at indexing time (big indexes, slow 
indexing).  On the other hand, ''query'' shapes generally scale well to the 
maximum configured precision regardless of shape size.
   * Rectangles with user-specifiable corners.  Oddly, Solr 3 spatial only 
supports the bounding box of a circle. 
   * Multi-value distance sort / score boost.  Note: this is a preliminary 
unoptimized implementation that uses a fair amount of RAM, even when 
multiValued=false.  An alternative should be provided in the future.
   * Configurable precision which can vary per shape at query time (and sort of 
at index time).  This enhances the performance.

Reply via email to