[GRASS-SVN] r71396 - grass-addons/grass7/raster/r.seasons
svn_grass at osgeo.org
svn_grass at osgeo.org
Sun Aug 13 01:55:10 PDT 2017
Author: veroandreo
Date: 2017-08-13 01:55:10 -0700 (Sun, 13 Aug 2017)
New Revision: 71396
Modified:
grass-addons/grass7/raster/r.seasons/r.seasons.html
Log:
r.seasons addon: manual corrections and further explanations
Modified: grass-addons/grass7/raster/r.seasons/r.seasons.html
===================================================================
--- grass-addons/grass7/raster/r.seasons/r.seasons.html 2017-08-11 22:20:47 UTC (rev 71395)
+++ grass-addons/grass7/raster/r.seasons/r.seasons.html 2017-08-13 08:55:10 UTC (rev 71396)
@@ -2,11 +2,11 @@
<em>r.seasons</em> counts the number of seasons in a time series. A
season is defined as a time period of at least <em>min_length</em>
-length in which no value is below the threshold set. If the <em>-l</em>
-flag is used, the seasons are identified when no value is above the
-threshold set. As threshold, either a fixed value for the whole region
-can be specified with the <em>threshold_value</em> option, or a raster
-map with per-cell threshold values can be supplied with the
+length in which values are above the threshold set. If the <em>-l</em>
+flag is used, a season will be a time period in which values are below
+the threshold set. As threshold, either a fixed value for the whole
+region can be specified with the <em>threshold_value</em> option, or a
+raster map with per-cell threshold values can be supplied with the
<em>threshold_map</em> option.
<p>
@@ -18,14 +18,29 @@
A season is a period of time that might include gaps up to <em>max_gap</em>.
For each season identified, two start dates and two end dates are determined.
The start date "start1" and the end date "end1" indicate the start and
-end of the core season (i.e.: season without gaps), while the start date
-"start2" and the end date "end2" indicate the start and end of the full
-season including some periods shorter than <em>min_length</em> separated
-by gaps shorter than <em>max_gap</em> at the beginning and end of the
-season. A core season is at least <em>min_length</em> long and does not
-have any gaps, while a full season can have blocks shorter than
-<em>min_length</em> at the beginning or end as long as these blocks are
-separated by gaps shorter than the <em>max_gap</em>.
+end of the core season, while the start date "start2" and the end date
+"end2" indicate the start and end of the full season including some
+periods shorter than <em>min_length</em> separated by gaps shorter than
+<em>max_gap</em> at the beginning and end of the season. A
+<b>core season</b> is at least <em>min_length</em> long and might
+contain gaps shorter than the <em>max_gap</em> inbetween, but not at the
+beginning or end. A <b>full season</b>, on the other hand, can have
+blocks shorter than <em>min_length</em> at the beginning or end as long
+as these blocks are separated by gaps shorter than the <em>max_gap</em>.
+Let's consider an example to visualize core and full seasons. We have
+a certain time series in which 0 means below the threshold and 1 means
+that the value is above the threshold set:
+<div class="code"><pre>
+000101111010111101000
+</pre></div>
+If <em>min_length=4</em> and <em>max_gap=2</em>, core and full seasons
+will be identified as follows:
+<div class="code"><pre>
+# core season:
+000001111111111100000
+#full season
+000111111111111111000
+</pre></div>
<p>
The length of the longest core and full seasons can be stored in the
More information about the grass-commit
mailing list