You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current logic of separate the data of the SDAC and EXAA when retrieving German prices is to request the 60min resolution for SDAC and the 15min resolution for EXAA. This feels like an unsustainable way, definitely when the SDAC would change to also use the 15min resolution. Now currently the response contains a 'classificationSequence_AttributeInstanceComponent.position' tag which is 1 for SDAC and 2 for EXAA. The field can even be passed as parameter to only receive one or the other. It could be a nice way of clearly distinguish the datasets. But I can't find an explanation of the 'classificationSequence_AttributeInstanceComponent.position' in the documentation anywhere so I am just guessing a.t.m. My proposal would be to start using this field instead of the resolution if we can confirm its meaning.
The text was updated successfully, but these errors were encountered:
Mmm yes I did a quick test with receiving german data which worked: https://web-api.tp.entsoe.eu/api?documentType=A44&securityToken=<SECRET>&periodStart=202410060000&periodEnd=202410071300&in_domain=10Y1001A1001A82H&out_domain=10Y1001A1001A82H&classificationSequence_AttributeInstanceComponent.Position=1
But I now also tested it for the belgian zone and it does not return any data. Seems like it only works for the german zone then which makes it less usable.
The current logic of separate the data of the SDAC and EXAA when retrieving German prices is to request the 60min resolution for SDAC and the 15min resolution for EXAA. This feels like an unsustainable way, definitely when the SDAC would change to also use the 15min resolution. Now currently the response contains a 'classificationSequence_AttributeInstanceComponent.position' tag which is 1 for SDAC and 2 for EXAA. The field can even be passed as parameter to only receive one or the other. It could be a nice way of clearly distinguish the datasets. But I can't find an explanation of the 'classificationSequence_AttributeInstanceComponent.position' in the documentation anywhere so I am just guessing a.t.m. My proposal would be to start using this field instead of the resolution if we can confirm its meaning.
The text was updated successfully, but these errors were encountered: