Post by cso on Dec 6, 2012 20:45:59 GMT
Now, before anyone jumps, I know TfL publish some of the information I'm about to talk about through their APIs...
However, the question I put is as per the subjection line: Should TfL take a leaf out of Network Rail and release more of their data openly?
For example, Network Rail publish digital, and reusable timetabling data, and things like Temporary Speed Restrictions are available as well.
What benefit is there to TfL not publishing information?
The argument is usually "the tube is a turn up and go service" but with some lines, having timetable data available could be considered a benefit - so you know the next service is going to Heathrow or Uxbridge, how long it might wait at Terminal 4, or which branch of the Met Line you're going on.
Personally, as a developer and a geek, I'd appreciate the opportunity of doing something if I wanted to... I mean, I can get Real Time data from Trackernet (as best as it works!) so why not the timetable to correlate the data too?
However, the question I put is as per the subjection line: Should TfL take a leaf out of Network Rail and release more of their data openly?
For example, Network Rail publish digital, and reusable timetabling data, and things like Temporary Speed Restrictions are available as well.
What benefit is there to TfL not publishing information?
The argument is usually "the tube is a turn up and go service" but with some lines, having timetable data available could be considered a benefit - so you know the next service is going to Heathrow or Uxbridge, how long it might wait at Terminal 4, or which branch of the Met Line you're going on.
Personally, as a developer and a geek, I'd appreciate the opportunity of doing something if I wanted to... I mean, I can get Real Time data from Trackernet (as best as it works!) so why not the timetable to correlate the data too?
I've informed the creator/maintainer
