ENTSOE: PL->UA exchange is missing

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.48k stars 925 forks source link

ENTSOE: PL->UA exchange is missing #602

Closed corradio closed 7 years ago

corradio commented 7 years ago

Hello @Dalius-ENTSO-E ,

It seems like there's two exchanges between PL and UA. It seems like the one with id 10YUA-WEPS-----0 is missing (whereas it is working with all other exchanges to/from UA), whereas the one with 10Y1001A1001A869 works. The above screenshot makes me think there could be a mistake because there shouldn't be two entries in the list?

Thanks for your help.

Olivier

Dalius-ENTSO-E commented 7 years ago

No, all is correct. Let me explain what is there. PL have lines with 10YUA-WEPS-----0 (Burshtyn island) but all lines are disconnected. There is only one active connection between PL and UA (DobTPP island). DobTPP is working through one line to PL and flow can be only from UA-DobTPP to PL. This is why data is not expected for one direction (PL>UA-DobTPP) and data exists only for direction UA-DobTPP (10Y1001A1001A869 ) > PL . We are testing new area concept to UA on our test platform and names of UA areas will change soon.

corradio commented 7 years ago

Hi @Dalius-ENTSO-E,

Thanks for the explanation. We are working on a country-level for PL and UA (and neighbouring countries). For PL, we use the identifier 10YPL-AREA-----S For UA, there are two country identifiers 10Y1001A1001A869 and 10YUA-WEPS-----0. We use 10YUA-WEPS-----0 because it has exchange data for HU, RO and SK (and not PL as you said) Shouldn't there be only one country-level identifier, thus enabling us, with a single UA identifier, to fetch the exchanges between UA and neighbouring countries?

Thanks for your help!

Olivier

Dalius-ENTSO-E commented 7 years ago

Aggregation of commercial schedules on country level is implemented only for Germany. We will add aggregation of commercial schedules on country level for all countries starting from 1/1/2018. There will be only one identifier for UA only when we will change area concept for UA. btw., EIC code for country and bidding zone UA will be 10Y1001C--00003F . Currently, there are 2 identifiers for UA: 10YUA-WEPS-----0 for (WEPS) borders with HU, RO and SK, and 10Y1001A1001A86 for the border with PL. These EIC codes will remain on control area level.

corradio commented 7 years ago

Thanks for the clarification.

On Fri, Aug 4, 2017 at 2:28 PM, Dalius-ENTSO-E notifications@github.com wrote:

Aggregation of commercial schedules on country level is implemented only for Germany. We will add aggregation of commercial schedules on country level for all countries starting from 1/1/2018. There will be only one identifier for UA only when we will change area concept for UA. btw., EIC code for country and bidding zone UA will be 10Y1001C--00003F . Currently, there are 2 identifiers for UA: 10YUA-WEPS-----0 for (WEPS) borders with HU, RO and SK, and 10Y1001A1001A86 for the border with PL. These EIC codes will remain on control area level.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/tmrowco/electricitymap/issues/602#issuecomment-320236175, or mute the thread https://github.com/notifications/unsubscribe-auth/ABlEKE2X5R5rQqrrQaj13jXPDFO26Ng8ks5sUw5RgaJpZM4ODt2f .