Methods to load maps of explanatory variables, which may be created from file, an existing Raster* object or a list of Raster* objects.
1 2 3 4 5 6 7 8 9 10 11 12 13
ExpVarRasterList(x, ...) ## S4 method for signature 'missing' ExpVarRasterList(x, pattern = NULL, ...) ## S4 method for signature 'character' ExpVarRasterList(x, pattern = NULL, ...) ## S4 method for signature 'RasterStack' ExpVarRasterList(x, pattern = NULL, ...) ## S4 method for signature 'list' ExpVarRasterList(x, pattern = NULL, ...)
path (character) to directory containing observed land use maps, a Raster* object or a list of Raster* objects
regular expression (character). Only filenames (if
additional arguments to
Explanatory variables should follow a naming convention to identify them as static (one map provided for the study period) or dynamic (one map provided for each year of the study period). The name should consist of two (static) or three (dynamic) parts: firstly, the prefix should differentiate explanatory variables from other maps in the directory, list or RasterStack. This should be followed by a unique number to differentiate the explanatory variables (note that the order of variables in the ExpVarRasterList object is determined by this value) If the variable is dynamic this number should be followed by a second number representing the timestep to which the map applies. Dynamic variables should include a map for time 0 (corresponding to the initial observed map) and every subsequent timestep in the simulation. The different parts should be separated by a period or underscore.
Maps of different explanatory variables should have the same coordinate
reference system but do not have to have the same extent and resolution as
long as the minimum extent is that of the study region defined by an
ObsLulcRasterStack object. However, maps for different timesteps of the same
dynamic variable should have the same extent and resolution because these are
stored as RasterStack objects.
An ExpVarRasterList object.
1 2 3 4 5