Add support for finding train by headcode (Including PIS Code) #17

New Issue

fred.boniface · 2023-06-01T20:35:38+01:00

fred.boniface commented

2023-06-01 20:35:38 +01:00

The initial code required in backend and db-manager have been written.

Searching for a train by headcode required locally hosting a copy of Network Rail's SCHEDULE data. Currently VSTP trains will not be supported however LTP and STP services should be available.

The method of storing PIS codes has changed, each PIS code now contains an array of CRS codes and an array of TIPLOC codes which are updated automatically each time the PIS source file is changed.

The timetable data is also handled by db-manager - it's method of operation (CronJob) is not compatible with the messaging system used for VSTP updates. The code in db-managers 'timetable' module should automatically update the timetable as required but it needs to be monitored for a few daily updates to ensure that it is functioning properly.

The web-frontend will need a new page to display the train data as well as methods of calling it. The current idea is to have a HEADCODE box on the PIS Code lookup as well as a HEADCODE box on a 'Find Train' page. Both of these will direct to the same place to view the timetable data alongside the trains PIS code.

Where multiple trains share a headcode they will both be shown with the earliest at the top. Train data will be filtered by day so only valid services on the day of a search will be displayed.

The initial code required in backend and db-manager have been written. Searching for a train by headcode required locally hosting a copy of Network Rail's SCHEDULE data. Currently VSTP trains will not be supported however LTP and STP services should be available. The method of storing PIS codes has changed, each PIS code now contains an array of CRS codes and an array of TIPLOC codes which are updated automatically each time the PIS source file is changed. The timetable data is also handled by db-manager - it's method of operation (CronJob) is not compatible with the messaging system used for VSTP updates. The code in db-managers 'timetable' module should automatically update the timetable as required but it needs to be monitored for a few daily updates to ensure that it is functioning properly. The web-frontend will need a new page to display the train data as well as methods of calling it. The current idea is to have a HEADCODE box on the PIS Code lookup as well as a HEADCODE box on a 'Find Train' page. Both of these will direct to the same place to view the timetable data alongside the trains PIS code. Where multiple trains share a headcode they will both be shown with the earliest at the top. Train data will be filtered by day so only valid services on the day of a search will be displayed.

fred.boniface added the

labels 2023-06-01 20:35:38 +01:00

fred.boniface commented

2023-06-24 23:56:56 +01:00

Done

fred.boniface closed this issue

2023-06-24 23:56:57 +01:00

Sign in to join this conversation.