lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Solr Wiki] Update of "SpatialForTimeDurations" by DavidSmiley
Date Mon, 03 Mar 2014 18:11:23 GMT
Dear Wiki user,

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

The "SpatialForTimeDurations" page has been changed by DavidSmiley:
https://wiki.apache.org/solr/SpatialForTimeDurations?action=diff&rev1=5&rev2=6

Comment:
Old rect syntax is deprecated

  }}}
  
  Some explanation:
-  * worldBounds: The left two numbers are the starting epoch values (usually 0) and the end
two are the maximum values.  "minX minY maxX maxY" order.  The min and maximums should be
set to the same in the X & Y dimensions.  I'm tempted to suggest using a power of two
large enough for your max value, particularly if you experience any small precision problems.
 But I'm unaware of problems so you don't have to do this.
+  * worldBounds: The left two numbers are the starting epoch values (usually 0) and the end
two are the maximum values.  "minX minY maxX maxY" order.  The min and maximums should be
set to the same in the X & Y dimensions.  I'm tempted to suggest using a power of two
large enough for your max value, particularly if you experience any small precision problems.
 But I'm unaware of problems so you don't have to do this.  The syntax here will eventually
be unsupported in Solr 5, where you'll have to use the ENVELOPE WKT style syntax (supported
in Solr 4.7 and beyond).
   * distErrPct: This use of spatial generally implies precise results, not approximate results.
 Setting distErrPct to 0 means no approximation.
   * maxDistErr:  This is basically the smallest indivisible value.  This use of spatial should
generally use the integer range to keep things simpler, so use "1".
  
@@ -38, +38 @@

  
  == Search ==
  
- Now for queries, look at the examples on Hossman's slides.  '''However''' to avoid edge
cases, you should slightly buffer the query shapes -- the edges other than the minimum or
maximum. One example query given was {{{Intersects(0 9 8 365)}}}  but this should instead
become {{{Intersects(0 8.5 8.5 365)}}}   Math: 9 - 0.5, 8 + 0.5
+ Now for queries, look at the examples on Hossman's slides.  '''However''' to avoid edge
cases, you should slightly buffer the query shapes -- the edges other than the minimum or
maximum. In addition, the syntax used is deprecated; use the rectangle range query style instead.
 One example query given was {{{Intersects(0 9 8 365)}}}.  In rectangle range query format,
this is {{{["0 9" TO "8 365"]}}}.  '''But we need to buffer it:''' {{{["0 8.5" TO "8.5 365"]}}}
  Math: 9 - 0.5, 8 + 0.5
  
  == Limitations ==
  

Mime
View raw message