Compare GHG footprints across databases
Align indicator definitions, regional identities and units before comparing source estimates.
Inputs · Local EXIOBASE 3.10.2, Eora26 and ADB releases with their extensions. The companion notebook lists the exact years and expected folder structure.
Accounts → Characterization → Regional totals → Common units → Chart
Indicator, geography and units#
Indicator
The example requests AR5/GWP100. Already characterized source CO2eq totals keep their original factors.
Geography
Source-specific labels are reconciled to ISO3 before countries are selected.
Units
Regional totals are converted to a common magnitude before plotting.
Analysis steps#
1 · Check accounts
Inspect the selected profiles and the gas rows actually present in each source. A supported profile does not imply identical coverage.
2 · Characterize
db.calc_ghg(ipcc_report="AR5", time_horizon=100)
ghg = "GHG AR5 GWP-100"
db.calc_all(["f"])
This block applies to a compatible IOT with the required gas accounts. See GHG characterization and footprints for source-total limitations.
3 · Build totals
direct_fd = db.EY.loc[ghg].groupby(level=0).sum()
pba = db.E.loc[ghg].groupby(level=0).sum() + direct_fd
embodied_fd = db.f.loc[ghg] @ db.Y
cba = embodied_fd.groupby(level=0).sum() + direct_fd
f @ Y retains final-demand columns, so their region identifies the
consumer. F instead retains production-node columns and cannot
be grouped by origin to obtain consumption-based totals. Direct
final-demand emissions are added once to both accounting views.
The companion’s harmonization step aligns regional labels and units. For partial numerical results, handle NaN explicitly before aggregating.
4 · Compare
Plot the selected countries and years. Differences still reflect source coverage, accounts and modelling choices; a shared label alone does not make the estimates equivalent.
Start with Calculate greenhouse gas emissions for the single-database workflow.