ReferenceData: Difference between revisions
PeterHicks (talk | contribs) Add a page outlining the new reference data available |
PeterHicks (talk | contribs) m →Reference Data: Add reference to TIPLOC data in SCHEDULE files |
||
Line 6: | Line 6: | ||
A periodically-updated snapshot of data from CORPUS is available. This can be used to translate STANOX, TIPLOC, NLC, UIC and 3-alpha (CRS) codes to location descriptions. | A periodically-updated snapshot of data from CORPUS is available. This can be used to translate STANOX, TIPLOC, NLC, UIC and 3-alpha (CRS) codes to location descriptions. | ||
== TIPLOC data == | |||
The [[SCHEDULE]] feed contains TIPLOC, NLC and CRS code data, along with descriptions. A full SCHEDULE file will contain 'TI' (TIPLOC Insert) records for all locations, and update SCHEDULE files will contain any updates. | |||
Whilst this data is updated more frequently than the location reference data from CORPUS, the location reference data is more comprehensive. | |||
== Berth stepping data == | == Berth stepping data == | ||
A periodically-updated snapshot of data from SMART is available. This can be used in conjunction with the [[TD]] feed to translate train movements in to arrivals and departures from locations. | A periodically-updated snapshot of data from SMART is available. This can be used in conjunction with the [[TD]] feed to translate train movements in to arrivals and departures from locations. |
Revision as of 09:29, 22 January 2013
Reference Data
Three sets of reference data have been provided.
Location reference data
A periodically-updated snapshot of data from CORPUS is available. This can be used to translate STANOX, TIPLOC, NLC, UIC and 3-alpha (CRS) codes to location descriptions.
TIPLOC data
The SCHEDULE feed contains TIPLOC, NLC and CRS code data, along with descriptions. A full SCHEDULE file will contain 'TI' (TIPLOC Insert) records for all locations, and update SCHEDULE files will contain any updates.
Whilst this data is updated more frequently than the location reference data from CORPUS, the location reference data is more comprehensive.
Berth stepping data
A periodically-updated snapshot of data from SMART is available. This can be used in conjunction with the TD feed to translate train movements in to arrivals and departures from locations.