Brightcon 2025, hackathon & courses in Grenoble and online

Climate change constitutes a global challenge affecting across all regions of the world, producing significant risks to human health and natural ecosystems. Allocating global greenhouse gas emissions is necessary to identify effective mitigation strategies.
The methodology of environmentally extended multiregional input-output (EEMRIO) analysis enables the calculation of environmental impacts by assigning emissions and other environmental burdens to the locations where they are produced. This methodology is based on input-output matrix, an economic tool that models the interdependencies between different sectors of the economy, usually on an annual basis. Adding environmental data, is possible to determine the environmental footprint of goods and services across the supply chain.
However, one of the main challenges of applying EEMRIO lies in the complexity and size of the available databases, such as EXIOBASE, EORA or WIOD. These datasets are rich in information, but it could be difficult to integrate into life cycle assessment (LCA) tools, due to their structure and scale, hindering the implementation of this methodology.
This study addresses this limitation by developing a routine to import EXIOBASE (hybrid version) into Brightway 2.5. Two approaches are explored: creating a datapackage, and generating a database. Once the data is successfully integrated, it is possible to use conventional Brightway 2.5 to carry out a LCA of products. The datapackage approach presents some advantages, such as the reduced runtime when executing the code, while the database approach offers the advantage of requiring only a single import, facilitating easier reuse in future analyses.
The code imports emission data not only for quantifying climate change impacts but also for almost all categories of Environmental Footprint 3.1 (EF) method, and it can likewise be extended to evaluate social impacts within the social footprint method. Future lines of this work include adding the database created to other LCA software, e.g. Activity Browser.