feat: introduce offshore wind hubs topology

[tgilon]

Closes #48. This PR builds on top of #53.

Changes proposed in this Pull Request

This PR introduces the topology of offshore wind hubs. It reads in the Offshore Hub Modelling Inputs from the TYNDP 2024. The grid topology (buses coordinates and transmission capacities) is exogenously set using these data.

The following schematic illustrates an overview of the 2024 TYNDP Offshore Hub topology as implemented in this PR:

Tasks

• Prepare reference grid data set
• Add reference grid data to network model
• Map onshore H2 nodes to Z2 nodes
• Set economic lifetime to 25y
• Ensure that the radial connections are made directly to the home land node
• Implement TYNDP offshore technology modelling approach
• Set existing capacities
• Address DEOH002 discrepancy
• Filter data for configured countries
• Fix H2 efficiencies
• Apply PECD capacity factors for offshore wind
• Validate myopic approach for existing capacities
• Add a constraint for H2 / DC potentials
• Add a constraint for zone potentials
• Remove pypsa-eur offwind technologies
• Check new files licensing
• Address final # ToDo in the code

Workflow

1. (new config) sector:offshore_hubs defines whether TYNDP offshore hubs must be added to the network.
2. retrieve_tyndp_bundle retrieves the raw offshore buses (tyndp_2024_bundle/Offshore hubs/NODE.xlsx) and the reference grid data (tyndp_2024_bundle/Offshore hubs/GRID.xlsx).
3. (new) build_tyndp_offshore_hubs processes the data to create a clean files that define the buses, the grid, the electrolyzers and the generators for the selected scenario and planning horizons.
4. prepare_sector_network add the offshore buses and the reference grid to the network.
   • For each node, defines an H2 and AC bus using provided coordinates
   • Add H2 and DC grid connections between hubs, and between hubs and onshore nodes
   • Add power production and H2 production units
   • Add electrolyzers

Open Issues

• Some nodes have coordinates incorrectly placed on land.
• Cost assumptions are missing for parts of the reference grid. To address this, any link for which investment assumptions are missing will be considered non-extendable and zero costs.
• No units have been specified for the cost assumptions: for CAPEX, we assume kEUR/MW, and for OPEX, assume kEUR/MW/a
  • n.links.capital_cost default unit is EUR/MW/period.
    • capital_cost = (annuity_factor * CAPEX + OPEX) * nyears
    • We use a 25y economic lifetime (not documented in the methodology but has been confirmed).
• Formatting issues in the tables on p104 of Annex II of the Methodology report
• The use and data of Offshore Hubs/GENERATORS.xlsx file is not documented. A detailed notebook has been necessary to validate assumptions.
  • Existing capacities will be read from the LAYER_POTENTIAL sheet, utilizing technology shares specified in EXISTING for hydrogen-generating capacities. A discrepancy of 526 MW for DEOH002 in 2045 (across all scenarios) is noted when comparing existing capacities with ZONE_POTENTIAL. It remains uncertain which of the two values is correct: 5828.55 MW from LAYER_POTENTIAL or 6354.55 MW from ZONE_POTENTIAL. Currently, the value of 5828.55 MW is used.
  • Potentials will be obtained from both the LAYER_POTENTIAL and the ZONE_POTENTIAL sheets. LAYER_POTENTIAL will establish a technology level constraint, while ZONE_POTENTIAL will restrict expansion across all technologies at each node. The same 526 MW discrepancy in DEOH002 (across all planning horizons and scenarios) has been noted and needs to be addressed to ensure that existing capacities do not exceed their potential. Currently, the value ZONE_POTENTIAL value is corrected at 5828.55 MW.

Notes

Offshore hubs coordinates

Checklist

• I tested my contribution locally and it works as intended.
• Code and workflow changes are sufficiently documented.
• Changed dependencies are added to envs/environment.yaml.
• Changes in configuration options are added in config/config.default.yaml.
• Changes in configuration options are documented in doc/configtables/*.csv.
• Changes in configuration options are added in config/test/*.yaml.
• Sources of newly added data are documented in doc/data_sources.rst.
• A release note doc/release_notes.rst is added.