Identifying Locations: Difference between revisions

From Open Rail Data Wiki
m Update table style
Clarify source of E/N TIPLOC mappings and specify license to prevent confusion
 
(15 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Identifying Stations ==
Locations on the rail network can be identified by several different methods:


Stations/locations are identified by a few different items of data.
* '''3-Alpha Codes''' - A 3-character code used for stations. Previously referred to as CRS (Computer Reservation System) or NRS (National Reservation System) codes.
* '''NLC (National Location Code)''' -  A 6-digit code generally used for retail purposes, [[NLC|described further here]]
* '''TIPLOC (Timing Point Location)''' - Codes relating to points used in deriving train schedules
* '''STANOX (Station Number)''' - These codes can refer to non-station locations such as sidings and junctions.  STANOX codes are grouped by geographical area - the first two digits specify the area in which the location exists. See the [[STANOX_Areas | STANOX code areas]] page for details.
* '''ATCO Code''' - Used by multi-modal journey planners and timetables<ref>ATCO Codes are maintained in the [https://beta-naptan.dft.gov.uk/ National Public Transport Access Nodes (NaPTAN) dataset]. "ATCO" stands for the [https://www.atco.website/ Association of Transport Co-ordinating Officers]. Not to be confused with the Association of Train Operating Companies (ATOC), now known as the [https://www.raildeliverygroup.com/ Rail Delivery Group].</ref>


* CRS - Computer reservation system, also referred to as national reservation system NRS codes
A single location may have multiple codes representing it, and different sets of platforms in one location may have differing codes - see the [[#Multiple_Codes | multiple codes]] section below.
** The handy 3 Character Code
 
* NLC - National Location Codes
See the [[Reference_Data | reference data]] page for sources of these codes.
* TIPLOC - Timing Point Locations
 
* STANOX - Station Numbers
* [[File:TIPLOC_Eastings_and_Northings.xlsx.gz|TIPLOCs Mapped to Eastings and Northings]] (FOI response from Network Rail, licensed under [https://www.networkrail.co.uk/who-we-are/transparency-and-ethics/freedom-of-information-foi/ OGL3])
* ATCO code - Used by multi-modal journey planners and timetables


== Examples ==
== Examples ==
Line 15: Line 18:
|-
|-
! scope="col" | Station
! scope="col" | Station
! scope="col" | CRS
! scope="col" | 3Alpha
! scope="col" | NLC
! scope="col" | NLC
! scope="col" | TIPLOC
! scope="col" | TIPLOC
Line 32: Line 35:
|}
|}


== Multiple Codes for a Station ==
== Multiple Codes ==


Emil Vaughan asked, "There appear to be two CRS codes used for Highbury and Islington in the ATOC timetables: HHY and HII. The first is used for the Overground, and the second for the deep-level FGW services. Only one of the codes, HII, is in the NaPTAN RailReferences.csv file. I was wondering how common it is for a station to have multiple CRS codes? Thanks!"
Emil Vaughan asked, "There appear to be two CRS codes used for Highbury and Islington in the ATOC timetables: HHY and HII. The first is used for the Overground, and the second for the deep-level FGW services. Only one of the codes, HII, is in the NaPTAN RailReferences.csv file. I was wondering how common it is for a station to have multiple CRS codes? Thanks!"
Line 40: Line 43:
A lot of the time these different TIPLOCs will additionally have a CRS code assigned to them (as in the case of HII for the Highbury & Islington low level platforms), but as far as I can see these secondary CRS codes are never used for anything, at least not in any of the public ATOC and Network Rail data. Yes, they appear in various indexes and master lists, but not elsewhere.
A lot of the time these different TIPLOCs will additionally have a CRS code assigned to them (as in the case of HII for the Highbury & Islington low level platforms), but as far as I can see these secondary CRS codes are never used for anything, at least not in any of the public ATOC and Network Rail data. Yes, they appear in various indexes and master lists, but not elsewhere.


HHY is definitely the main CRS code for Highbury & Islington; you can check this in the ATOC master station names file (TTISxxx.MSN) downloadable from data.atoc.org.
HHY is definitely the main CRS code for Highbury & Islington; you can check this in the ATOC master station names file (TTISxxx.MSN) in the ATOC timetable feed, downloadable from data.atoc.org.
 
== Notes ==
<references />


== Data Source ==
{{Navtable-DataFeeds}}


* A Searchable List and MySQL Database Dump [http://trains.barrycarlyon.co.uk/data/locations/ Trains.BarryCarlyon.co.uk]
[[Category:3-Alpha Codes]]
* [http://deaves47.zxq.net/CRS/CRS0.htm Phil Deaves, fairly up to date list]
[[Category:NLC Codes]]
* [http://data.gov.uk/dataset/naptan NaPTAN] (National Public Transport Access Nodes) - the single government source for all public transport stops/stations in the UK - also includes bus stops, ferry terminals, airports, metro stations, heritage railways, and associated metadata, including the location of entrances to stations, and platform locations in some circumstances. Contains ATCO, CRS and TIPLOC codes and latitude/longitudes.
[[Category:TIPLOC Codes]]
[[Category:STANOX Codes]]
[[Category:ATOC Data]]
[[Category:Identifying Locations]]

Latest revision as of 16:44, 15 April 2024

Locations on the rail network can be identified by several different methods:

  • 3-Alpha Codes - A 3-character code used for stations. Previously referred to as CRS (Computer Reservation System) or NRS (National Reservation System) codes.
  • NLC (National Location Code) - A 6-digit code generally used for retail purposes, described further here
  • TIPLOC (Timing Point Location) - Codes relating to points used in deriving train schedules
  • STANOX (Station Number) - These codes can refer to non-station locations such as sidings and junctions. STANOX codes are grouped by geographical area - the first two digits specify the area in which the location exists. See the STANOX code areas page for details.
  • ATCO Code - Used by multi-modal journey planners and timetables[1]

A single location may have multiple codes representing it, and different sets of platforms in one location may have differing codes - see the multiple codes section below.

See the reference data page for sources of these codes.

Examples

Station 3Alpha NLC TIPLOC STANOX ATCO
Leeds LDS 848700 LEEDS 17132 9100LEEDS
Kings Cross KGX 612100 KNGX 54311 9100KNGX
Lincoln Central LCN 634000 LINCLNC 44038 9100LINCLNC
Glasgow Central High Level GLC 981300 GLGC 07257 9100GLGC
Gatwick Airport GTW 541600 GTWK 87911 9100GTWK

Multiple Codes

Emil Vaughan asked, "There appear to be two CRS codes used for Highbury and Islington in the ATOC timetables: HHY and HII. The first is used for the Overground, and the second for the deep-level FGW services. Only one of the codes, HII, is in the NaPTAN RailReferences.csv file. I was wondering how common it is for a station to have multiple CRS codes? Thanks!"

It is reasonably common for a station to have multiple TIPLOC codes, where it consists of multiple groups of platforms on completely different lines. London Bridge, Victoria, Clapham Junction, Reading, Liverpool South Parkway are all examples of this I can think of off the top of my head. These different TIPLOC codes are used in schedules.

A lot of the time these different TIPLOCs will additionally have a CRS code assigned to them (as in the case of HII for the Highbury & Islington low level platforms), but as far as I can see these secondary CRS codes are never used for anything, at least not in any of the public ATOC and Network Rail data. Yes, they appear in various indexes and master lists, but not elsewhere.

HHY is definitely the main CRS code for Highbury & Islington; you can check this in the ATOC master station names file (TTISxxx.MSN) in the ATOC timetable feed, downloadable from data.atoc.org.

Notes

  1. ATCO Codes are maintained in the National Public Transport Access Nodes (NaPTAN) dataset. "ATCO" stands for the Association of Transport Co-ordinating Officers. Not to be confused with the Association of Train Operating Companies (ATOC), now known as the Rail Delivery Group.


Network Rail Open Data Feeds
Data Feeds About the Feeds Account States Durable Subscriptions Example Code ( PHP / C# / Java / Ruby / Node.js) • Advanced UsesFAQ Release Notes
RTPPM RTPPM Feed
Train Movements Train Movements Feed Train Activation Train Cancellation Train Movement Train Reinstatement Change of Origin Change of Identity Change of Location TSPEED Field Planned Cancellations Cancellation Codes
TD TD Feed C-Class Messages S-Class Messages Train Describers TD Berths
VSTP VSTP Feed
TSR TSR Feed Route Codes
SCHEDULE SCHEDULE Feed TIPLOC Records Schedule and Location Records Association Records CIF Codes How Scheduling Works Allowances
Reference Data Reference Data Feed TOC Codes CIF Codes Delay Attribution Codes Identifying Locations (STANOX, TIPLOC, NLC and 3-Alpha Codes) STANOX Geographical Areas Train Planning data (BPLAN)