CO2 Emission Prognosis

The dataset is an estimated prognosis for at least the next 9 hours for the CO2 emission from the estimated electricity consumption in Denmark per kWh.

The forecast is based on the production schedules for each power plant, combined with the CO2 emission per kWh per power plant. The forecast is updated with the production schedules during the day.\nThe 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. \nFor further information please see the document (in Danish) “Deklarationer af EL”. \n\nPlease also note: \n-\tDepending on the time of the day an update of the prognosis may include estimates for more than 9 hours, but every update will at least have 9 hours into the future. \n-\tThe resolution of the data is 5 minutes but the up-date frequency is a bit slower, which is 15 minutes.\n-\tTo calculate the emission rate from CO2 the 125% method is used, which means that coproduced heat is \n produced by a given efficiency by 125%. \n


5 minutes UTC

Comment

Please note that the format shown in the example applies to data download as JSON, XML or fetched through the API and is in accordance with the ISO 8601 standard. The format is slightly different when it is shown on screen or downloaded manually as CSV or XLSX. This is mainly due to readability and consideration for Excel users.

In preview (in the GUI) all timestamps are shown as (display convention) YYYY-MM-DD hh:mmZ e.g. 2017-07-14 08:05Z. The Z will remind viewers that this is UTC.

In download (CSV and XLSX) the date time are exported as YYYY-MM-DD hh:mm e.g. 2017-07-14 08:05. That is without the \u201cT\u201d and the \u201cZ\u201d and the seconds. Excel will recognize it as date-time. The user must remember the convention about time zones.

In download (JSON and XML) the full format is used YYYY-MM-DDThh:mmZ e.g. 2017-07-14T08:05Z.

Description

A date and time (interval), shown in UTC time zone, where the values are valid. 00:00:00 o\u2019clock is the first 5 minutes of a given day, interval 00:00:00 - 00:04:59, and 00:05:00 covers the second 5 minutes period (interval) of the day and so forth.

Please note: The naming is based on the length of the interval of the finest grain of the resolution

Format
Property constraint
Title

5 minutes UTC

Validation rules
Size

20

Type

datetime

Example

2017-07-14T08:05:00Z

Unit
Name

Minutes5UTC

5 minutes DK

Comment

On one normal day there will be 24 * 12 = 288 intervals.

When daylight saving times shifts there will be either 276 or 300 intervals.

Please note that the format shown in the example applies to data download as JSON, XML or fetched through the API and is in accordance with the ISO 8601 standard. The format is slightly different when it is shown on screen or downloaded manually as CSV or XLSX. This is mainly due to readability and consideration for Excel users.

In preview (in the GUI) all timestamps are shown as (display convention) YYYY-MM-DD hh:mm e.g. 2017-07-14 08:00. Please note that is no time zone indicator, showning that this is local (Danish) time.

In download (CSV and XLSX) the date time are exported as YYYY-MM-DD hh:mm:ss e.g. 2017-07-14 08:00:00. That is without the \u201cT\u201d and the seconds. Excel will recognize it as date-time. The user must remember that this is local (Danish) time.

In download (JSON and XML) the format used is YYYY-MM-DDThh:mm:ss e.g. 2017-07-14T08:00:00.

Description

A date and time (interval), shown in Danish time zone, where the values are valid. 00:00:00 o\u2019clock is the first 5 minutes of a given day, interval 00:00:00 - 00:04:59, and 00:05:00 covers the second 5 minutes period (interval) of the day and so forth.

Title

5 minutes DK

Property constraint
Format
Name

Minutes5DK

Validation rules
Type

datetime

Example

2012-10-01T02:15:00

Unit
Size

19

Price area

Comment

DK1 and DK2 are the standard abbreviation for the two Danish price areas

Description

DK1 is Jutland and Fyen and DK2 is Zealand and islands

Format

DK1 | DK2

Property constraint
Title

Price area

Validation rules

DK1 or DK2

Size

3

Type

string

Example

DK1

Unit
Name

PriceArea

CO2 emission

Comment
Description

The estimated value for the emission in g/kWh for the relevant 5 minutes period.

Format

\d{4}

Property constraint
Title

CO2 emission

Validation rules
Size

6

Type

integer

Example

301

Unit

g/kWh

Name

CO2Emission