So, result of update dated 29/2 2024:
Line restored: 226
Line deleted: 159
309/outbound: most stops missing?
We should have a fix in for 159 today. We’re still working on the 309 as the fix didn’t seem to take!
Many thanks,
James
@jamesevans Just my curiosity but does anyone at TfL know why apparently random errors come and go with such frequency?
I initiated use of Line/Route/Sequence because I thought the API might be a more reliable way to maintain an up-to-date bus route/sequence database than the XML timetables but it simply seems to have different issues.
To be honest, there can be multiple reasons. There can be human error either with the operators or within TfL when processing the timetables. We try to catch these at various steps using quality control, but the occasional issues pop through. We’re writing some more automated testing of the source data before it’s imported. It will be very difficult to eradicate it completely in the current set-up though.
Many thanks,
James
Thanks @jamesevans . I’m currently downloading the update dated 4/3/24 - looks as if the timeout problem is back. I’ll let you know the full results (much!) later
thanks - we’ve noticed as well. we’re looking at it…
We think we’ve stabilised the system now. It appears there was an issue with our memory recycling.
Can you please let us know how things go.
Many thanks,
James
Not looking any better from this end, churning its way through the 2nd pass of /Line/Route/Sequence with plenty of timeouts
Finally completed at 18:32 after 7 passes. I abandoned /Line/Timetable as pointless until this is sorted
Oh, and:
Result of update dated 4/3/2024:
Line restored: 159
309/outbound: most stops missing?
Result of intermediate update on 7/3/2024:
309/|outbound: mot stops missing
K4: Line/Route/Sequence returning 404 (not found) in both directions
Thanks @nickp - we have got a fix going to be released for 309 today. We’re building another release to restore the K4, although I don’t think we’ll be able to release that today.
And so,
Result of update dated 7/3/2024:
Lines restored: 309, K1, K2, K3, N65
Line deleted: K4
Lines duplicated: N199, P12
Piccadilly/outbound: wrong stop at Caledonian Road, should be 940GZLUCAR, not 940GZZLUCAR2
Also, looks like the timeout problem has been sorted, thanks @jamesevans
Result of intermediate update on 10/3/2024:
Line deleted: K4
Lines duplicated: N199, P12
Circle reduced to Hammersmith to Edgware Road (one direction) only
Piccadilly/outbound: wrong stop at Caledonian Road, should be 940GZLUCAR, not 940GZZLUCAR2
Result of intermediate update on 11/3/2024:
Line deleted: K4
Lines duplicated: N199, P12
Circle has outbound (clockwise) only
Piccadilly/outbound: wrong stop at Caledonian Road, should be 940GZLUCAR, not 940GZZLUCAR2
Result of intermediate update on 12/3/2024:
Line restored: Circle
Line deleted: K4
Lines duplicated: N199, P12
Piccadilly/outbound: wrong stop at Caledonian Road, should be 940GZLUCAR, not 940GZZLUCAR2
I also note that the Victoria line data has expired, as of 10/3, but not been replaced
Hi @nickp - we’ve identified fixes for K4 and Piccadilly/Caledonian Road issues. Hopefully we can get this in within the next day or 2.
In terms of expiry of Victoria line - can you please let me know where you see this?
Many thanks,
James
Hi @jamesevans
This was in /Line/Mode/{modes}/Route , line victoria now shows valid 11/3/24-23/12/24, but was showing 2/3/24-10/3/24 this morning (and yesterday)
hi @nickp
There was a change of timetable on those dates. The cache on your endpoint should only be 30 minutes though. Did you do the run just after midnight?
Many thanks,
James
Hi @jamesevans
The run was at 08:13 on 12/3 and showed both victoria & circle as expired since 10/03/2024 00:00:00.
I have pointed out before that your routes are flagged as expired 24 hours before you mean them to be, due to the 00:00:00 in the timestamp.
Log extract below:
Checking for changes 12/03/2024 08:13:01
Route circle expired 09/03/2024 00:00:00 > 10/03/2024 00:00:00
Route great-western-railway amended
Route victoria expired 02/03/2024 00:00:00 > 10/03/2024 00:00:00
Check complete 12/03/2024 08:13:06
Pass 1 starting 12/03/2024 08:13:06
victoria/inbound: ##R Timeout error: The operation has timed out
1 retryable errors in pass
Pass 2 starting 12/03/2024 08:13:20
Load complete after 2 passes 12/03/2024 08:13:23