Search results

Jump to navigation Jump to search
  • Temporary Speed Restriction (TSR) messages are sent once a week, on a Friday at 0600, and contain a snapshot ...ave a durable subscription in place at this time, you will not receive the TSR messages.
    6 KB (711 words) - 10:35, 6 December 2023
  • ...ormation in CIF for both Daily and Weekly which can be access via S3. Live Data for trains in UK. Leeds, Rockshore. ...ormation in CIF for both Daily and Weekly which can be access via S3. Live Data for trains in UK. Leeds, Rockshore.
    387 bytes (66 words) - 07:39, 10 March 2015
  • [[Category: TSR Data]]
    190 bytes (31 words) - 14:09, 12 December 2018
  • |text = Network Rail Open Data Feeds}} |title = Data Feeds
    2 KB (273 words) - 15:51, 28 March 2021
  • ...igh-volume, and if you disconnect for even a minute, you can lose a lot of data * The [[TSR]] feed has a handful of messages on a Friday morning (when the Weekly Opera
    2 KB (389 words) - 18:35, 23 May 2013
  • |Berth-level data from the Train Describer system, showing raw data with train movements in more detail than the [[Train Movements]] feed. |[[TSR]]
    5 KB (801 words) - 13:35, 9 March 2024
  • |TSR speed restrictions for track work outside of the Timetable Planning Rules |Reactionary Delay to ‘P’ coded TSR
    25 KB (3,875 words) - 17:47, 7 February 2022
  • ...hedules, or if you want to receive data for non-passenger TOC trains. The data in these feeds is of a highly technical nature and you will require a fair ...ds|National Rail Enquiries feeds]]''' if you want industry-wide consistent data on passenger train movements which matches that shown in railway stations a
    8 KB (1,261 words) - 13:33, 9 March 2024
  • ...list of acronyms] was released by Network Rail on 10th August 2018 from a data set held in TOPS, hence all text is in upper-case. The data has not been updated for many years and may not reflect current practice -
    75 KB (11,188 words) - 19:08, 10 August 2018