(16 Jan 2025, 1:34 pm)Storx wrote The problem is if you use timetable data then the data is flawed.

In an ideal world you'd need something like

Calculate the times using some form of live data between points in 30 minute periods.
Select how many resources you're willing to put on your route.
Let AI work how the best use of those resources to give the most runs with enough padding so they can recover from delays.

I'd assume it's how the First system works behind the scenes or similar to it.

I did find this, but its been about 5 years since I have touched python.

https://pypi.org/project/BODSDataExtractor/ 

And to answer the highlighted point, thats exactly what I want. A robust schedule with enough slack to avoid major unreliability.