updated FR parser to enable historical backfill

[ghost]

Issue

We noticed that we couldn't refetch data that was older than 9 months using the current dataset. We know that RTE publishes final data at Y+1 and we want to be able to update our dataset with the most up-to-date data.

Description

the aim here is to enable historical refetch. the historical data is available in the dataset eco2mix-national-cons-def

Preview

2023-03-26

2021-12-31

Double check

• I have tested my parser changes locally with poetry run test_parser "zone_key"
• I have run pnpx prettier --write . and poetry run format to format my changes.

[netlify]

✅ Deploy Preview for phenomenal-syrniki-c5ceaa ready!

Name	Link
🔨 Latest commit	a16ed21
🔍 Latest deploy log	https://app.netlify.com/sites/phenomenal-syrniki-c5ceaa/deploys/6421c56702df340008016e52
😎 Deploy Preview	https://deploy-preview-5240--phenomenal-syrniki-c5ceaa.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[VIKTORVAV99]

Note this is not a review of the code itself but the implementation of the new data source. In #4853 there was some concerns about validating the data source and making sure all the data was valid before we proceeded. Is this still the case?

If not might it not be better to proceed with #4853 and split France up in the process when switching the parsers (and aggregating it again together with corsica)?

[ghost]

If not might it not be better to proceed with #4853 and split France up in the process when switching the parsers (and aggregating it again together with corsica)?

Hi @VIKTORVAV99, I don't know how much we want to prioritize splitting FR into regions. We realised we couldn't backfill and that the data can be significantly modified and thought that this was more important to the Sales team. As you can see on the OpenData page, the data we collect is provisional.

[VIKTORVAV99]

If not might it not be better to proceed with #4853 and split France up in the process when switching the parsers (and aggregating it again together with corsica)?

Hi @VIKTORVAV99, I don't know how much we want to prioritize splitting FR into regions. We realised we couldn't backfill and that the data can be significantly modified and thought that this was more important to the Sales team. As you can see on the OpenData page, the data we collect is provisional.

Perhaps we should increase the priority of https://github.com/electricitymaps/electricitymaps/pull/3230, since it would allow us to fetch estimated data (separate from validated data)? Seems like yet another scenario where it would be beneficial.

I'll do a full code review this afternoon as well 👍🏻

[unitrium]

Just some naming suggestions but looks good to me!

[VIKTORVAV99]

Everything looks good to me with the exception of the type issue. If you can take care of that it would be greatly appreciated.