Discuss: Store price data

Verification

• I have searched the existing issues to ensure this feature has not already been requested.

Provide a detailed description of the proposed feature.

Store price data in the data-platform

What is the motivation for the feature?

We currently collect DA price data from Entsoe everytime the NL Consumer and Forecast runs. This seems slightly over kill, and we should only collect this one.

Its possible to believe that we might need to store more of this data in the future

Outline a potential approach or solution (optional).

• New schema called prices
• one table thats stores the prices, columns could be, location_uuid, timestamp_utc, value, market (note market could be in a separate table to save space rather than reparting 'NL_DA')
• write function
• read function

Note it is quite similar to an observation (just not MW, its £/MW), so it might be possible to squeeze it into there

Start by examining how observations are stored and how DA price data is collected for the NL Consumer and Forecast runs. Define the prices schema and decide whether it belongs in the observation model, then add the write and read paths. Done means price data is collected once and can be stored and retrieved for the proposed location, timestamp, value, and market fields.