Global Fire Emission Database v4 (GFED4 / std)

Description

This is the plugin to accommodate fluxes as generated in the database GFED.

Monthly HDF files are expected. Data can be downloaded directly on GFED website here.

A detailed README file with all details on the data format is available here.

Use the yaml parameters to select the temporal resolution from monthly/daily/diurnal. Depending on resolution, sub-monthly fraction are used or not.

Scale burned dry matter to trace gas emissions using the scaling factors from GFED official file: GFED4_Emission_Factors.txt. The trace gas to be used in the emission factor file is taken as the tracer name in the Yaml. It is possible to specify another tracer using varname

Note

It is possible to use other scaling factors by specifying a custom scaling factor using the transform unit_conversion.

Warning

Emissions processed by the present plugin are reported in g${species}/hour. Original GFED data are reported in g/month. The conversion to hours is carried out to simplify further conversions without having to bother about the number of days per month.

Yaml arguments

The following arguments are used to configure the plugin. pyCIF will return an exception at the initialization if mandatory arguments are not specified, or if any argument does not fit accepted values or type:

Optional arguments

file_freq: (optional): 1YS

File frequency of GFED outputs

accepted type: <class ‘str’>

temporal_fraction: (optional): diurnal

Temporal fraction to use to generate emissions.

accepted values:

  • monthly: use only monthly surface areas

  • daily: use the daily_fraction variable in HDF files

  • diurnal: use the diurnal_fraction variable in HDF files.

file_emisfactors: (optional)

Full path to the file GFED4_Emission_Factors.txt.

Warning

This parameter is not mandatory. If not specified, dry matter values will be directly read and not converted. In that case, make sure to have a unit_conversion transform specified in your yaml.

ecosystems: (optional): [‘SAVA’, ‘BORF’, ‘TEMF’, ‘DEFO’, ‘PEAT’, ‘AGRI’]

List of ecosystems to include in the computed fluxes

accepted type: <class ‘list’>

Yaml template

Please find below a template for a Yaml configuration:

 1datastream:
 2  plugin:
 3    name: GFED4
 4    version: std
 5    type: datastream
 6
 7
 8  # Optional arguments
 9  file_freq: XXXXX
10  temporal_fraction: XXXXX
11  file_emisfactors: XXXXX
12  ecosystems: XXXXX