James,
I think you need to define “full timetable system”. My definition is a system that describes the railroad and the scheduled trains indicating the times those trains will be at each location. The output is the employee timetable. This is used to implement “timetable and train order” operations. It can also feed a train management system which is responsible for day to day train activity.
My idea is based on a timetable system that I developed in the early 90s. The current version is a web based application. That system requires supplying all of the layout data, such as distance between locations, along with planned trains with their speeds, stops, etc.
Dave Sand
toggle quoted message
Show quoted text
On Aug 21, 2018, at 5:16 PM, jamespetts via Groups.Io <jamespetts@...> wrote:
I suspect that Andy is probably right (if I understand him correctly) and that the best implementation of a full timetable system would be perhaps a little more from the ground up than the lighter implementation suggested by David - but it is interesting that this topic is being discussed at all.
As Andy noted, one would need to start by understanding what users might actually want to do, and then consider what abstraction layers are necessary to generalise these functions into a workable set of algorithms in a way that interfaces well with the existing systems and data structures.
