Issue with Hydro Pumped Storage values
See original GitHub issueHi,
The entsoe pandas client (probably also the Raw client but I didn’t tested it), does not take into consideration the “negative values” of the Hydro Pumped Storage. This production is able to pump water and so have a negative production (it’s a charge not a generator).
The ENTSOE API website does the difference
But the Python client does not :
I don’t know how to do the difference too in the raw XML
<TimeSeries>
<mRID>5</mRID>
<businessType>A01</businessType>
<objectAggregation>A08</objectAggregation>
<inBiddingZone_Domain.mRID codingScheme="A01">10YFR-RTE------C</inBiddingZone_Domain.mRID>
<quantity_Measure_Unit.name>MAW</quantity_Measure_Unit.name>
<curveType>A01</curveType>
<MktPSRType>
<psrType>B10</psrType>
</MktPSRType>
<Period>
<timeInterval>
<start>2019-05-20T05:00Z</start>
<end>2019-05-20T06:00Z</end>
</timeInterval>
<resolution>PT60M</resolution>
<Point>
<position>1</position>
<quantity>1902</quantity>
</Point>
</Period>
</TimeSeries>
<TimeSeries>
<mRID>6</mRID>
<businessType>A01</businessType>
<objectAggregation>A08</objectAggregation>
<outBiddingZone_Domain.mRID codingScheme="A01">10YFR-RTE------C</outBiddingZone_Domain.mRID>
<quantity_Measure_Unit.name>MAW</quantity_Measure_Unit.name>
<curveType>A01</curveType>
<MktPSRType>
<psrType>B10</psrType>
</MktPSRType>
<Period>
<timeInterval>
<start>2019-05-20T03:00Z</start>
<end>2019-05-20T05:00Z</end>
</timeInterval>
<resolution>PT60M</resolution>
<Point>
<position>1</position>
<quantity>1236</quantity>
</Point>
<Point>
<position>2</position>
<quantity>308</quantity>
</Point>
</Period>
</TimeSeries>
The first TimeSeries should be considerated as positive and the second as negative.
I have send an email to ENTSO-E platform for more information.
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Pump it up? The economics of stored-hydro energy may not ...
The value of pumped storage will only increase as more intermittent renewable resources are added to the grid in our efforts to meet...
Read more >Challenges and Opportunities For New Pumped Storage ...
In today's pumped storage development community, project proponents attempt to minimize these issues by focusing on new project sites where proposed ...
Read more >A review of pumped hydro energy storage - IOPscience
Pumped hydro energy storage (PHES) comprises about 96% of global storage power capacity and 99% of global storage energy volume. Batteries occupy most...
Read more >Pumped Storage Hydropower | Department of Energy
According to the 2021 edition of the Hydropower Market Report, PSH currently accounts for 93% of all utility-scale energy storage in the United...
Read more >Market Opportunities and Challenges for Pumped Hydro in an ...
This paper explores several market opportunities and challenges for pumped storage hydropower related to ongoing changes in the electric power grid.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
1st column should be gross generation (“Actual Aggregated”), 2nd column should be the electricity used to operate the power plants (“Actual Consumption”). Not every country has live gross generation, and therefore directly publishes net generation (1st minus 2nd column).
According to ENTSO-E documentation, "Net Generation is preferred however gross generation could be used where it is available with the better precision. TSOs should decide gross or net generation will be used but the net/gross characteristic should be consistent per Bidding zone. "
Your solution leaves it to the user whether gross or net generation should be retrieved (when available). Vote to merge this pull request.
Solution deployed in 0.3.2