Scope gsps legacy data saved in data-platform

[peterdudfield]

Every few months NESO create new GSPS and make some legacy

Here is some information of the ML and software work thats required to update our systems - https://app.notion.com/p/openclimatefix/Updates-for-new-GSPS-36f9894e1aa98090b77ee774ecb72cee

Currently we store legacy gsps data in the solar-consumer and the blend

I think it makes sense to move this to the data-platform. We could store this in the metadata. We should come up here with a design of how we store this data in the metadata

[peterdudfield]

One idea is we store in the metadata, something like this

metadata = {
"legacy_gsp_id_weights": {
"343":"1.0"
"344":"1.0"
}

on gsp_id 44. This would mean add up 343 and 344 to make gsp 4

We can then load these from the data-platform and do the same blend and filling in

[peterdudfield]

@devsjc would you be able to review this? i.e. say it s a good idea or not. Then afterwards we can think about how we implement it