Entropy-based Chinese city-level MRIO table framework

Zheng, Heran; Többen, Johannes; Dietzenbacher, Erik; Moran, Daniel; Meng , Jing; Wang, Daoping; Guan, Dabo

doi:10.1080/09535314.2021.1932764

アイテム詳細

登録内容を編集ファイル形式で保存

一時保存へ追加

タグ情報を表示リリース履歴を表示詳細要約

公開

学術論文

Entropy-based Chinese city-level MRIO table framework

Authors

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;

URL

There are no locators available

フルテキスト (公開)

26957oa.pdf
(出版社版), 4MB

付随資料 (公開)

There is no public supplementary material available

引用

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. doi:10.1080/09535314.2021.1932764.

引用: https://publications.pik-potsdam.de/pubman/item/item_26957

要旨

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.