GSP - Gnode - Direct Connect - Region Lookup 20181031
A Comma-Separated-Variable (CSV) file containing the locations of each of the GSPs / Gnodes / Direct Connects and a lookup of which region represents them in the accompanying GIS files. This file also includes a lookup between GSP / Gnode and DNO License Area (a.k.a PES region a.k.a GSP Group region).
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=bbe2cc72-a6c6-46e6-8f4e-48b879467368&limit=5
|
Query example (via SQL statement) |
https://api.neso.energy/api/3/action/datastore_search_sql?sql=SELECT * from "bbe2cc72-a6c6-46e6-8f4e-48b879467368" LIMIT 5
|
A simple ajax (JSONP) request to the data API using jQuery.
var data = { resource_id: 'bbe2cc72-a6c6-46e6-8f4e-48b879467368', // 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=bbe2cc72-a6c6-46e6-8f4e-48b879467368&limit=5' fileobj = urllib2.urlopen(url) print fileobj.read()
Data Explorer
Data Explorer
Table Information
ng_id
Title | ng_id |
---|---|
Type | integer |
Description | Unique ID used in region derivations |
Comment | Arbitrary, not widely used outside of this dataset. Not consistent between versions of this dataset. |
Example | 1 |
Unit | N/A |
ggd_id
Title | ggd_id |
---|---|
Type | integer |
Description | Unique ID representing a fundamental entity in the lookup between GSP, Gnode and DNO License Area |
Comment | Arbitrary, not widely used outside of this dataset. Not consistent between versions of this dataset. Facilitates a MANY:MANY relationship between GSP and Gnode |
Example | 1 |
Unit | N/A |
gnode_id
Title | gnode_id |
---|---|
Type | integer |
Description | Unique ID for each Gnode |
Comment | Arbitrary, not widely used outside of this dataset. Not consistent between versions of this dataset. |
Example | 1 |
Unit | N/A |
gnode_name
Title | gnode_name |
---|---|
Type | string |
Description | Unique Name for each Gnode |
Comment | Preferred name for the Gnode entity within National Grid ESO. |
Example | COWL |
Unit | N/A |
gnode_lat
Title | gnode_lat |
---|---|
Type | number |
Description | Latitude of the Gnode location |
Comment | Not always the same as the corresponding GSP location due to disparate datasets and occasionally complex Gnode definitions. |
Example | 51.71105 |
Unit | Decimal degrees in WGS 1984 Coordinate Reference System |
gnode_lon
Title | gnode_lon |
---|---|
Type | number |
Description | Longitude of the Gnode location |
Comment | Not always the same as the corresponding GSP location due to disparate datasets and occasionally complex Gnode definitions. |
Example | -1.18901 |
Unit | Decimal degrees in WGS 1984 Coordinate Reference System |
gsp_id
Title | gsp_id |
---|---|
Type | integer |
Description | Unique ID for each Grid Supply Point |
Comment | Arbitrary, not widely used outside of this dataset. Not consistent between versions of this dataset. |
Example | 1 |
Unit | N/A |
gsp_name
Title | gsp_name |
---|---|
Type | string |
Description | Unique Name for each Grid Supply Point |
Comment | Consistent with the naming convention used by Elexon in Settlement Data |
Example | COWL_1 |
Unit | N/A |
gsp_lat
Title | gsp_lat |
---|---|
Type | number |
Description | Latitude of the Grid Supply Point location |
Comment | Not always the same as the corresponding Gnode location due to disparate datasets and occasionally complex Gnode definitions. |
Example | 51.71105 |
Unit | Decimal degrees in WGS 1984 Coordinate Reference System |
gsp_lon
Title | gsp_lon |
---|---|
Type | number |
Description | Longitude of the Grid Supply Point location |
Comment | Not always the same as the corresponding Gnode location due to disparate datasets and occasionally complex Gnode definitions. |
Example | -1.18901 |
Unit | Decimal degrees in WGS 1984 Coordinate Reference System |
dc_id
Title | dc_id |
---|---|
Type | integer |
Description | Unique ID for each 'Direct Connect' |
Comment | Arbitrary, not widely used outside of this dataset. Not consistent between versions of this dataset. |
Example | 1 |
Unit |
dc_name
Title | dc_name |
---|---|
Type | string |
Description | Unique Name for each 'Direct Connect' |
Comment | Preferred name for the 'Direct Connect' entity within National Grid ESO. Direct Connects represent demand that is connected directly to the transmission network. They are included in this dataset because they may theoretically host embedded generation and/or may form part of a MANY:MANY relationship with a Gnode. |
Example | T_CASKD-1 |
Unit |
dc_lat
Title | dc_lat |
---|---|
Type | number |
Description | Latitude of the 'Direct Connect' |
Comment | |
Example | 53.3421 |
Unit | Decimal degrees in WGS 1984 Coordinate Reference System |
dc_lon
Title | dc_lon |
---|---|
Type | number |
Description | Longitude of the 'Direct Connect' |
Comment | |
Example | 2.7297 |
Unit | Decimal degrees in WGS 1984 Coordinate Reference System |
region_id
Title | region_id / RegionID |
---|---|
Type | integer |
Description | Unique ID for each geospatial boundary |
Comment | Arbitrary, not widely used outside of this dataset. Not consistent between versions of this dataset. |
Example | 1 |
Unit | N/A |
region_name
Title | region_name / RegionName |
---|---|
Type | string |
Description | Unique Name for each geospatial boundary |
Comment | Usually derived from GSP name but may differ for complex GSP definitions. |
Example | Cowley |
Unit | N/A |
has_pv
Title | has_pv |
---|---|
Type | boolean |
Description | Whether the entity is deemed to possibly host any embedded Solar Photovoltaic capacity based on best available evidence at the time the regions were derived. |
Comment | Uses human intelligence from stakeholders within National Grid ESO. |
Example | 1 |
Unit | N/A |
pes_id
Title | pes_id |
---|---|
Type | integer |
Description | Unique ID for each Public Electricity Supplier region a.k.a DNO License Area a.k.a GSP Group region |
Comment | Widely used integer ID for each PES region, including for example in the Meter Point Administration Number (MPAN) where it is known as 'Distributor ID'. There are 14 PES regions with IDs from 10 to 23. Note that the 'Distributor ID in an MPAN can also have a value greater than 23 which represents an Independent Distribution Network Operator (IDNO) - IDNOs are not represented in this dataset. |
Example | 20 |
Unit | N/A |
pes_name
Title | pes_name |
---|---|
Type | string |
Description | Character code used to identify each PES a.k.a DNO License Area a.k.a GSP Group |
Comment | Widely used across the electricity industry, including for example in settlment data published by Elexon. |
Example | _H |
Unit | N/A |