The Power Station Dictionary is a site that enables mapping between various power plant ids and automatically extracts data relating to those plants from Frictionless Data packages.
N.b. This project is currently in active development.
Any and all contributions are very welcome. If you are less comfortable editing via GitHub please contribute via this Google Sheet (GitHub is still preferred if possible).
Existing work into increasing the visibility of energy data has focused on improving the ability of humans to find datasets, which has historically been a key issue within a highly fragmented energy data landscape. Groups such as the Energy Data Taskforce have prompted a new wave of metadata standardisation and data cataloguing initiatives which have gone a long way to solving this issue, opening up new opportunities such as the creation of digital twins of the power grid. However, these new opportunities bring new challenges. To enable a digital twin of the energy system we need to be able to "describe relationships between assets and datasets", requiring two core extensions to our existing toolset:
These additions enable us to move from improving the ability of humans to discover datasets to making it easier for machines to automatically find and extract relevant data - a need that will only increase as the number and size of datasets continues to grow. The benefits extend beyond our digital colleagues though - by pivoting data exploration to be about finding objects/assets, which then reveal the datasets (and attributes) they are linked to, we can create a more intuitive search experience. Similar to Google’s move from searching for "Things not Strings", the data dictionary lets us search for "Assets not Datasets".
To illustrate the benefits of such a framework we are building a pilot dictionary focused on improving the discoverability, linkage, and automated extraction of data relating to power stations on the GB system. Power stations were chosen due to the high number of datasets they relate to, the wide range of ids used to describe them, and the current duplication in efforts to link them across industry and academia. We will then demonstrate how the dictionary can be used for analysis with two case studies: one researching the carbon intensity of individual generators by matching power output and carbon emission datasets, the second linking wholesale price and renewable subsidy data to help explain why wind subsidies have fallen below the average market price.
The dictionary is composed of two files, a csv containing ids that relate to different power stations and a json containing metadata written as an extension to the Frictionless Data Tabular schema. "Frictionless Data (FD) is an open-source toolkit that brings simplicity to the data experience" through an open-source standard that defines a specification for describing metadata relating to different types of datasets. Once a dataset has been described using the specification it then becomes incredibly easy to load it using different programming languages as well as export it into a wide range of different formats. What makes FD different to most other specifications is that they provide a comprehensive way to describe individual columns within a dataset, including their formats and constraints.
The majority of the schema is the same as the Tabular Schema published by FD. The core change is the use of foreignKeys
to link to external datasets that use ids specified in the dictionary, a separate attributes
entry then describes the columns which should be extracted from the dataset. The hierarchy
attribute for each column then describes whether the ids in that column have a same-as
or part-of
relationship with the asset they’re linked to. A further url_format
entry then provides a way to convert specific IDs into urls (e.g. with wikidata ids).
The datasets linked to the dictionary must be described using the FD tabular schema, however, the metadata does not need to be stored adjacent to the raw source and could be generated by a third party rather than the original data provider. Data-providers from within the energy sector already using this format include Public Utility Data Library and Open Power System Data. As well as being able to link into the dictionary by publishing your datasets using this standard you can make use of a wider ecosystem of data tools.
Once the dictionary has been created a Python library then uses it to programmatically identify the different assets it contains, and then extract data relating to those assets from the datasets linked to the dictionary. The generation steps are as follows:
To install the powerdict
library please run:
pip install powerdict
To set-up a new environment you can run the following from the batch_scripts directory
setup_env
Alternatively you can run these commands
call conda env create -f environment.yml
call conda activate PowerDict
call ipython kernel install --user --name=PowerDict
To publish the powerdict
module to PyPi simply run the following from the batch_scripts directory
pypi_publish
or follow these commands
call conda activate PowerDict
call python setup.py sdist bdist_wheel
call twine upload --skip-existing dist/*
When prompted you should enter your PyPi username and password
After this you will be able to install the latest version of powerdict using pip install powerdict