conorhaining / desiro Goto Github PK

Creation of new routes to facilitate some reference data

Ideas:

• CRS to TIPLOCs
• TIPLOC to CRS
• Station Data?

Detect and add 'via' locations to the station board

Examples:

• Glasgow -> Falkirk High -> Edinburgh
• Glasgow -> Cumbernauld -> Edinburgh
• Cathcart Circle

In cases where a schedule splits/joins another schedule, the API should only display the origin/destination where it is applicable. For example, if a service has already split, then it should not display the destination for the other service.

Currently when no arrival or departure movement message is received for a station, no information is displayed for an arrival/departure time if a movement is received later in the journey.

When an error occurs somewhere in the process chain, there should be a unified approach to responding with error details.

A number of stations, in particular larger stations, may have multiple TIPLOCs relating to their station which is used in ITPS. All these TIPLOCs should be found and then the query modified to include any number of them.

Reference: https://groups.google.com/d/msg/openraildata-talk/CA2hOQzdzr0/CafAAjp5BAAJ

Known Stations:

• London Victoria
• Clapham Junction
• London Bridge
• London Waterloo

Check that public_arrival and public_departure fields are populated for the relevant direction mode, if they aren't remove them.

📎 station/STG/departures/2019/04/01/1641

Creation of a AWS Codepipe line to test & deploy this software