2 CBM_dataPrep
This documentation is work in progress. Potential discrepancies and omissions may exist for the time being. If you find any, please contact us here.
2.1 Overview
CBM_dataPrep processes spatially explicit inputs for use in CBM_vol2biomass_SK and CBM_core. In SpaDES-speak, it has two events, the init event (scheduled once) and the readDisturbanceEvents which processes disturbances (usually provided as rasters) into a table format used in CBM_core. SpaDES was designed for spatially explicit modelling and provides a wide variety of tools to support it. CBM_dataPrep makes use of these tools. We use an example that simulates a scenario where remotely-sensed disturbances are simulated in the managed forests of Saskatchewan from 1985 to 2011, as described in Boisvenue et al. (2016) (scenario = time horizon + disturbances).
2.3 Inputs
| Name | Class | Description | Source |
|---|---|---|---|
| masterRaster | SpatRaster | Raster of study area | User provided, for SK: Google Drive |
| ecoLocator | SpatRaster | Canada’s ecozone as polygon features with ecozone IDs | Canadian Soil information Service |
| adminLocator | SpatRaster | Spatial data source of Canada’s administrative boundary names | |
| ageLocator | SpatRaster | Spatial data source of cohort ages or a single value to use for all cohorts | |
| ageDataYear | Numeric | Year that the ages in ageLocator represent |
|
| ageSpinupMin | Numeric | Minimum age for cohorts during spinup | |
| gcIndexLocator | SpatRaster | Raster giving the growth curve value for each pixel | |
| cohortLocators | List | List of values or spatial data sources for additional columns in cohortDT
|
|
| curveID | Character | Column(s) uniquely defining each growth curve in cohortDT, userGcMeta, and userGcM3
|
|
| userGcMeta | Data table | User provided growth curve data | Growth curve metadata for CBM_vol2biomass |
| gcMeta | Data table | Growth curve metadata | |
| disturbanceRasters | List | Disturbance rasters for the study area for the duration of simulation | |
| disturbanceMeta | Data table | Table defining the disturbance event types |
2.4 Module functioning
CBM_dataPrep_SK has 2 events; the init event, which is run only once, and the readDisturbanceEvents event, which is repeated for each simulation year.
2.4.1 init
This first event performs the majority of the data processing steps in this module. The study area’s various spatial data is also processed into a table format for use in the CBM_core and CBM_vol2biomass_SK modules. This event is run only once.
2.4.2 readDisturbanceEvents
This short event serves to process disturbance events for each simulation year. Separating this processing from the init event enables dynamic linkages to disturbance models. However, in our example, disturbances are provided in the form of remotely-sensed disturbance rasters.
2.4.3 Disturbances
There are 468 unique disturbance matrices identified in the defaults. Since root parameters and snag carbon transfer rates have hardwood and softwood specific rates, each disturbance has a hardwood and a softwood instance, which means we have 234 unique disturbances across Canada as defaults in this modelling system, one for hardwood and one for softwood. A user could add or modify the proportions transferred between pools to represent a disturbance (NOTE THAT THIS WOULD HAVE TO HAPPEN IN THE CSVs, and even then would that work? Does libcbm point to those files? what if we change them? QUESTION FOR SCOTT, VINI and SUSAN). Add a section on how one would modify the disturbance matrices
Figure 1: Proportional carbon transfers between pools during a fire in Saskatchewan
There are a series of helper functions in CBMutils to help users explore and navigate disturbance matrices: - spuDist for extracting the disturbances in a specific spatial unit, - simDist() which lists the disturbances used in a simulation, and - seeDist() which pulls out the proportions from source to sink pools.
Because growth curves can be identified by strata, multiple columns can be used to identify growth curves using the curveID object. In our example, only gcids is used.
2.5 Outputs
| Name | Class | Description |
|---|---|---|
| standDT | Data table | Table of stand attributes. Stands can have 1 or more cohorts |
| cohortDT | Data table | Table of cohort attributes |
| userGcSPU | Data table | Table of growth curves and spatial unit combinations for each cohort |
| userGcMeta | Data table | Growth curve metadata with additional species attributes |
| gcMeta | Data table | Growth curve metadata |
| disturbanceEvents | Data table | Table with disturbance events for each simulation year |
| disturbanceMeta | Data table | Table defining disturbance event types |