Train Movements

From Open Rail Data Wiki
Revision as of 20:41, 22 July 2012 by PeterHicks (talk | contribs) (Created page with "== Overview == The train movements feed contains messages produced by [TRUST]. These messages are one of eight types, all in JSON format: * 0001 - [Train Activation] * 0002 - …")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Overview

The train movements feed contains messages produced by [TRUST]. These messages are one of eight types, all in JSON format:

  • 0001 - [Train Activation]
  • 0002 - [Train Cancellation]
  • 0003 - [Train Movement]
  • 0004 - [Unidentified Train]
  • 0005 - [Train Reinstatement]
  • 0006 - [Change of Origin]
  • 0007 - [Change of Identity]
  • 0008 - [Change of Location]

Lifecycle

Before any action can be taken on a train, the schedule must be activated. An [Activation] message will be received, which will link a schedule to a 10-character train identity. This identity is referenced in all other message types, and there is no need to calculate it manually.

A train may be cancelled (either entirely or from a particular calling point onwards) through a [Train Cancellation] message, or start from a location other than the originating location through a [Change of Origin] message. A train may be reinstated after cancellation through a [Train Reinstatement] message.

One point to note - the [Change of Identity] message type is rarely seen. This is used when a train running under one class (e.g. a Class 4 freight with a train identity starting 4---) must run under a different class for some reason - usually because it must run at a lower speed due to the type of load it is carrying.