Hi,
Have been getting complaints that predictions for Route 20 have not been available for approx 2 weeks.
Please advise.
Seems OK today so unless something has been fixed it’s not the kit on the buses.
I did see on London Vehicle Finder the last couple of nights that they did show three (I think) buses having operated on the route earlier in the day. That’s well short of the actual number of buses used but the implication is that those three vehicles should have had predictions in the system, I think.
I note that 20 has both MFHo and SMFHo schedules (that is, normal school holiday and Summer school holiday). I wonder if there is a mismatch between what has been assumed to be running and what actually is, though I don’t really know whether that would be enough to stop buses appearing - and why would three buses then appear?
Back to no predictions today. At least, nothing live. London Vehicle Finder shows buses used until 0648 and 0730 (twice). As those buses would have continued in service, their failure to appear is hard to understand, unless my theory in my previous post somehow turns out to be correct.
Out of interest, is this happening for the old http://data.tfl.gov.uk/tfl/syndication/feeds/bus-sequences.csv digest too or just the unified API?
We (LVF) use the Countdown feed, so it’s happening there too.
Simon
That’s interesting, that must mean that it’s an input-to-iBus problem, rather than an API-output issue.
Perhaps “CT Plus” might like to check their drivers are logging into i-Bus?
Brian
But some of them are, as journeys appear for some vehicles at the start of the day, then they stop. As I type, London Vehicle Finder shows no live predictions but is does show one vehicle used from 0530 to 0700, another from 0615 to 0950 and one from 0044 to 0045. I simply do not believe that the first bus operated no more journeys after 0700, which is why the only thing I can think of is that the wrong schedule is being used somewhere and once the two diverge predictions disappear (and perhaps return in the evening).
Michael
1 Like
As we’ve had data throughout the weekend again, I’d say this is definitely a Mon-Fri schedule issue.
This is what we’ve recorded so far today*:
| Veh | Reg | Date/Time | Route | Destination | |
|---|---|---|---|---|---|
| 2549 | E20HCT | 2021-08-11 05:20 | 20 | Walthamstow Central | |
| 2549 | E20HCT | 2021-08-11 06:00 | 20 | Debden | |
| 2542 | YX19ORT | 2021-08-11 06:15 | 20 | Walthamstow Central | |
| 2541 | YX19ORS | 2021-08-11 06:30 | 20 | Walthamstow Central | |
| 2541 | YX19ORS | 2021-08-11 07:04 | 20 | Debden | |
| 2542 | YX19ORT | 2021-08-11 07:14 | 20 | Debden | |
| 2549 | E20HCT | 2021-08-11 07:14 | 20 | Walthamstow Central | |
| 2541 | YX19ORS | 2021-08-11 08:09 | 20 | Walthamstow Central | |
| 2549 | E20HCT | 2021-08-11 08:21 | 20 | Debden | |
| 2541 | YX19ORS | 2021-08-11 09:19 | 20 | Debden | |
| 2549 | E20HCT | 2021-08-11 09:31 | 20 | Walthamstow Central | |
| 2541 | YX19ORS | 2021-08-11 10:20 | 20 | Walthamstow Central | |
| 2549 | E20HCT | 2021-08-11 10:41 | 20 | Debden | |
| 2549 | E20HCT | 2021-08-11 11:49 | 20 | Walthamstow Central | |
| 2549 | E20HCT | 2021-08-11 12:50 | 20 | Debden |
*Ignoring 2543 which appeared at 23:32 last night and did an 00:15 trip to Debden this morning…
Regards,
Simon
(Edited to say I’m impressed the table worked! 
)
Seems to be working today. What actually went wrong? While it would be nice to know, I ask in the hope that the issue is understood well enough to stop it recurring on the 20 or any other route.
1 Like
New schedules tend to be uploaded to iBus in the early hours of a Friday morning.
Simon
Bang on cue, predictions have (almost) dried up for the 137 starting from Sunday 15th.
Michael
This is all we got for the 137 on Sunday:
| Fleet | Reg | Departure | Line | Destination |
|---|---|---|---|---|
| LT970 | LTZ2170 | 2021-08-15 14:00 | 137 | Marble Arch |
| LT965 | LTZ2165 | 2021-08-15 14:20 | 137 | Marble Arch |
| LT723 | LTZ1723 | 2021-08-15 14:40 | 137 | Marble Arch |
| LT970 | LTZ2170 | 2021-08-15 14:50 | 137 | Streatham Hill, Telford Avenue |
| LT962 | LTZ2162 | 2021-08-15 14:50 | 137 | Marble Arch |
| LT965 | LTZ2165 | 2021-08-15 15:20 | 137 | Streatham Hill, Telford Avenue |
| LT723 | LTZ1723 | 2021-08-15 15:30 | 137 | Streatham Hill, Telford Avenue |
| LT962 | LTZ2162 | 2021-08-15 15:40 | 137 | Streatham Hill, Telford Avenue |
| LT970 | LTZ2170 | 2021-08-15 16:19 | 137 | Marble Arch |
| LT965 | LTZ2165 | 2021-08-15 16:37 | 137 | Marble Arch |
| LT723 | LTZ1723 | 2021-08-15 16:53 | 137 | Marble Arch |
| LT970 | LTZ2170 | 2021-08-15 17:41 | 137 | Streatham Hill, Telford Avenue |
| LT723 | LTZ1723 | 2021-08-15 18:10 | 137 | Streatham Hill, Telford Avenue |
| LT723 | LTZ1723 | 2021-08-15 19:20 | 137 | Marble Arch |
And today, Monday:
| Fleet | Reg | Departure | Line | Destination |
|---|---|---|---|---|
| LT744 | LTZ1744 | 2021-08-16 05:00 | 137 | Marble Arch |
| LT723 | LTZ1723 | 2021-08-16 05:44 | 137 | Marble Arch |
| LT744 | LTZ1744 | 2021-08-16 05:49 | 137 | Streatham Hill, Telford Avenue |
| LT723 | LTZ1723 | 2021-08-16 06:01 | 137 | Streatham Hill, Telford Avenue |
| LT744 | LTZ1744 | 2021-08-16 06:36 | 137 | Marble Arch |
| LT723 | LTZ1723 | 2021-08-16 07:00 | 137 | Marble Arch |
| LT983 | LTZ2183 | 2021-08-16 07:30 | 137 | Marble Arch |
| LT744 | LTZ1744 | 2021-08-16 07:39 | 137 | Streatham Hill, Telford Avenue |
| LT723 | LTZ1723 | 2021-08-16 08:00 | 137 | Streatham Hill, Telford Avenue |
| LT983 | LTZ2183 | 2021-08-16 08:00 | 137 | Streatham Hill, Telford Avenue |
| LT744 | LTZ1744 | 2021-08-16 08:46 | 137 | Marble Arch |
| LT723 | LTZ1723 | 2021-08-16 09:05 | 137 | Marble Arch |
| LT983 | LTZ2183 | 2021-08-16 09:11 | 137 | Marble Arch |
| LT744 | LTZ1744 | 2021-08-16 10:02 | 137 | Streatham Hill, Telford Avenue |
| LT723 | LTZ1723 | 2021-08-16 10:18 | 137 | Streatham Hill, Telford Avenue |
| LT744 | LTZ1744 | 2021-08-16 11:15 | 137 | Marble Arch |
| LT723 | LTZ1723 | 2021-08-16 11:34 | 137 | Marble Arch |
| LT744 | LTZ1744 | 2021-08-16 12:26 | 137 | Streatham Hill, Telford Avenue |
| LT744 | LTZ1744 | 2021-08-16 13:51 | 137 | Marble Arch |
| LT744 | LTZ1744 | 2021-08-16 15:02 | 137 | Streatham Hill, Telford Avenue |
| LT744 | LTZ1744 | 2021-08-16 16:21 | 137 | Marble Arch |
| LT744 | LTZ1744 | 2021-08-16 17:35 | 137 | Streatham Hill, Telford Avenue |
| LT744 | LTZ1744 | 2021-08-16 19:05 | 137 | Marble Arch |
| LT982 | LTZ2182 | 2021-08-16 21:30 | 137 | Marble Arch |
Simon
N137 looks OK by the way
theres no predictions for N9 or unless due to changes happening today at Aldwych it could be part of schedule issue?
Same for 9. Other services normally serving Aldwych seem OK (I haven’t looked at them all) though clearly buses are being turned short (e g 15 at Ludgate Circus, 172 at Waterloo). I can only imagine that the 9 and N9 are doing something more ad hoc out of line with the normal schedule.
On the 137, I have read elsewhere that there was a partial garage reallocation last weekend. That would normally result in a new schedule but nothing has appeared in the WTTs or on Datastore (maybe it is transitory). Could this be the explanation?
Michael
1 Like
9 was working yesterday, operating between Hammersmith and Trafalgar Square.
I’m sure 9 and N9 are operating but (for example) only four buses are actually appearing in the feed for 9 this afternoon.
1 Like
9 is back in the feed today post-Aldwych. 137 (mostly) isn’t.
1 Like
Sadly there is no predictions for route 9 and also staying up late i saw there wasnt any arrivals for N9 and N65.
London Vehicle Finder shows 12 buses having operated on the route today, over and above the 3 for which predictions are available. No idea why they have disappeared, unless the schedule has been rendered Extinct by Rebellion. LVF also shows 4 buses having run overnight on N65 but none on N9.
1 Like