Confusion between PeriodStart/End and PeriodStartUpdate/EndUpdate?

[alp-yg]

Hi there,

I'm trying to look at outages published on the Transparency Platform, and I'm having some dates problems.

From what I understood of the API, it is possible to specify in a request two different intervals. One representing the dates/times of the last update of outages, and the other representing the dates/times of the outage itself. If I'm correct, the former is set using the parameters PeriodStartUpdate and PeriodEndUpdate, and the latter using PeriodStart and PeriodEnd.

However, in your EntsoePandasClient, it looks like you're mixing them, and more precisely in _query_unavailability where you use start/end (passed as PeriodStart/PeriodEnd in the actual request) to truncate the dataframe on its index. However, this index represents the last update time, so shouldn't this truncation be done on periodstartupdate/periodendupdate when they are given?

Best, Yannick

[fboerman]

hi @alp-yg could you provide a code example?

[aappxx]

Hi @fboerman!

I'm also trying to query outages using EntsoePandasClient, but to no avail. The query_unavailability_of_generation_units method does not return outages between start and end parameters. From my observations, it returns rows, which satisfy two rules at the same time:

• _create_doctime (index of returned data frame) is between parameters start and finish,
• column end is earlier than parameter end.

This behaviour is different from the one observed on Entsoe transparency platform, where outages occurring between from and to on Day Range picker are listed.

Regards

[andreadib]

Hi @alp-yg ,

I have also encountered similar issue. Did you manage to understand this?

Thanks in advance. Regards

[fboerman]

hi I still dont fully understand this, can one of you provide a clear code snippit in which this occurs? @andreadib @aappxx