Child pages
  • Metadata for Regional Integrated Assessments
Skip to end of metadata
Go to start of metadata

Metadata are used in RIAs to allow linkage between model inputs and outputs for each phase of modeling. There are just few metadata variables that can completely describe the scenario being modeled and which allow modeling inputs and final outputs to be connected so that the simulations are well defined and can be replicated and linked to input data. These linkages in the metadata allow for cohesiveness between the components of the RIAs, help provide transparency , facilitate reproducibility, and provide documentation of analyses on a very fundamental level.

Within the Impacts Explorer, these metadata variables provide the linkage for all Regional Integrated Assessment analyses.

Figure 1. Schematic of the components of a Phase 2 Regional Integrated Assessment. consistent metadata allow all data from each component to be linked and fully described.

The table below defines these metadata elements and to which phases of the RIA they are relevant.

Required common metadata

AgMIP variable name

Climate

Crop

Livestock

Econ

Impacts Explorer

1. Region identifier

REG_ID

X

X

X

X

X

2. Climate scenario identifier

CLIM_ID

X

X

X

X

X

3. RAP identifier

RAP_ID

 

X

X

X

X

4. Climate change adaptation package identifier

MAN_ID

 

X

X

X

X

5. Stratum (regional, socioeconomic, other) identifier

STRATUM

(X)

X

X

X

X

6. Crop production identifier(s)

CRID_text

 

X

 

X

X

7. Livestock production identifier(s)

BRID

 

 

X

X

X

8. Crop model identifier

CROP_MODEL

 

X

 

X

X

9. Livestock model identifier

LIVESTOCK_MODEL

  

X

X

X

10. Crop Model simulation set

CMSS

 

X

X

 

X

11. RIA Phase

Phase

   

X

X

12. Core question for RIA

CoreQuestion

 

 

 

X

X

NOTE: Metadata should not contain dashes (-) or spaces in the names.

Interdisciplinary teams should work together to define these metadata fields so that they are used consistently through climate, crop, livestock, and economic simulations.

The first four metadata fields (blue) are used to identify a unique crop production system. For crop model simulations, these are identified in the DOMEs. Livestock models take the values from the ACMO files and pass them along in ALMO files.  

 

  1. Region identifier (REG_ID): Unique text string; ISO 3-character country code, sub-country description, geographical region description.
    Examples:
    • PAK_Punjab
    • Lake_Victoria

  2. Climate scenario identifier (CLIM_ID): Using Climate Team protocols.
    Examples:
    • IEXA
    • 0XFX

  3. RAP identifier (RAP_ID): Identifies RAPs used in a particular region.
    Examples: 4.1; 4.2

  4. Climate change adaptation package identifier (MAN_ID): Identifies climate change adaptation package.
    Examples: 1.1; 1.2

  5. Stratum identifier (STRATUM): Defines elements of regional or socioeconomic strata.
    Examples: 1, 2, or 3.
     
  6. Crop production identifiers (CRID_text) for those crops which are modeled. These are the text values of crops as defined by ICASA and as listed in the ACMO files. (See the crop codes tab of the ICASA Data Dictionary.) 
    Examples: Maize, Rice 

  7. Livestock production identifier (BRID) for those livestock breeds which are modeled. The names of these breeds are identified by the livestock modelers and can be found in the ALMO files.  
    Example: NkayiLocal

  8. Crop Model identifier (CROP_MODEL). Short name for crop model used for this simulation as listed in the ACMO files.
    Examples: APSIM, DSSAT

  9. Livestock Model identifier (LIVESTOCK_MODEL). Short name for livestock model used for this simulation. For Phase 2, only one livestock model is used.
    Example: LIVSIM

  10. Crop Model Simulation Set (CMSS). These are assigned by the ACMO_UI based on CLIM_ID, RAP_ID, and MAN_ID and are listed in the ACMO and ALMO files. 
    • Examples: CM0, CM1, …, CM6
    • These same values will be used for Livestock simulation sets and will be auto-assigned based on other metadata

  11. RIA Phase (Phase): Value = 2 for all phase 2 data.
     
  12. Core Question (CoreQuestion): Core Question being answered as defined in the RIA Protocols. Value = 1, 2, 3 or 4


 See documentation for file naming conventions based on these metadata

  • No labels