Deutsch
 
Datenschutzhinweis Impressum
  DetailsucheBrowse

Datensatz

DATENSATZ AKTIONENEXPORT

Freigegeben

Zeitschriftenartikel

Entropy-based Chinese city-level MRIO table framework

Urheber*innen

Zheng,  Heran
External Organizations;

/persons/resource/Johannes.Toebben

Többen,  Johannes
Potsdam Institute for Climate Impact Research;

Dietzenbacher,  Erik
External Organizations;

Moran,  Daniel
External Organizations;

Meng ,  Jing
External Organizations;

Wang,  Daoping
External Organizations;

Guan,  Dabo
External Organizations;

Externe Ressourcen
Es sind keine externen Ressourcen hinterlegt
Volltexte (frei zugänglich)

26957oa.pdf
(Verlagsversion), 4MB

Ergänzendes Material (frei zugänglich)
Es sind keine frei zugänglichen Ergänzenden Materialien verfügbar
Zitation

Zheng, H., Többen, J., Dietzenbacher, E., Moran, D., Meng, J., Wang, D., Guan, D. (2022): Entropy-based Chinese city-level MRIO table framework. - Economic Systems Research, 34, 4, 519-544.
https://doi.org/10.1080/09535314.2021.1932764


Zitierlink: https://publications.pik-potsdam.de/pubman/item/item_26957
Zusammenfassung
Cities are pivotal hubs of socioeconomic activities, and consumption in cities contributes to global environmental pressures. Compiling city-level multi-regional input-output (MRIO) tables is challenging due to the scarcity of city-level data. Here we propose an entropybased framework to construct city-level MRIO tables. We demonstrate the new construction method and present an analysis of the carbon footprint of cities in China’s Hebei province. A sensitivity analysis is conducted by introducing a weight reflecting the heterogeneity between city and province data, as an important source of uncertainty is the degree to which cities and provinces have an identical ratio of intermediate demand to total demand. We compare consumption-based emissions generated from the new MRIO to results of the MRIO based on individual city input-output tables. The findings reveal a large discrepancy in consumption-based emissions between the two MRIO tables but this is due to conflicting benchmark data used in the two tables.