Bus line 307 is missing

Hi Team,

It seems like bus line 307 is missing from the API, I’m assuming this is not intentional and just thought I should inform you in case you didn’t already know.


Kind regards,

Very curious - it was there a couple of days ago in the update dated 21/6/2023 but isn’t now, even though the update date hasn’t changed. @jamesevans - are there updates happening without the datestamp being amended? If so, how are we supposed to know?

Hi All,

I’ve had a look at the data which had some information missed, I have corrected this now and this will be live from the next TxC upload, also please note the service change that had the issue has been pushed back a week so the corrected file will match this start date.

Matthew (cc @GerardButler )

hi @nickp

It was most likely a timetable rollover. Our API will switch to the next timetable/route on the day after expiry. In this case, there was an issue with the timetable that caused it not to load in the API.

Most bus timetable changes occur on a Saturday, so I would suggest checking for updates to routes on a weekend.


Thanks @jamesevans

Looking at /Line/Route as extracted on 23/6, i.e. with timestamps of 21/6, I can indeed see that the 307 has validTo dates of 23/6 for both directions.

Three thoughts arise from this:

Firstly, looking manually at /Line/Route extracted now (26/6), the 307 has disappeared, as expected, but I am not seeing any amended timestamps for other routes. To take route 26 as an example, which has a scheduled timetable change on the Saturday, the created and modified timestamps are still showing as 21/6 but the validity period has changed from 17/6-23/6 to 24/6-23/12. Surely this is a modification?

Secondly, if the data is due to expire within the week following the bulk update, should there be further routeSections for the latter half of the period (leaving aside the error that prevented the new 307 being loaded)?

Thirdly, I use lineId/originator/direction from this to generate /Line/Timetable calls, but neither those calls nor responses have any validity information. Is the timetable only good for the day that the request is made, good until the validTo date, or an agglomeration of all current and forward timetables?

I note that, in /Line/Route/Sequence, we get fairly frequent instances of duplicate stopPointSequences, normally reflecting changes to the route during the week. It would seem that the presentation of data is not consistent between the two calls

As a further issue, the bulk update last week was timestamped 21/6, actually published on 23/6 with a number of lines, including 307 and 26, due to expire on the same day, which makes the data pretty useless for forward planning.