Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DE_load_old vs. DE_load_new #20

Closed
uvchik opened this issue Sep 7, 2017 · 4 comments
Closed

DE_load_old vs. DE_load_new #20

uvchik opened this issue Sep 7, 2017 · 4 comments

Comments

@uvchik
Copy link

uvchik commented Sep 7, 2017

What is the difference between DE_load_old and DE_load_new? In the documentation both are the "Total load in Germany in MW" but in 2015 the values are different.

@jgmill
Copy link
Member

jgmill commented Nov 10, 2017

The data are from two different platforms, although both are maintained by ENTSO-E: DE_load_old is taken from the ENTSO-E Data Portal, which was discontinued in 2016 and replaced by the ENTSO-E Power Statistics. DE_load_new is taken from the ENTSO-E Transparency Platform

I had also noted that the reported values differ. In Germany in 2015, the load reported on the Data Portal is on avarage 3.1 GW or 5.5 % higher than that reported on the Transparency Platform, but this difference also changes every hour.

I am not sure where these differences are rooted, but my best guess is that the reason lies with the different reporting deadlines: Values on the Transparency Platform have to be reported "At the latest H+1 after the end of the operating period". For the Data Portal/Power Statistics, the data seems to be published only after the end of every month, which might allow for more accurate metering.

In priciple, the differences could also be an issue of different definitions of "load": The definition applied on the The ENTSO-E Transparency Platform is as follows (while I believe that the Data Portal/Power Statistics use the same definition, this is not 100% clear):

  • The sum of power generated by plants on both TSO/DSO networks, from which is deducted
    • the balance (export -import) of exchanges on interconnections between neighbouring bidding zones.
    • the power absorbed by energy storage resources.

The ENTSO-E Glossary also has this definition:

  • The consumption corresponding to the short-term average active power absorbed by all installations connected to the transmission grid or to the distribution grid
    • excluding consumption for pumping of the pumped-storage stations
    • excluding consumption of power plants auxiliaries
    • including network losses.

European electricity consumption data is a tricky subject, and neither of the hourly resolution time series are totally accurate. If you want to dig deeper: A former colleague did a comparison of different sources a while ago, not yet including the ENTSO-E Transparency Platform however.

As a final note: The documentation to the Agorameter estimates that the load values from the ENTSO-E Transparency Platform underestimate the actual situation on average by 8799.8 MW in 2017.

@uvchik
Copy link
Author

uvchik commented Nov 10, 2017

Thank you very much for this detailed answer.

@uvchik uvchik closed this as completed Nov 10, 2017
@jgmill jgmill pinned this issue Mar 5, 2019
@jgmill
Copy link
Member

jgmill commented May 25, 2020

Please note that I have changed the notation of the load columns since version 2018-03-13 of the time series data package:
DE_load_old has become DE_load_actual_entsoe_power_statistics
DE_load_new has become DE_load_actual_entsoe_transparency

As of Version 2015-05-15, The Data Portal/Power Statistics column is scaled with the country specific coverage ratio.

@jgmill
Copy link
Member

jgmill commented May 26, 2020

ENTSO-E had discontinued the Power Statistics in November 2019. An archive of historical data is now available, with the latest hourly load values provided for 31.10.2019.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants