get_yeardates

helper function needed to identify the ranges of dates to
be processed for a given year as a function of <code>download_range</code> selection
and starting/ending dates and years

Allows automating the creation of time series of rasters derived
from MODIS satellite land products data. It performs several typical
preprocessing steps such as download, mosaicking, reprojecting and resizing
data acquired on a specified time period. All processing parameters
can be set using a user-friendly GUI. Users can select which layers of
the original MODIS HDF files they want to process, which additional
quality indicators should be extracted from aggregated MODIS quality
assurance layers and, in the case of surface reflectance products,
which spectral indexes should be computed from the original reflectance
bands. For each output layer, outputs are saved as single-band raster
files corresponding to each available acquisition date. Virtual files
allowing access to the entire time series as a single file are also created.
Command-line execution exploiting a previously saved processing options
file is also possible, allowing users to automatically update time series
related to a MODIS product whenever a new image is available.
For additional documentation refer to the following article:
Busetto and Ranghetti (2016) <doi:10.1016/j.cageo.2016.08.020>.

Luigi Ranghetti

MODIStsp

Find, Download and Process MODIS Land Products Data

Lorenzo Busetto

Leah Wasser

Jeff Hanson

Babak Naimi

get_yeardates function

<dl><dt>download_range</dt>
<dd><code>character ["Full" | "Seasonal"]</code> If "full", all the
available images between the starting and the ending dates are downloaded;
If "seasonal", only the images included in the season are downloaded
(e.g: if the starting date is 2005-12-01 and the ending is 2010-02-31, only
the images of December, January and February from 2005 to 2010 - excluding
2005-01, 2005-02 and 2010-12 - are downloaded), Default: Full</dd>
<dt>yy</dt>
<dd><code>numeric</code> year for which the processing dates need to be identified</dd>
<dt>start_year</dt>
<dd><code>numeric</code> start year of current <code>MODIStsp_process</code> run</dd>
<dt>end_year</dt>
<dd><code>numeric</code> end year of current <code>MODIStsp_process</code> run.</dd>
<dt>start_date</dt>
<dd><code>character`` Start date for images download and preprocessing (yyyy.mm.dd) of current </code>MODIStsp_process` run.</dd>
<dt>end_date</dt>
<dd><code>character</code> Start date for images download and preprocessing
(yyyy.mm.dd) of current <code>MODIStsp_process</code> run.</dd></dl>

Arguments

Author

identify dates to be processed for a year — get_yeardates

<dl>

<dt>download_range</dt>
<dd><code>character ["Full" | "Seasonal"]</code> If "full", all the
available images between the starting and the ending dates are downloaded;
If "seasonal", only the images included in the season are downloaded
(e.g: if the starting date is 2005-12-01 and the ending is 2010-02-31, only
the images of December, January and February from 2005 to 2010 - excluding
2005-01, 2005-02 and 2010-12 - are downloaded), Default: Full</dd>


<dt>yy</dt>
<dd><code>numeric</code> year for which the processing dates need to be identified</dd>


<dt>start_year</dt>
<dd><code>numeric</code> start year of current <code>MODIStsp_process</code> run</dd>


<dt>end_year</dt>
<dd><code>numeric</code> end year of current <code>MODIStsp_process</code> run.</dd>


<dt>start_date</dt>
<dd><code>character`` Start date for images download and preprocessing (yyyy.mm.dd) of current </code>MODIStsp_process` run.</dd>


<dt>end_date</dt>
<dd><code>character</code> Start date for images download and preprocessing
(yyyy.mm.dd) of current <code>MODIStsp_process</code> run.</dd>

</dl>

get_yeardates: identify dates to be processed for a year

Description

Usage

Value

Arguments

Author