Update electricity demand profiles

[tgilon]

Description

This issue suggest to add options in PyPSA-Eur to use the custom electricity demand profiles of TYNDP. This feature is expected to create new rules and modify a set of rules (see bellow).

Having a lot of small switches is probably better to contribute some sections upstream and merge code from upstream. On the other hand, too much switches can make it hard to maintain. An option could be to have a new default configuration file. Another could be to have a configuration file specific to the project on top of the default configuration file.

Tasks

• Archive ENTSO-E data on Zenodo by @daniel-rdt
• Implement raw data processing in separate script by @daniel-rdt
• Create switches in the configuration file by @tgilon
• Add parameters in add_electricity and prepare_sector_networkby @tgilon

Workflow

1. build_shapes
   • Add a column with the bidding zones in the nuts3 shape files
2. (new) retrieve_tyndp_databundle
   • retrieve TYNDP data bundle from Zenodo
3. (new) build_tyndp_data
   • prepare the data input for build_electricity_demand (electricity) and prepare_sector_network (other carriers)
4. build_electricity_demand
   • By default, use data/electricity_demand_raw.csv (OPSD data) and data/load_synthetic_raw.csv (demand calculator)
   • Need to use TYNDP data bundle data
   • Currently, linear interpolation is used to fill gaps. This has to be disabled by default for TYNDP data (to use them as is).
   • Manual adjustments usage should raise a warning (as this is not supported by default for TYNDP data)
   • Data are given per bidding zones. We aim to keep this granularity and will change subsequent rules to work with it.
5. build_electricity_demand_base
   • Disaggregate electricity demand for base regions
   • TYNDP data will not be given per country (as for OSPD) but per bidding zones.
   • If it helps, we can live with electricity demand assigned to closest node
   • Need to add a warning if clustering configuration is not per bidding zone when using ENTSO-E data
   • Adjust shapes / groupby to match bidding zones
6. cluster_network
   • We want to avoid breaking changes and add a warning
   • No specific work expected here
7. add_electricity
   • Load attached to the network
   • no specific work expected here
8. prepare_sector_network
   • add_storage_and_grids
     • H2 electrolysis, fuel cell, turbines, storages, H2 network added to network
     • Batteries added to network
     • Methanation, SMR, SMR CC added to network
   • Transport:
     • Electric transport demand will be addressed in https://github.com/open-energy-transition/openmod-at-entsoe/issues/10
     • Oil and H2 transport demand can be disabled using shares in the configuration file
     • Always enable distribution as TYNDP model both prosumer and street nodes
     • Only passenger cars are considered, to be addressed by https://github.com/open-energy-transition/openmod-at-entsoe/issues/10
   • Heating:
     • Considering the fact that most of the heat demand is included in the profiles provided (except HHP), loops on HeatSystem are set to [] when TYNDP load is used
     • district heating is set exogenously in supply tool
     • waste heat ?
     • do we need a new function only for HHP ? As HHP will not be expanded, make sense to only add existing in add_existing_baseyear
   • Industry:
     • Shipping and aviation are included over here (e-kerosene, e-diesel)
     • Syntethic fuel modeling will be addressed in https://github.com/open-energy-transition/openmod-at-entsoe/issues/11
     • Fischer-tropsch added here
9. add_existing_baseyear
   • Check existing technologies added
   • Add existing HHP ? Will be addressed by https://github.com/open-energy-transition/openmod-at-entsoe/issues/12

Notes

• electricity_demand.csv from PyPSA-Eur is a CSV file with hourly resolution data as rows and countries as columns. Electricity demand profiles of TYNDP have climatic years as column and tabs for each nodes. This means that the configuration has to take CY into account if TYNDP data is used.
• Shape files per bidding zones
  • GDP and population data are available at NUTS3 level