Latest revision as of 13:19, 8 June 2024

Tiploc records are contained within the SCHEDULE data feed, and provide information about the possible timing point locations in train schedules. For further details, see the TIPLOC page.

Record Layout

Tiploc records are encoded as a JSON hash with a key of "TiplocV1" and a value containing the location data, in the following layout:

TiplocV1:
 transaction_type
 tiploc_code
 nalco
 stanox
 crs_code
 description
 tps_description

Example JSON record

 {
   "TiplocV1": {
     "transaction_type": "Create",
     "tiploc_code": "BURGESH",
     "nalco": "548300",
     "stanox": "87971",
     "crs_code": "BUG",
     "description": "BURGESS HILL",
     "tps_description": "BURGESS HILL"
   }
 }

Tiploc Record Fields

Field	Description
transaction_type	create, update or delete. A full snapshot file will only contain create records. Daily updates may contain either.
tiploc_code	TIPLOC of the location
nalco	NLC (National Location Code)
stanox	STANOX (Station Number)
crs_code	CRS (Computer Reservation System) code. Now 3-Alpha Code.
description	The short name of the location. Not populated for every location.
tps_description	The name of the location

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)

@@ Line 17: / Line 17: @@
    {
-     "JsonAssociationV1": {
+     "TiplocV1": {
        "transaction_type": "Create",
-       "main_train_uid": "C30123",
+       "tiploc_code": "BURGESH",
-       "assoc_train_uid": "C42949",
+       "nalco": "548300",
-       "assoc_start_date": "2024-06-03T00:00:00Z",
+       "stanox": "87971",
-      "assoc_end_date": "2024-06-21T00:00:00Z",
+       "crs_code": "BUG",
-      "assoc_days": "1111100",
+       "description": "BURGESS HILL",
-      "category": "NP",
+       "tps_description": "BURGESS HILL"
-      "date_indicator": "S",
-      "location": "YORK",
-       "base_location_suffix": null,
-      "assoc_location_suffix": null,
-       "diagram_type": "T",
-       "CIF_stp_indicator": "P"
      }
    }