Data Feeds: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
As published by ITPS, the CIF contains limited train association data (AA records) however, prior to publication to PPTE for consumption, the CIF is parsed by a service known as POINTA. | As published by ITPS, the CIF contains limited train association data (AA records) however, prior to publication to PPTE for consumption, the CIF is parsed by a service known as POINTA. | ||
{{POINTA is a service which infers associations and enriches the CIF file, prior to publication. <i>Platform Occupancy INference of Train Associations</i> POINTA is considered to be an enhancement on the association parsing and inference undertaken by WACI (or similar) components common at many locations.}} | {{Quote|POINTA is a service which infers associations and enriches the CIF file, prior to publication. <i>Platform Occupancy INference of Train Associations</i> POINTA is considered to be an enhancement on the association parsing and inference undertaken by WACI (or similar) components common at many locations.}} | ||
Revision as of 12:00, 3 July 2020
This section describes the numerous data feeds that acumen consumes.
POINTA CIF
A train service database (TSDB) is maintained within acumen; the TSDB is created from a full extract CIF file at initialisation, and kept up to date by consumption of an incremental update which takes place each morning at 01:00 Hrs.
Both the full CIF and incremental update CIF files are obtained via SFTP directly from Network Rail PPTE (Pre-production Test Environment).
As published by ITPS, the CIF contains limited train association data (AA records) however, prior to publication to PPTE for consumption, the CIF is parsed by a service known as POINTA. Template:Quote