London Transport Data opened up

The best information I can get out of it is in this style:
apibeta.london.gov.uk/TrackernetWebServicev3/timetableService.aspx?Feed=4&Line=H&StationCode=GPS&Time=30
I'm sure the different codes (I assume S means train no., and D is destination number) are explained somewhere, but I have problems finding it.
Much better to use than departure boards though, just have to find a list over the station codes first!

You can get better - apibeta.london.gov.uk/TrackernetWebServicev3/timetableService.aspx?Feed=5&Line=N&StationCode=BNK&TimeDuration=30

I have an itch to create a real-time map showing the locations of all running services...

edgemaster: Someone (it might be you...) has already done it: traintimes.org.uk/map/tube/

Very impressive.

I notice that anything running on the Circle - including the District side - is shown as a "Hammersmith &Circle." There was also a District Line train 000 travelling at roughly 200mph between Earl's Court and Wimbledon and back when I looked earlier. Obviously a new service the Green Line has failed to publicise ;D

I can certainly see the benefits of having an app similar to this on your mobile - especially if you're waiting for a train on an open-section platform. However, I dread the day when such information is stored and replayed following disruption and people begin to criticise the way in which we have handled the service. Our own management do that already. They are experts in hindsight - taking maybe only 2 weeks to come up with an alternative to the decision I had to make within 30 seconds on the day.

It's when I think of drawbacks such as this that I then wonder if we're revealing a little too much. But then, the world is changing...

Maybe the London Metro(politan) and the Paris Metro are finally merging?

But central France to Moor Park in 30 secounds? No way.

Management already have this facility on Trackernet, and can replay any event up to 28 days in the past. Plus with virtually everything recorded anyway, a full record is always at hand to those who may need it.



It's one thing to turf a trainload of people out at Harrow, but another to be judged for that decision by those who think they know better. What the new information doesn't do is tell you the full story of why a train may need to be detrained or its destination changed.

My point was that when we need to make these decisions - which are never taken lightly because we are watched by our own management - the last thing any of us then needs is someone, say on a forum like this, posting a link of some sort of replay, complete with how they think things should have been done. Statements such as "You had a train behind and could have done x,y,z and then the original train could have done a,b,c and then the outcome would have been e,f,g."

That kind of explanation is already sought on here by some. There's nothing wrong with that at all, and I am always happy to explain where I can. However, it becomes more frustrating when you are faced with an actual "playback" of what happened. Given too much information, people tend to start trying to do your job for you.

Watching the data earlier, I spotted a gap on the H&C. But even I, a qualified Controller on that line, would never pass any kind of judgement because, unless I am at work, I don't have the first idea of what is actually happening.

Something I've noticed. H&C Trains are labelled as "Metropolitan Train to Hammersmith/Barking" etc, is this a historical throw back to the old Met of yore?

Furthermore just to confuse matters I've seen a "Hammersmith & Circle train to Barking Sidings" as well. Its rather interesting to watch them all move ;D

Cheers,
~ TGR

The access to this API is back, although you now need to register for it...

Thanks to @anniemole on Twitter for the news.

data.london.gov.uk/blog/guess-whats-back-trackernet-returns