Reference Data: Difference between revisions
BarryCarlyon (talk | contribs) |
Added other reference data sources to maintain a comprehensive list on one page |
||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:Reference Data}} | {{DISPLAYTITLE:Reference Data}} | ||
Two sets of reference data are | Two sets of reference data are available from Network Rail. The ''All Reference Data'' topic must be selected and subscribed to in the ''My Feeds'' tab of the data feeds site to be able to access the reference data. See the [[About_the_feeds|about the feeds]] page for more details. | ||
Other useful reference sources are also listed. | |||
= CORPUS: Location Reference Data = | |||
This is provided from the CORPUS system (''Codes for Operations, Retail & Planning – a Unified Solution''). The data is a periodically-updated snapshot of the CORPUS database. This can be used to translate STANOX, TIPLOC, NLC, UIC and 3-alpha (CRS) codes to location descriptions. | This is provided from the CORPUS system (''Codes for Operations, Retail & Planning – a Unified Solution''). The data is a periodically-updated snapshot of the CORPUS database. This can be used to translate STANOX, TIPLOC, NLC, UIC and 3-alpha (CRS) codes to location descriptions. | ||
== Downloading CORPUS Data == | |||
To download the data, visit http://datafeeds.networkrail.co.uk/ntrod/SupportingFileAuthenticate?type=CORPUS | To download the data, visit http://datafeeds.networkrail.co.uk/ntrod/SupportingFileAuthenticate?type=CORPUS | ||
== CORPUS Data Format == | |||
CORPUS data is supplied as a plain text file containing a JSON representation of the data. Entries comprise the following fields (not all fields may contain data): | CORPUS data is supplied as a plain text file containing a JSON representation of the data. Entries comprise the following fields (not all fields may contain data): | ||
| Line 42: | Line 44: | ||
|} | |} | ||
= SMART: Berth Stepping Data = | |||
The SMART database contains details of [[TD|train describer berths]] and allows movements into berths to be translated into arrivals and departures from locations. The data feed contains a periodically-updated snapshot of the SMART database. | The SMART database contains details of [[TD|train describer berths]] and allows movements into berths to be translated into arrivals and departures from locations. The data feed contains a periodically-updated snapshot of the SMART database. | ||
== Downloading SMART Data == | |||
To download the data, visit http://datafeeds.networkrail.co.uk/ntrod/SupportingFileAuthenticate?type=SMART | To download the data, visit http://datafeeds.networkrail.co.uk/ntrod/SupportingFileAuthenticate?type=SMART | ||
== SMART Data Format == | |||
SMART data is supplied as a plain text file containing a JSON representation of the data. Entries comprise the following fields (not all fields may contain data): | SMART data is supplied as a plain text file containing a JSON representation of the data. Entries comprise the following fields (not all fields may contain data): | ||
| Line 98: | Line 100: | ||
|- | |- | ||
|} | |} | ||
= Other Sources = | |||
* [http://deaves47.zxq.net/rail_index.htm Phil Deaves] has compiled a reference site listing location codes (CRS, STANOX and TIPLOC) as well as a comprehensive listing of other railway codes | |||
* [http://trains.barrycarlyon.co.uk/data/locations/ http://trains.barrycarlyon.co.uk/data/locations/] provides a searchable list of locations with their CRS, STANOX and TIPLOC codes and offers a downloadable SQL dump of the data | |||
* [http://data.gov.uk/dataset/naptan NaPTAN] (National Public Transport Access Nodes) is provided by the Department for Transport and is the single government source for all public transport stops/stations in the UK, also including bus stops, ferry terminals, airports, metro stations, and heritage railways, as well as associated metadata, including the location of entrances to stations, and platform locations in some circumstances. Contains ATCO, CRS and TIPLOC codes and latitude/longitudes. | |||
* Peter Hicks at [http://www.opentraintimes.com/ OpenTrainTimes] has written a [http://stash.poggs.com/reference_data_relationships.pdf a useful guide to the relationships between different datasets] which gives a good overview of the way that different sets of data interact | |||
Revision as of 07:56, 17 May 2013
Two sets of reference data are available from Network Rail. The All Reference Data topic must be selected and subscribed to in the My Feeds tab of the data feeds site to be able to access the reference data. See the about the feeds page for more details.
Other useful reference sources are also listed.
CORPUS: Location Reference Data
This is provided from the CORPUS system (Codes for Operations, Retail & Planning – a Unified Solution). The data is a periodically-updated snapshot of the CORPUS database. This can be used to translate STANOX, TIPLOC, NLC, UIC and 3-alpha (CRS) codes to location descriptions.
Downloading CORPUS Data
To download the data, visit http://datafeeds.networkrail.co.uk/ntrod/SupportingFileAuthenticate?type=CORPUS
CORPUS Data Format
CORPUS data is supplied as a plain text file containing a JSON representation of the data. Entries comprise the following fields (not all fields may contain data):
| Field | Description |
|---|---|
| STANOX | STANOX code |
| UIC | UIC code |
| 3ALPHA | 3-letter location code |
| TIPLOC | TIPLOC code |
| NLC | NLC code |
| NLCDESC | Description of the NLC |
| NLCDESC16 | NLC description (16-character version) |
SMART: Berth Stepping Data
The SMART database contains details of train describer berths and allows movements into berths to be translated into arrivals and departures from locations. The data feed contains a periodically-updated snapshot of the SMART database.
Downloading SMART Data
To download the data, visit http://datafeeds.networkrail.co.uk/ntrod/SupportingFileAuthenticate?type=SMART
SMART Data Format
SMART data is supplied as a plain text file containing a JSON representation of the data. Entries comprise the following fields (not all fields may contain data):
| Field | Description |
|---|---|
| TD | Train describer area |
| FROMBERTH | TD berth that movement is from |
| TOBERTH | TD berth that movement is to |
| FROMLINE | Line which the movement is from |
| TOLINE | Line which the movement is to |
| BERTHOFFSET | Berth offset |
| PLATFORM | Platform |
| EVENT | One of A, B, C, D |
| ROUTE | |
| STANOX | STANOX code for location |
| STANME | Abbreviated description of location |
| STEPTYPE | One of B, F, C, D, I, T, E |
| COMMENT |
Other Sources
- Phil Deaves has compiled a reference site listing location codes (CRS, STANOX and TIPLOC) as well as a comprehensive listing of other railway codes
- http://trains.barrycarlyon.co.uk/data/locations/ provides a searchable list of locations with their CRS, STANOX and TIPLOC codes and offers a downloadable SQL dump of the data
- NaPTAN (National Public Transport Access Nodes) is provided by the Department for Transport and is the single government source for all public transport stops/stations in the UK, also including bus stops, ferry terminals, airports, metro stations, and heritage railways, as well as associated metadata, including the location of entrances to stations, and platform locations in some circumstances. Contains ATCO, CRS and TIPLOC codes and latitude/longitudes.
- Peter Hicks at OpenTrainTimes has written a a useful guide to the relationships between different datasets which gives a good overview of the way that different sets of data interact