I have been entertained by the 410 this week. Due to emergency water works, there has been a diversion in place for much of this week. The stops themselves have been hooded and marked closed since Monday, but from past and present experience, that really is only an indication that something might be, might soon be, or might recently have been, going on. It certainly doesn’t mean the stops are currently closed. In reality the bus returned to route until well after seven o’clock on Tuesday morning and then was only diverted one way for the day. It now seems to have happily settled down to being diverted both ways.
Unfortunately the API has not even come close to communicating this on occasions. Sometimes the status has been updated to acknowledge the diversion. It was correct on Tuesday and belatedly caught up (with a minor error) on Wednesday, but has been reset to normal service even though the buses are very much on diversion. There have been times when the stops have been marked as closed. Looking at Matthew Somerville’s fun Live Bus Map, there was one point when all the bus stops on the diverted section were not displayed but I don’t know if that was just the stops being marked closed, or a more drastic change. But anyway for the last two days there has been arrivals data for all the stops that are not being served, with or without a status update.
The bottom line is that there is no useful way of reliably knowing what is happening with this route without actually walking to one of the two diversion points and hanging around for fifteen minutes or so to see which way the buses go.
Anyway, coming to the point … Is this just a symptom of a disconnect between what is happening operationally, and the information in the API? Is the accuracy of the API data entirely dependent on someone manually updating it in an accurate and timely fashion?