https://github.com/brightway-lca/mrio_common_metadata

Common Datapackage schema and utilities for MRIO tables
https://github.com/brightway-lca/mrio_common_metadata

bw3 life-cycle-assessment mrio-tables python

Last synced: about 2 months ago
JSON representation

Common Datapackage schema and utilities for MRIO tables

• Host: GitHub
• URL: https://github.com/brightway-lca/mrio_common_metadata
• Owner: brightway-lca
• License: bsd-3-clause
• Created: 2019-10-24T09:03:31.000Z (almost 6 years ago)
• Default Branch: master
• Last Pushed: 2023-05-24T11:48:35.000Z (over 2 years ago)
• Last Synced: 2025-06-08T21:28:32.050Z (4 months ago)
• Topics: bw3, life-cycle-assessment, mrio-tables, python
• Language: Python
• Size: 275 KB
• Stars: 0
• Watchers: 3
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGES.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# mrio_common_metadata

`mrio_common_metadata` provides three things:

* A guide on how the [Data Package](https://frictionlessdata.io/specs/data-package/) and [Table Schema](https://frictionlessdata.io/specs/table-schema/) specifications can be used to make MRIO table more consistently formatted and easier to use.

* Translations of some common MRIO tables to this format

* Utility code to help make the previous two objectives possible

# Separating data and metadata

MRIO tables are often given with weird offsets, and multiple or mixed column/row labels, e.g.

![Worksheet with column labels as rows](docs/images/worksheet-1.png)

![Worksheet with multiple column and row labels](docs/images/worksheet-2.png)

Working with this type of data requires writing custom code each time. It's a pain. The biggest problem is the mixing of two data types: The metdata on what each row and column represent, and the numerical table that forms the main body of the worksheet. `mrio_common_metadata` takes the position that these two data streams should be stored separately. It also requires that data be stored in common formats (compressed CSV) with metadata that meets the `Data Package` specification.