search

electricitymaps / electricitymaps-contrib

A real-time visualisation of the CO2 emissions of electricity consumption
https://app.electricitymaps.com
GNU Affero General Public License v3.0
3.52k stars 937 forks source link

Add North Sea Link (GB<->NO-NO2) #2832

Closed q-- closed 3 years ago

q-- commented 3 years ago

National Grid and Statnett are building an interconnector (1400MW) between Great Britain and South-West Norway (should be NO-NO2 based on physical location).

Installation of subsea cables is only planned to be finished in 2021, but apparently the interconnector has already been added to ELEXON and possibly broken that parser.

So, it seems to be possible to add the exchange to ElectricityMap. I can't find it in ENTSO-E yet though, so if we want to use that one instead of ELEXON we'll have to wait.

ilfrich commented 3 years ago

The new exchanges (3 of them, 2 to FR, 1 to NO) haven't been added yet. Probably best to add them via ELEXON, will have a look.

ilfrich commented 3 years ago

Not 100% sure, but does the direction of the exchange matter? It looks like ELEXON returns positive and negative values depending on the flow, but the EXCHANGES listed in the parser seem to depend on the direction of the exchange and how it is defined.

They've also created 2 more exchanges to France (currently not providing any values yet, one provides 0, the other None), so there's probably some need to refactor the parser to support multiple columns per exchange (FR->GB). I can extend this, but would need to know if the new link is NO-NO2->GB or GB->NO-NO2 - and the same question for the 2 new French connections.

ilfrich commented 3 years ago

Did some more digging. It looks like ELEXON provides all their data under the following convention:

The convention adopted is that a positive value represents import into the GB Transmission System, whilst a negative value represents an export from GB.

Given that, the ELEXON parser currently handles the FR->GB and BE->GB exchanges incorrectly (basically inverting the actual power flow). I'm assuming for FR->GB this has to do with the ENTSOE parser being used to fetch the forecast of the exchange, which might provide the information in that direction. Additionally, the BE->GB exchange seems to be entirely handled by ENTSOE

ilfrich commented 3 years ago

Ok, the new link is added. I figured out the "direction" issue eventually. The answer became obvious once I saw the result, given the sorted_zone_keys are returned, and not the keys passed in.