View source for ReleaseNotes

= Release 3.2.0 - January 2013 =

== Non-passenger train data ==

Anonymised freight train data is now included in the feeds.  This allows the analysis of train movements by non-passenger operators.

This will affect the following feeds:

* '''SCHEDULE''' - schedules for non-passenger operators are included
* '''VSTP''' - late notice schedules for non-passenger operators are included
* '''Train Movement''' - real-time movements for non-passenger operators
* '''TD''' - berth-level data for non-passenger operators

The SCHEDULE and VSTP feeds have the train reporting number (headcode) and train category removed.  Before the train commences its journey, an anonymous identifier, in the format CXXX (where C is the original train's class and XXX is an identifier which will increment from 00A to 99Z) will be allocated, and this will be reported through the Train Movement and TD feeds.

== Additional signalling data ==

The TD feed will contain three additional message types - SF, SG and SH - for train describers which support S-Class data.  These messages contain information on the status of signal aspects, routes set, point positions, track circuit occupation and other low-level data.

As a result of the changes to implement non-passenger train data, the TD feed will include Class 0, 3 and 5 trains that are operated by a passenger operator.

See the [TD] page for more information.

== Reference data ==

Additional reference data is being supplied:

* The SCHEDULE feed will include TIPLOC records from ITPS.  The 'full' data will contain a snapshot of all TIPLOC data, and the 'update' data will contain incremental updates.
* Data from CORPUS, with a snapshot of NLC, STANOX, TIPLOC, CRS and UIC code data is available through the web interface
* Data from SMART, with details of berth steps and the locations to which they apply, will be available through the web interface