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
Jeg har brugt app'en stort set dagligt i over et år nu, og er rigtig glad for den.... jeg har kigget forskellige steder - men aldrig ikke fundet nogen angivelse af, om I viser øst- eller vestdanmark eller et gennemsnit?
Det ville også være dejligt at kunne skifte mellem øst- og vestdanmark.
The values for DK1 and DK2 are the same, because both represent the total value of CO2 emissions in Denmark. Ongoing work will later give the correct individual values for the two price areas and the current value (for DK1 and DK2) will be shown under an extra column named DK.
That is, the data would represent some sort of (presumably weighted) average. And indeed, that note used to be true, but looking at it right now, the values for DK1 (West Denmark) and DK2 (East Denmark) in those datasets are not the same, yet no column named "DK" exists. They must have changed that quite recently.
So that's good; this means we can let the user choose their own region and get more accurate data (e.g. by doing something like the screenshot below). I'll have that set up once time allows. Until then, what's actually shown is the data for DK2; that means that the actual numbers will be off, of course, but considering only decisions of the form "when should I turn on the dishwasher" goes, it's still useful for DK1.
Jeg har brugt app'en stort set dagligt i over et år nu, og er rigtig glad for den.... jeg har kigget forskellige steder - men aldrig ikke fundet nogen angivelse af, om I viser øst- eller vestdanmark eller et gennemsnit?
Det ville også være dejligt at kunne skifte mellem øst- og vestdanmark.
I henviser til https://www.energidataservice.dk, men de har rigtig mange kilder, så lidt mere specifikt, er det mon https://www.energidataservice.dk/tso-electricity/CO2Emis I bruger?
Tak for en god service :-)
The text was updated successfully, but these errors were encountered: