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
I was thinking of using this data source as a replacement for global_energy_mix.json, when computing CO2 emissions.
Have you already considered a method for people to include different APIs of this kind as plugins? I noticed another related question regarding using ElectricityMap, but it would be interesting to incorporate data from freely accessible API than rely on commercial ones.
cheers,
Étienne
The text was updated successfully, but these errors were encountered:
Hi Etienne, thanks for using CodeCarbon. It would mean a lot of maintenance to handle a different API for each country unless they all have the same standardized way of querying. On improvement I could imagine though would be to use this API to enrich a more detailed static file with evolution of mix across seasons or lets be crazy the hours of the day.
Another option would be to allow any API to provide electricity data but you would need to implement a "middle man" API to ensure standardisation so that code carbon could call it the same way it does the electricitymaps API
Thanks for the reply. I was indeed thinking of a middle man structure, where one could wrap different APIs into a unified call to code carbon. So I think I'll fork and explore a bit :)
Hello!
I have noticed in Denmark that the national electricity grid manager provides an API to track, among other things, the evolution of the energy mix in realtime: https://www.energidataservice.dk/tso-electricity/DeclarationGridmix
I was thinking of using this data source as a replacement for
global_energy_mix.json
, when computing CO2 emissions.Have you already considered a method for people to include different APIs of this kind as plugins? I noticed another related question regarding using ElectricityMap, but it would be interesting to incorporate data from freely accessible API than rely on commercial ones.
cheers,
Étienne
The text was updated successfully, but these errors were encountered: