Identifying Locations: Difference between revisions
No edit summary |
Leon Byford (talk | contribs) →Multiple Codes: Update reference to soon-to-be-shutdown data.atoc.org |
||
| (11 intermediate revisions by 6 users not shown) | |||
| Line 2: | Line 2: | ||
* '''3-Alpha Codes''' - A 3-character code used for stations. Previously referred to as CRS (Computer Reservation System) or NRS (National Reservation System) codes. | * '''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 | * '''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 | * '''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. | * '''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 | * '''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> | ||
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. | 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. | ||
| Line 11: | Line 11: | ||
See the [[Reference_Data | reference data]] page for sources of these codes. | See the [[Reference_Data | reference data]] page for sources of these codes. | ||
= Examples = | * [[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]) | ||
== Examples == | |||
{| class="wikitable" | {| class="wikitable" | ||
| Line 33: | Line 35: | ||
|} | |} | ||
= Multiple Codes = | == 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 41: | 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 | HHY is definitely the main CRS code for Highbury & Islington; you can check this in the master station names file (RJTTFxxx.MSN) in the Rail Delivery Group's [[DTD|Timetable Information Data Feed]]. | ||
== Notes == | |||
<references /> | |||
{{Navtable-DataFeeds}} | |||
[[Category:3-Alpha Codes]] | |||
[[Category:NLC Codes]] | |||
[[Category:TIPLOC Codes]] | |||
[[Category:STANOX Codes]] | [[Category:STANOX Codes]] | ||
[[Category:ATOC Data]] | |||
[[Category:Identifying Locations]] | |||
Latest revision as of 10:25, 16 December 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.
- File:TIPLOC Eastings and Northings.xlsx.gz (FOI response from Network Rail, licensed under OGL3)
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 master station names file (RJTTFxxx.MSN) in the Rail Delivery Group's Timetable Information Data Feed.
Notes
- ↑ 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 Uses • FAQ • 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) |