Nomenclature for constraint labels in Eora’s adherence, violations and data source lists
When you open Eora’s adherence and violations list you may find that constraints, and their corresponding raw data items, are labelled using a standard sequence of abbreviations. These standard abbreviations completely describe the characteristics of raw data. The purpose of the following information is to assist the users of the Eora tables in reading and understanding the adherence and violations reports.
General Form
All elements are separated by an underscore. Example:
20111107_WorldMRIO_UsaUsa,AllUsa_w,t-IIOTi-2001_RAggCLASS,RSum_CAggCLASS_ba,t_cur_1_USA_ser_100_fisim_#__UNSDSNAOC_Table4.1_D2-D3
Explanation:
Date
The date of sourcing and saving the raw data to file, using a yyyymmdd format. Example: 20190504 for the 4th May 2019.
Project
The name of the project that the data item was used for. Example: WorldMRIO or GlobalMRIO.
CountryCountry
A 3-digit UN code for country names. Examples: Chl for Chile, Deu for Germany, Usa for the United States. If countries are summed, Alo or All are used to denote “all other countries” or “all countries”. For example, all imports into Chile are AloChl. All exports from Germany are DeuAlo. All imports to the USA plus all US intermediate transactions (domestic input-output table plus imports matrix) is denoted by AllUsa. A domestic German transactions matrix would be denoted by DeuDeu. Exports from Germany to Chile would be named DeuChl.
DataIdentifier-Year
This part defines which data are contained in the constraint, and is therefore the most important part of the constraint label. The data identifier holds the data type. There are 4 basic types: t for a transactions matrix (use, trade, imports), y for final demand, w for value-added, GDP or primary inputs, and v for a supply matrix. These cover all types of matrices in an MRIO table (see table below).
Transactions data adhere to three basic input-output architectures: supply-use tables (SUT), industry-by-industry input-output tables (IIOT) or commodity-by-commodity input-output tables (CIOT). IIOT and CIOT can use industry (i) or commodity (c) technology assumption, which is denoted for example by ‘IIOTi’ or ‘CIOTi’.
An example is y-IIOTi-2000, which denotes data/constraints for a year-2000 final demand block in an industry-by-industry input- output table using the industry technology assumption. If ‘ty’ or ‘t,y’ is used, it means intermediate demand plus final demand (see table below). Which final demand block it is (for example domestic or imports) can be determined thorugh the CountryCountry identifier.
| Identifier | Meaning |
|---|---|
| t | Use table or intermediate demand |
| y | Final demand |
| w | Value added |
| v | Supply table |
| ty | Intermediate plus final demand |
| t,y | Same as previous |
| wt | Intermediate demand plus value added |
| w,t | Same as previous |
OriginAggregationInfo
This part of the label describes whether a data item is – in its supplying sectors – an aggregation of the MRIO data. For example if the data source identifies only one aggregate sector over which all supplying sectors in the MRIO are summed, the identifier is RSum. If the data source’s supplying sectors are aggregated according to concordance CLASS, the identifier is RAggCLASS. If the data source’s supplying sectors are identical to the MRIO’s supplying sectors, the identifier is NSum (no sum) or NAgg (no aggregation). For every RAggCLASS, there exists a concordance matrix between classification CLASS the classifications used in the Eora MRIO tables.
DestinationAggregationInfo
This part of the label describes whether a data item is – in its receiving sectors – an aggregation of the MRIO data. For example if the data source identifies only one aggregate sector over which all receiving sectors in the MRIO are summed, the identifier is CSum. If the data source’s receiving sectors are aggregated according to concordance CLASS, the identifier is CAggCLASS. If the data source’s supplying sectors are identical to the MRIO’s receiving sectors, the identifier is NSum (no sum) or NAgg (no aggregation). For every CAggCLASS, there exists a concordance matrix between classification CLASS the classifications used in the Eora MRIO tables.
ValuationInfo
This identifier holds the information if this constraint refers to basic price or purchasers price valuation. Possible ValuationInfos are
- ba for basic price
- pu for purchasers’ price
- pr for producers’ price
- m1 for trade margin
- m2 for transport
- t1 for tax
- t2 for subsidies
- m for all margins, and
- mt for all margins and taxes (mark- ups)
- fb for f.o.b. price
- cf for c.i.f. price
PriceInfo
This part of the label holds information about whether the data is represented in current price of constant price data. PriceInfo can be cur for current price or con for constant price.
Unit and Currency
Unit holds the information, in which unit the data is saved in the file. Possible values are
- 1 if data are represented in US$
- 10000 if data are represented in 10,000 ¥
- 1000000 if data are represented in million €
- 100000000 if data are represented in billion £
VersionInfo
This part of the label contains information on possible subsequent version of data from a certain source, for example UN SNA series.
Notes
This part of the label contains qualifications on the validity of data, for example about whether a value includes Financial Intermediation Services Indirectly Measured (FISIM) or not.
Source information
This part of the label holds any information on the data source, for example name, issuing organisation, tables, sections etc.