emissionfactor-nl
Forecasting grid emission factor for the Netherlands
Science Score: 44.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
✓CITATION.cff file
Found CITATION.cff file -
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
○DOI references
-
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (12.7%) to scientific vocabulary
Repository
Forecasting grid emission factor for the Netherlands
Basic Info
Statistics
- Stars: 0
- Watchers: 7
- Forks: 0
- Open Issues: 2
- Releases: 2
Metadata Files
README.md
Forecasting grid emission factor for the Netherlands
This repository contains a workflow to produce emission factor forecasts for the electricity mix of the Netherlands, up to 7 days ahead.
Model training
Model training is performed with AutoGluon, using the time series forcasting module.
As training data the total energy production and the energy mix's emission factor are used, sourced from the Nationaal Energie Dashboard with the produced solar and wind energy as "known covariates".

Model training result, validation on unseen data
The NED also provides forecasts for the solar and wind production. These are used in forecasting of the emission factor.

Example forecast, for 2025-01-28 - 2025-02-04
To produce a better forecast, the model also makes use of forecasted air temperature data.
Reproducing results
The Dockerfile contained in this reposity describes all steps you need to go through to train a model and to produce a forecast.
The container image allows easy production of forecasts. Docker engine is freely available on Linux.
To run the container image do:
docker
docker run \
-e NED_API_KEY \
--volume /local/path/to/output/dir:/data \
ghcr.io/esi-far/emissionfactor-forecast:0.2.0
The /data directory is the location where the prediction file should end up.
The container will also write the run-up data used in the prediction, as well as
NED's forecast for available wind and solar energy.
The environmental variable NED_API_KEY should be your ned.nl API key. Set this with:
sh
export NED_API_KEY=enter-your-key-here
More information on the NED API is available here.
[!IMPORTANT] If you want to use the forecast for commercial use, you will have get a commercial license and API key from OpenMeteo. To pass this API key, set the
OPENMETEO_API_KEYenvironment variable, and pass it to the container in the same way as the NED API key.
Note that the container's ouput files will be written as root. To avoid this you
can set the user ID, e.g.:
docker
docker run \
-e NED_API_KEY \
--volume /local/path/to/output/dir:/data \
--user 1000:1000 \
ghcr.io/esi-far/emissionfactor-forecast:0.2.0
If your user ID is 1000.
Building the container image
Note that for model training, historical NED and KNMI data is required, but this is removed
from the container image due to licensing restrictions. The required files are;
- NED.nl:
- wind, zeewind, zon, electriciteitsmix .csv files
- years 2021, 2022, 2023, 2024
- KNMI:
- Historical weather data from De Bilt (as .txt, i.e., uurgeg_260_2021-2030.txt)
These NED.nl files are available after registering.
Local installation, training and prediction
Instead of the containerized model, you can also work in a local environment.
- Download the data from NED.nl, see the previous section for which files you need
- Clone this repository, change working directory into the repository
- In a Python environment (3.10/3.11) do:
sh
pip install autogluon.timeseries --extra-index-url https://download.pytorch.org/whl/cpu
pip install -e .[dev]
- Set the following environmental variables:
MODEL_PATHshould refer to a directory where the trained model should be storedTRAINING_DATAshould refer to the directory with the training data .csv filesNED_API_KEYshould be your API key from NED.nl (available after registration)OPENMETEO_API_KEYshould be your OpenMeteo API key (only for commercial use).OUTPUT_PATHshould be the path where you want the output .csv files to be written to
- Now you can run
python src/emissionfactor_nl/train_model.pyto train the model - With
python src/emissionfactor_nl/predict.pyyou can generate a forecast based on the currently available forecast data from NED.nl
Owner
- Name: ESI-FAR
- Login: ESI-FAR
- Kind: organization
- Repositories: 1
- Profile: https://github.com/ESI-FAR
Citation (CITATION.cff)
# YAML 1.2
---
cff-version: "1.2.0"
title: "emissionfactor-nl"
authors:
- family-names: Schilperoort
given-names: Bart
orcid: "https://orcid.org/0000-0003-4487-9822"
- family-names: Vroegh
given-names: Thijs
orcid: "https://orcid.org/0000-0002-6311-0798"
date-released: 2025-01-14
repository-code: "https://github.com/ESI-FAR/emissionfactor-nl"
keywords:
- "co2 emission"
- "forecasting"
message: "If you use this software, please cite it using these metadata."
GitHub Events
Total
- Create event: 2
- Release event: 1
- Issues event: 8
- Delete event: 1
- Issue comment event: 2
- Push event: 10
- Pull request event: 2
Last Year
- Create event: 2
- Release event: 1
- Issues event: 8
- Delete event: 1
- Issue comment event: 2
- Push event: 10
- Pull request event: 2
Issues and Pull Requests
Last synced: 6 months ago
All Time
- Total issues: 6
- Total pull requests: 1
- Average time to close issues: about 1 month
- Average time to close pull requests: 22 minutes
- Total issue authors: 2
- Total pull request authors: 1
- Average comments per issue: 0.17
- Average comments per pull request: 0.0
- Merged pull requests: 1
- Bot issues: 3
- Bot pull requests: 0
Past Year
- Issues: 6
- Pull requests: 1
- Average time to close issues: about 1 month
- Average time to close pull requests: 22 minutes
- Issue authors: 2
- Pull request authors: 1
- Average comments per issue: 0.17
- Average comments per pull request: 0.0
- Merged pull requests: 1
- Bot issues: 3
- Bot pull requests: 0
Top Authors
Issue Authors
- BSchilperoort (3)
- github-actions[bot] (3)
Pull Request Authors
- BSchilperoort (1)