Transmission Lines
Data on capacity, scheduled trade, actual exchange and congestion income.
The TSOs decide how much capacity is to be transferred, and the capacity for the coming day is published at Nord Pool Spot every day before 10:00.
Scheduled trade on the transmission lines is the flow of electricity from areas of surplus to areas of deficit resulting from the Nord Pool Spots price calculation. The physical exchange is the actual measured exchange of electricity. Negative values indicate export of electricity out of the area to the connected area, and positive values indicate import.
Congestion rent is calculated as the difference in spot prices between the two price areas multiplied by the estimated exchange between the two areas concerned. The international connections to Norway and Sweden are completely at the disposal of NordPool Spot and in return the TSOs receive the congestion rent. In NORDEL (Denmark, Norway, Sweden, Finland, Iceland) the congestion rent is distributed according to a scale agreed upon. With regard to the KONTEK interconnection the congestion rent is paid to Energinet.dk, Vattenfall Europe Transmission and Vattenfall AB (Vattenfall’s trading company in Sweden) according to a scale agreed upon.
The interconnection between Western Denmark and Germany is at the disposal of the market at annual, monthly and daily auctions at which payment for utilization of the interconnection - and thereby the congestion rent - is calculated on the basis of demand and supply. The congestion rent is equally divided between Energinet.dk and E.ON Netz.
Hour UTC
Description | A date and time (interval), shown in UTC time zone, where the values are valid. 00:00 o\u2019clock is the first hour of a given day interval 00:00 - 00:59 and 01:00 covers the second hour (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:00Z. 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:00. 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:00Z. |
Name | HourUTC |
Type | datetime |
Unit | |
Size | 17 |
Example | 2017-07-14T08:00Z |
Format | |
Property constraint | |
Validation rules | Always full hours, i.e. minutes are 00 |
Hour DK
Description | A date and time (interval), shown in Danish time zone, where the values are valid. 00:00 o\u2019clock is the first hour of a given day, interval 00:00 - 00:59, and 01:00 covers the second hour period (interval) of the day and so forth. |
---|---|
Comment | On one normal day there will be 24 intervals. When daylight saving times shifts there will be either 23 or 25 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 e.g. 2017-07-14 08: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 e.g. 2017-07-14T08:00. |
Name | HourDK |
Type | datetime |
Unit | |
Size | 17 |
Example | 2017-07-14T08:00 |
Format | |
Property constraint | |
Validation rules | Always full hours, i.e. minutes are 00 |
Price area
Description | Same as bidding zone. Denmark is divided in two price areas, or bidding zones, divided by the Great Belt. DK1 is west of the Great Belt and DK2 is east of the Great Belt. |
---|---|
Comment | If price area is \u201cDK\u201d, the data covers all Denmark. |
Name | PriceArea |
Type | string |
Unit | |
Size | 3 |
Example | DK1 |
Format | DK1 | DK2 |
Property constraint | |
Validation rules | DK1 or DK2 |
Connected area
Description | The destination area of the connection. |
---|---|
Comment | DK1 is the Jutland and Fyen and DK2 is Zealand and islands. DK1 is connected to Norway (Oslo), Sweden (SE3) and Germany (EPEX) DK2 to Sweden (SE4) and Germany (EPEX) |
Name | ConnectedArea |
Type | string |
Unit | text |
Size | 8 |
Example | DK1 |
Format | DK1 | DK2 | SE3 | SE4 | NO2 | DE |
Property constraint | |
Validation rules | One of the following values DK1, DK2. SE3, SE4, NO2, DE |
Import capacity
Description | Import capacity from connected area to the area. The TSOs decide how much import capacity is to be transferred, and the capacity for the coming day is published at Nord Pool Spot every day before 10:00. |
---|---|
Comment | |
Name | ImportCapacity |
Type | number |
Unit | MWh per hour |
Size | 9.1 |
Example | 184.3 |
Format | ([0-9]*[,])[0-9] |
Property constraint | |
Validation rules |
|
Export capacity
Description | Export capacity from area to the connected area. The TSOs decide how much export capacity is to be transferred, and the capacity for the coming day is published at Nord Pool Spot every day before 10:00. |
---|---|
Comment | |
Name | ExportCapacity |
Type | number |
Unit | MWh per hour |
Size | 9.1 |
Example | 184.3 |
Format | ([0-9]*[,])[0-9] |
Property constraint | |
Validation rules |
Scheduled exchange day ahead
Description | Scheduled exchange on the transmission lines is the flow of electricity from areas of surplus to areas of deficit resulting from the Nord Pool Spots price calculation |
---|---|
Comment | Positive values are import from connected area to the area. Negative values are eksport from area to connected area. |
Name | ScheduledExchangeDayAhead |
Type | number |
Unit | MWh per hour |
Size | 9.1 |
Example | 184.3 |
Format | ([0-9]*[,])[0-9] |
Property constraint | |
Validation rules |
Scheduled exchange intraday
Description | Scheduled exchange on the transmission lines is the flow of electricity from areas of surplus to areas of deficit resulting from the Nord Pool Spots price calculation |
---|---|
Comment | Positive values are import from connected area to the area. Negative values are eksport from area to connected area. |
Name | ScheduledExchangeIntraday |
Type | number |
Unit | MWh per hour |
Size | 9.1 |
Example | 184.3 |
Format | ([0-9]*[,])[0-9] |
Property constraint | |
Validation rules |
Physical exchange non-validated
Description | Scheduled exchange on the transmission lines is the flow of electricity from areas of surplus to areas of deficit resulting from the Nord Pool Spots price calculation |
---|---|
Comment | Positive values are import from connected area to the area. Negative values are eksport from area to connected area. |
Name | PhysicalExchangeNonvalidated |
Type | number |
Unit | MWh per hour |
Size | 9.1 |
Example | 184.3 |
Format | ([0-9]*[,])[0-9] |
Property constraint | |
Validation rules |
Physical exchange settlement
Description | Scheduled exchange on the transmission lines is the flow of electricity from areas of surplus to areas of deficit resulting from the Nord Pool Spots price calculation |
---|---|
Comment | Positive values are import from connected area to the area. Negative values are eksport from area to connected area. |
Name | PhysicalExchangeSettlement |
Type | number |
Unit | MWh per hour |
Size | 9.1 |
Example | 184.3 |
Format | ([0-9]*[,])[0-9] |
Property constraint | |
Validation rules |
Congestion income (DKK)
Description | 9.2 |
---|---|
Comment | ([0-9]*[,])[0-9][0-9] |
Name | CongestionIncomeDKK |
Type | number |
Unit | DKK per hour |
Size | 9.2 |
Example | Congestion income is calculated as the difference in spot prices between the two price areas multiplied by the estimated exchange between the two areas concerned. |
Format | Congestion income from connection between price areas. |
Property constraint | |
Validation rules |
Home price (DKK)
Description | Price in the home price area |
---|---|
Comment | |
Name | HomePriceDKK |
Type | number |
Unit | DKK per hour |
Size | 9.2 |
Example | 543,45 |
Format | ([0-9]*[,])[0-9][0-9] |
Property constraint | |
Validation rules |
Connected price (DKK)
Description | Price in the connected area |
---|---|
Comment | |
Name | ConnectedPriceDKK |
Type | number |
Unit | DKK per hour |
Size | 9.2 |
Example | 300.0 |
Format | ([0-9]*[,])[0-9][0-9] |
Property constraint | |
Validation rules |
Congestion income (EUR)
Description | Congestion income from connection between price areas. |
---|---|
Comment | Congestion income is calculated as the difference in spot prices between the two price areas multiplied by the estimated exchange between the two areas concerned. |
Name | CongestionIncomeEUR |
Type | number |
Unit | EUR per hour |
Size | 9.2 |
Example | 300.0 |
Format | ([0-9]*[,])[0-9][0-9] |
Property constraint | |
Validation rules |
Home price (EUR)
Description | Price in the home price area |
---|---|
Comment | |
Name | HomePriceEUR |
Type | number |
Unit | EUR per hour |
Size | 9.2 |
Example | 543,45 |
Format | ([0-9]*[,])[0-9][0-9] |
Property constraint | |
Validation rules |
Connected price (EUR)
Description | Price in the connected area |
---|---|
Comment | |
Name | ConnectedPriceEUR |
Type | number |
Unit | EUR per hour |
Size | 9.2 |
Example | 300.0 |
Format | ([0-9]*[,])[0-9][0-9] |
Property constraint | |
Validation rules |