Welcome to mytube - independent(ish) stats on London Underground delays

Current tube status:
Bakerloo -	communications issues: since 00:00
Central -	communications issues: since 00:00
Circle -	communications issues: since 00:00
District -	communications issues: since 00:00
Eastlondon -	communications issues: since 00:00
Hammersmith_city -	communications issues: since 00:00
Jubilee -	communications issues: since 00:00
Metropolitan -	communications issues: since 00:00
Northern -	communications issues: since 00:00
Piccadilly -	communications issues: since 00:00
Victoria -	communications issues: since 00:00
Waterloo_city -	communications issues: since 00:00
horse's mouth? click here for tfl's info page

London Underground delays so far today:

Date:	012345678910111213141516171819202122232425262728293031	Month:	JuneJulyAugustSeptemberOctober

Graphs

Gantt: delays by time & date by line
Gantt: delays by date
Barchart: delays by line [alpha test]

Reports

Current Status
List of delays by line by month
List of delays by cause by month

Straight data dump

Notes, faqs & feedback

Thoughts? Comments?
Blog them...
About the author Hosting by C360

Notes & FAQs:

How does mytube work?

Mytube visits Transport For London's website frequently to get the latest tube status. The information is categorised by Line, Issue and Location and stored in a database so that you can see what delays occur, where and how often. Importantly, for TFL - the term stats are collected by a timed process which will collects a fixed number of times per hour - and not too many; while the news feeds work off a cache which we update upon request or every few minutes. In total this means we can provide any number of updates to our visitors with fewer than 350 hits to tfl's website per day. ie. Rather than adding to tfl's server load [the only objection tfl might have to this system] we can actually reduce it enormously

Why do you do it?

A mixture of:

Most importantly; because London Underground do a good job of collecting and using data, unlike so many other bodies, but there's so much more which can be done when data is published at a granular level via the internet. I want to demonstrate some of these uses

a belief that public bodies like tfl should be thoroughly accountable

belief in digital public information freedom

frustration that the tube's service can be unnecessarily bad and that their standard aggregated stats do not always show this

Weaknesses/issues

Useability - apologies for crap layout and useability issues. I wanted to experiment a little with CSS and am not quite there yet.. It will be improved over time.

Currently it works off the tube live information page. It also grabs the news ticker from the tfl front page. I intend to, but don't yet, use the two sources as a cross-check (they are different surprisingly often).

The stats are currently dependent on the quality of info provided by TFL.

TFL's definition of what constitutes a delay

TFL's inconsistent coding of incidents which can cause our engine to miss issues [this is very rare] or not identify the details of the issue[more frequent, but not too bad]

Gantt charts are delivered by the excellent JPGraph library for php, but currently use the beta version 2.0 which is not yet thoroughly stable. You may occasionally need to refresh the window to get a 'stuck' gantt to load properly. Additionally, gantts are currently generated entirely on demand, and cause a fair load on the server so we may start caching them with, say, hourly updates