Closed nwootton closed 7 years ago
Issue is with Transport API. Support email notified:
"Thank you for your email. This is a good bug report. It looks like the aimed_departure_time is snapping to the first departure of the day here. We will be looking into what's causing this. There should be no differences between departure data when toggling the 'group' option."
Helpdesk - #3825
Hack put in code to remove departures with a delay of over 60 minutes. Side effect is that it will reduce the number of arrivals displayed.
UPDATE I've chased TransportAPI about this (1/Aug/2017):
"Unfortunately the main developers of these bus API features, are all tied up with a major project for one of our enterprise customers at the moment, but I imagine we'll be able to get onto this bug in the next couple of weeks."
Helpdesk - #3825
Report from user via forum:
"I use it for two bus routes (44 and 344) and what I noticed during the weekend is that very early buses (like 01:00 in the morning or so) got delayed. BUT they got delayed more and more according to the module which causes the timing to be off. Eventually the timer showed something like “1756 Minutes late”. These late runners did not disappear but would always stay on top of the list.
I understand that this might be a bug on TFL’s side but is there a way to have buses that are, lets say more than 60 minutes delayed, shown as cancelled or have them faded out? For routes that are running like every 5-10 minutes usually this might make sense I think."