That’s great news, James.
John - I am glad you raised this issue. I’ve reported cases of this type a number of times via the @TfLBusAlerts Twitter team and they have always been receptive to that information. It has then led to the stop being correctly marked as closed soon thereafter.
However in each case there have been official yellow hoods and drivers have also appeared aware (‘The Next Bus Stop Is Closed’ iBus announcement is usually played). Although that’s possibly because the drivers have been passed that ‘live’ info by colleagues on the route, is the local garage/depot/line controller maybe aware before the central team?
The more complex issue of this type - and one with a wider effect on passengers - comes when unscheduled diversions (due to things like RTAs or burst water mains) lead to a whole series of stops being closed.
Although in those cases the stops themselves are pretty much always flagged as closed, the problems are quite significant for those waiting at subsequent stops where the bus returns to line of route.
I trust everyone who uses the data to provide services is aware that if a bus is on diversion it ‘disappears’ from predictions, leading to the impression that it isn’t going to arrive. The first couple of stops may show services counting down to 4 or 5 minutes before disappearing, while buses arrive unannounced - and outside Turnham Green Station, for example, I have watched people walking away from stops and running back as the information changes in a seemingly (to passengers) random fashion.
I wonder if any possible solutions to this have been discussed, James? I had a couple of thoughts about how this could be treated, but ultimately the idea of hours/days of ‘wrong predictions’ (one could answer ‘meaningless’) when diversions significantly change the timings mean this rather spoils trustworthiness for affected passengers.