Interconnector Register 04 February 2025
This data file contains the latest version of the Interconnector Register including all changes up to publication. This file will be updated twice weekly on Tuesdays and Fridays.
CKAN Data API
Access resource data via a web API with powerful query support.
Further information in the main CKAN Data API and DataStore documentation.
The Data API can be accessed via the following actions of the CKAN action API.
Query example (first 5 results) |
---|
https://api.neso.energy/api/3/action/datastore_search?resource_id=64f7908f-f787-4977-93e1-5342a5f1357f&limit=5
|
Query example (via SQL statement) |
https://api.neso.energy/api/3/action/datastore_search_sql?sql=SELECT * from "64f7908f-f787-4977-93e1-5342a5f1357f" LIMIT 5
|
A simple ajax (JSONP) request to the data API using jQuery.
var data = { resource_id: '64f7908f-f787-4977-93e1-5342a5f1357f', // the resource id limit: 5 // get 5 results }; $.ajax({ url: 'https://api.neso.energy/api/3/action/datastore_search', data: data, dataType: 'jsonp', success: function(data) { alert('Total results found: ' + data.result.total) } });
A simple ajax (JSONP) request to the data API using jQuery.
import urllib2 url = 'https://api.neso.energy/api/3/action/datastore_search?resource_id=64f7908f-f787-4977-93e1-5342a5f1357f&limit=5' fileobj = urllib2.urlopen(url) print fileobj.read()
Data Explorer
Data Explorer
Table Information
Project Name
Title | Project Name |
---|---|
Type | string |
Description | Name of Generation Project |
Comment | n/a |
Example | Aminth |
Unit | n/a |
Customer Name
Title | Customer Name |
---|---|
Type | string |
Description | Name of Generator |
Comment | n/a |
Example | AMINTH ENERGY LTD |
Unit | n/a |
Connection Site
Title | Connection Site |
---|---|
Type | string |
Description | Name of Generation Connection Site |
Comment | n/a |
Example | Mablethorpe 400kV |
Unit | n/a |
Stage
Title | Stage |
---|---|
Type | number |
Description | Stage refers to Staged TEC – how much TEC the Customer will connect and when. |
Comment | The customer may choose to bring on capacity in chunks to align with their build. /commissioning program. Staged contracts are also used when a customer may only be able to bring on a proportion of their total capacity at a particular point in time ahead of further reinforcement works being carried out, completion of which would allow the remaining TEC onto the system. Field is only completed if the project is staged otherwise it will be empty |
Example | 1 |
Unit | n/a |
MW Import - Current
Title | MW Import - Current |
---|---|
Type | number |
Description | Amount of import capacity currently connected to the National Grid |
Comment | Field will state 0MW until the project is built and connected |
Example | 1200 |
Unit | MW |
MW Export - Current
Title | MW Export - Current |
---|---|
Type | number |
Description | Amount of export capacity currently connected to the National Grid |
Comment | Field will state 0MW until the project is built and connected |
Example | 1200 |
Unit | MW |
MW Import - Increase / Decrease
Title | MW Import - Increase / Decrease |
---|---|
Type | number |
Description | Amount of import capacity contracted to connect or be removed at a future date |
Comment | Field will state 0MW unless the TEC is due to increase or decrease |
Example | 1400 |
Unit | MW |
MW Export - Increase / Decrease
Title | MW Export - Increase / Decrease |
---|---|
Type | number |
Description | Amount of export capacity contracted to connect or be removed at a future date |
Comment | Field will state 0MW unless the TEC is due to increase or decrease |
Example | 1400 |
Unit | MW |
MW Import - Total
Title | MW Import - Total |
---|---|
Type | number |
Description | Total amount of import capacity contracted across all Stages |
Comment | n/a |
Example | 500 |
Unit | MW |
MW Export - Total
Title | MW Export - Total |
---|---|
Type | number |
Description | Total amount of export capacity contracted across all Stages |
Comment | n/a |
Example | 500 |
Unit | MW |
MW Effective From
Title | MW Effective From |
---|---|
Type | date |
Description | Date on which Connection is contracted to be effective from |
Comment | Field will only include dates for future connections or increase/decreases to TEC, otherwise this field will be empty |
Example | 2028-10-31 |
Unit | yyyy-mm-dd |
Project Status
Title | Project Status |
---|---|
Type | string |
Description | Indicates what stage the Project is at in it's build cycle |
Comment | The Status classifications are very much based on information we have either ascertained from the customer or from another source, i.e. government website. It’s important to note that we hold no authority on the Status classifications on Registers and are produced on an “as far as we are aware” basis. To this end we deem the classifications to mean: Scoping – we are not aware that a planning application has been made Awaiting Consents – we are aware (or the customer has told us) a planning application has been made Consents Approved – we are aware (or the customer has told us) the planning application has been approved |
Example | Scoping |
Unit | n/a |
HOST TO
Title | HOST TO |
---|---|
Type | string |
Description | Indicates which TO is responsible for the connection |
Comment | NGET, SHET, SPT or OFTO |
Example | NGET |
Unit | n/a |
Project Number
Title | Project No |
---|---|
Type | string |
Description | Unique Project Identifier |
Comment | If there is more than one Stage the Project number will be followed by a dash and the relevant stage number. |
Example | PRO-001292-1 |
Unit | n/a |