15min vs 60min data

[borg42]

Thank you for your effort!

I think this mixes up the 15min and 60min data. Looks like it first parses the 15min data (as if it were 60min data) and then overwrites the first 24 positions with 60min data.

I think you need another parameter with resolution=PT15MIN/PT60MIN and search for

pe_child.tag.endswith("resolution")

and filter accordingly. Then it will work.

Edit: I just realized that you are properly testing with a country that only has 60min data. You can try '10Y1001A1001A82H' (DE_LU) to see the problem.

[GeneralCP]

Hey. what parameters are you using? Because when i run this for NL I get a list of hourly data back. I confirmed this by running the URL directly. I don't see 15m data.

Op vr 4 okt 2024 om 22:59 schreef Olaf Lüke @.***>:

Thank you for your effort!

I think this mixes up the 15min and 60min data. Looks like it first parses the 15min data (as if it were 60min data) and then overwrites the first 24 positions with 60min data.

I think you need another parameter with resolution=PT15MIN/PT60MIN and search for

pe_child.tag.endswith("resolution")

and filter accordingly. Then it will work.

— Reply to this email directly, view it on GitHub https://github.com/GeneralCP/entsoe2/issues/1, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABURJDFQEHJ55TX2I5XRYFTZZ36SDAVCNFSM6AAAAABPMTBIKWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU3DOMZWHEYTQMA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[borg42]

Try 10Y1001A1001A82H for the country (DE_LU)

[GeneralCP]

I fixed this in the latest version. https://github.com/EnergieID/entsoe-py is also fixed now so might want to go back to that. This version is still a lot lighter though.