Loading...

CO2 Emission Prognosis Data

Total number of rows: 661,800


Minutes5DK
2017-07-01 00:45Z DK2 82
2017-07-01 00:45Z DK1 82
2017-07-01 00:40Z DK2 91
2017-07-01 00:40Z DK1 91
2017-07-01 00:35Z DK2 91
2017-07-01 00:35Z DK1 91
2017-07-01 00:30Z DK2 90
2017-07-01 00:30Z DK1 90
2017-07-01 00:25Z DK2 89
2017-07-01 00:25Z DK1 89
2017-07-01 00:20Z DK2 88
2017-07-01 00:20Z DK1 88
2017-07-01 00:15Z DK2 89
2017-07-01 00:15Z DK1 89
2017-07-01 00:10Z DK2 87
2017-07-01 00:10Z DK1 87
2017-07-01 00:05Z DK2 80
2017-07-01 00:05Z DK1 80
2017-07-01 00:00Z DK2 75
2017-07-01 00:00Z DK1 75
2017-06-30 23:55Z DK2 75
2017-06-30 23:55Z DK1 75
2017-06-30 23:50Z DK2 74
2017-06-30 23:50Z DK1 74
2017-06-30 23:45Z DK2 69
2017-06-30 23:45Z DK1 69
2017-06-30 23:40Z DK2 69
2017-06-30 23:40Z DK1 69
2017-06-30 23:35Z DK2 69
2017-06-30 23:35Z DK1 69
2017-06-30 23:30Z DK2 69
2017-06-30 23:30Z DK1 69
2017-06-30 23:25Z DK2 69
2017-06-30 23:25Z DK1 69
2017-06-30 23:20Z DK2 69
2017-06-30 23:20Z DK1 69
2017-06-30 23:15Z DK2 69
2017-06-30 23:15Z DK1 69
2017-06-30 23:10Z DK2 69
2017-06-30 23:10Z DK1 69
2017-06-30 23:05Z DK2 69
2017-06-30 23:05Z DK1 69
2017-06-30 23:00Z DK2 69
2017-06-30 23:00Z DK1 69
2017-06-30 22:55Z DK2 69
2017-06-30 22:55Z DK1 69
2017-06-30 22:50Z DK2 69
2017-06-30 22:50Z DK1 69
2017-06-30 22:45Z DK2 69
2017-06-30 22:45Z DK1 69

Data Dictionary

Column Type Label Description
Minutes5UTC timestamptz
Minutes5DK timestamp
PriceArea text
CO2Emission int4

5 minutes UTC

Name 5 minutes UTC
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

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.

Example 2017-07-14T08:05:00Z
Unit
Field Minutes5UTC
Property Constraint
Type datetime
Size 20
Format Regex
Validation Rules

5 minutes UTC

Name 5 minutes UTC
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

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.

Example 2017-07-14T08:05:00Z
Unit
Field Minutes5UTC
Property Constraint
Type datetime
Size 20
Format Regex
Validation Rules

Price area

Name Price area
Description

DK1 is Jutland and Fyen and DK2 is Zealand and islands

Comment

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

Example DK1
Unit
Field PriceArea
Property Constraint
Type string
Size 3
Format Regex
Validation Rules DK1 or DK2

CO2 emission

Name CO2 emission
Description

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

Comment

-

Example 301
Unit g/kWh
Field CO2Emission
Property Constraint
Type integer
Size 6
Format Regex
Validation Rules