I’m a big fan of London’s Barclays Cycle Hire scheme. I praised it when it was introduced, I created a free API service for developers to help them get live data about bike availability to make useful apps for people, I built a realtime 3D visualisation of bike availability and I even wrote a simulator to help me better understand bike movement patterns. I still think it’s a great system and I’m keen to do what I can to help people use it and to make it work better.
So when Boris announced that the scheme had just passed its one millionth journey milestone it seemed like a good time to ask Transport for London for the journey data. It’s an easy enough job: Just a single database query to fetch the times, origin and destination of each trip. If I could load this data into my simulator I might be able to see where extra bikes and docking stations might be needed. I put in a Freedom of Information Act request, confident that I’d have the data within the 20 working days limit required by law.
That was three months ago on 8 October. I’m still waiting.
The good news is that the data has just been made available in TfL’s developers’ area and some people are already starting to do interesting and useful things with it. But behind that happy fact is another example of a public body deciding to completely ignore their Freedom of Information Act responsibilities and the rights of an applicant in pursuit of its own perceived interests.
Data delayed is data denied
Under the law, public bodies have got 20 working days to reply either with the information requested or to claim an exemption. The time limit is there for a good and obvious reason: Without it, public bodies can string an applicant along indefinitely, and with many requests being time-sensitive this can often past the point where the information would be useful.
Fortunately I didn’t have a specific deadline for using this data but it certainly would have been more useful to me sooner rather than later. I could have been working on it for two months by now. And if TfL had been keen for other developers to use it, they could have had it too. Some developers were keen to get hold of it for the Open Data Hackday on 4 December last year but that came and went without any sign of the data.
So why was the data delayed? I estimate that there would have been less than two hours work to produce it and send it to me, or to put it on an open website where anyone could download the file.
“Your free information is in this locked box. Sign this contract and if we like what you’re doing you can have it.”
The answer lies in TfL’s desire to wrap the data in a complicated contract rather than make it available to me or anyone else directly and legally unencumbered. This might make sense in the context of some data and some data users but it’s directly inimical to the aims and indeed the law of freedom of information. The data in TfL’s developers’ area isn’t open data and it’s not available to everyone. As the site says:
Please complete the registration form below to use our syndication feeds. Before we give permission to use any feeds, we need to know how they will be used, where they will be used and how many people are likely to view them.
So why should anyone have to apply for permission to get access to their freedom of information answer? Why not just send it to the applicant?
The Information Commissioner, who regulates public bodies’ compliance with the Freedom of Information Act is quite clear that information must be supplied regardless of the identity and motives of the applicant. His guidance (PDF) states:
A request therefore has to be considered on the basis that it could have been made by any person; the identity of that person is not a material consideration when deciding whether or not to release information. It is for this reason that we do recommend as good practice that requests under obvious pseudonyms should normally be considered unless there is reason to think that any of the matters below need to be taken into account.
There follows some general exceptions regarding vexatious requests, people requesting their own personal information and costs issues, none of which apply in this case.
On the issue of the applicant’s motives:
There is also no specific reference in the FOIA to the principle that requests for information must be considered without reference to the motives of the requester.
However, there are no references in the Act indicating that anyone can be asked to provide a reason for requesting information and it is from this absence that the principle [of disregarding the applicant's motives] is drawn.
The Information Commissioner then quotes the Lord Chancellor’s code of practice on freedom of information:
Authorities should be aware that the aim of providing assistance is to clarify the nature of the information sought, not to determine the aims or motivation of the applicant. Care should be taken not to give the applicant the impression that he or she is obliged to disclose the nature of his or her interest as a precondition to exercising the rights of access, or that he or she will be treated differently if he or she does (or does not).
But if I want to get a response to my FOI request from TfL I am asked to enter into a contract with them whose terms include:
2.1.2 [You shall] only use the Transport Data in accordance with these Terms and Conditions and the Syndication Developer Guidelines, and not use such information in any way that causes detriment to TfL or brings TfL into disrepute. The rights granted to You under these Terms and Conditions are limited to accessing and displaying or otherwise making available the Transport Data for the purposes stated by You in Your registration.
So not only is TfL’s contract explicitly asking me to state my motive as a precondition of access, it also constrains me from using the information for any other purpose and arguably prevents me from using that information to criticise TfL, thereby causing it “detriment” or bringing it into “disrepute”. If I don’t agree to this they can deny access altogether and if I subsequently break the agreement in their view they can revoke access. This is a funny kind of free information.
The Freedom of Information Act is designed to enable scrutiny of government. It’s inevitable that some information requested may cause embarrassment to the public body providing it or even bring it into disrepute. If the law is going to be workable at all, public bodies must consider each application on its merits alone without concerning themselves with the applicant or their motives. To do otherwise would allow public bodies to effectively pick and choose which requests they answered. TfL’s decision to require me to enter into an extremely restrictive contract with them to get a response to my freedom of information request is applicant and motive discrimination by the back door. It’s not something that should be tolerated from TfL much less adopted by other public bodies as a way to weaken FOI applicants’ rights. Free information should not come wrapped in a restrictive contract wall. That’s why I won’t be accepting TfL’s terms and I’ll simply have to leave the analysis of this Cycle Hire data in the very capable hands of others.
Tags: Boris Johnson, cycling, FOI, Freedom of Information, london, open data, TfL, Transport for London
Do you have any accident data for these bikes. Since they generate such good stats, one would thing we could know a lot about the accidents which are happening with these bikes, the circumstances, etc. Much appreciate any leads you can provide.
As far as I know there are no released figures for accidents. But the scheme includes public liability insurance for riders so there are presumably logs kept of incidents and claims.
You could put in a Freedom of Information request directly or through What Do They Know.
Disgraceful – I have blogged in support of you http://www.bigbrotherwatch.org.uk/home/2011/01/transport-for-london-breaks-the-law-.html and have complained to the ICO.
This seems to be another example of authorities not really living up to the promise of open data. The use of FOI is a great tactic: have you complained to the ICO about the lack of timely or satisfactory response?
Jim,
I want to be very clear about separating the open data and FOI issues.
FOI is a last resort from an open data point of view and data released through FOI doesn’t automatically become open. Nonetheless, I have unsuccessfully tried to persuade TfL that this data is eminently suitable for publishing as open data and being made available outside their developers’ area with a standard open licence. Unlike some of the realtime data feeds that TfL offers in their developers’ area, this bike movement data is historical and I can see no likely way in which its misuse is going to screw up anyone’s journey or unfairly affect TfL’s reputation.
The FOI issues are:
- requests should be serviced promptly and at the very least within the statutory time limit
- responses should be given unencumbered by additional contractual requirements
- no regard should be given to the identity and motive of the applicant (they shouldn’t even ask)
- no constraints should be put on the purposes to which the response may be used, other than the general requirements of the law
Mike and Adrian
Not got data on accidents, but I submitted to TfL an FoI request for number of naughty Boris Bike riders. Must be loads, yes?
Nope: http://ipayroadtax.com/no-such-thing-as-road-tax/bike-licensing-doesnt-work-just-ask-boris/
Whilst they’ve dragged their heels a little with actually making the data available, have you considered the likely communications within TfL?
FoI team: “We’ve got this 150Mb file of bike journeys we need to make available to this guy Adrian somewhere on our website”
IT team: “Ok, we’ve got an area set-up for transmitting data to the public, we can put it on there”
FoI team “Fantastic, can you send us the URL details?”
IT team “Sure, we’ve put it in our ‘Developers Area’, just get the guy to fill out this form and will give him the password to get to his file”
FoI team: “Ok, thanks”
2 problems are likely:
- IT team doesn’t appreciate that it has just caused a problem
- FoI team doesn’t read the sign-up form
My money is on this simply being a cock-up rather than anything malicious.
Bimbles,
The method physical used to deliver the data to me isn’t really that important. TfL is just using it as a smokescreen to cover for the fact that they’re insistent that I sign a restrictive contract before I’m allowed to access the data.
If you read the correspondence you can see that I tried to persuade TfL to send me the data directly rather than put it in the developers’ area and subsequently TfL’s legal and press officers have been defending their decision as FOIA-compliant.
But on the data delivery issue alone, it’s not hard. The file is 25MB. It’s actually small enough to email as an attachment and What Do They Know say they can handle that. The file is also available at an unauthenticated URL and TfL simply has to say that I can access it without accepting the developers’ terms and I’ll be happy.
I really have been very patient about this, quite clear about what I require and have only asked to be treated the same way as any other FOI applicant.
Have you noticed that the data that have been released via the TFL developer’s area only seem to include journeys made between 06:00-23:59? I can’t find any data for bikes released from their docking stations between 00:00-5:59am, and would therefore appear incomplete. Unless I am misreading the data, it would appear therefore, regardless of the way in which the data have been made available, TFL have not yet released the ‘first million journeys’ as requested.
on the subject of bike crashes, I note in the original TfL response: “Please note the spreadsheet excludes 180 journeys which do not have an end station “.
My initial read of that was thefts (and system malfunctions: I’ve had a couple of occasions where my journeys have just not been recorded), but it could involve other incidents where the bike journeys genuinely weren’t completed.