Posts Tagged: Boris Johnson


28
Apr 11

Boris says bye-bye to indie Boris Bikes developers

Barclays Cycle Hire app iTunes screenshot

9 May 2011: Some of my assumptions in this post are wrong so please read it in the context of Emer Coleman’s comment below.

Courted, used and discarded in less than a year. That’s Boris’s and Transport for London’s attitude towards independent app developers for the Barclays Cycle Hire scheme.

Let’s take it from the beginning.

A month before TfL launched their new cycle hire scheme, Boris was very keen to get independent developers on board. Why? Some deep commitment to digital diversity or small government doing what it does best and leaving the rest to the market?

Not really. Just that in 2010 if you’re launching a public cycle hire scheme in a major world city you need an app. And there wasn’t any budget allocated for one so the open data line was expedient.

Let’s hear some of the bull from back in June 2010:

In build up to the launch of the Mayor’s Barclays Cycle Hire scheme on 30 July, Transport for London (TfL) has relaxed its terms and conditions to allow commercial use of official data – opening the door for developers to provide accurate and reliable information about the hundreds of locations where hire cycles will be available, smart routes around town or proximity of docking stations to Tube stations and places of interest.

Of course this wasn’t actually true anyway. TfL didn’t release any live machine-readable data about bike or dock availability at that point. In fact, they still haven’t.

More bull from TfL:

Independently produced apps will complement the wealth of information that TfL is already generating to keep users up to speed about the scheme.

So what happened? Indie developers got on board only to find that they had to screen scrape data from TfL’s web map, the only publicly-available source of data. No real API, no service level standards, no support. And very often crap data.

The incident where TfL’s map started serving up data from the Montreal cycle hire scheme being just one case in point.

The indies have muddled through, producing some good apps that very often have been held back by poor and unreliable data. When it comes to realtime information services, your app is only as good as your data.

People have invested time and money in these apps, largely in the hope that TfL would see them right soon enough.

All the while, developers have been pressing TfL for a real API. The story has always been that it’s coming… one day.

I think it’s reasonable to say that indie developers have made a big contribution towards Barclays Cycle Hire’s success. There aren’t unlimited bikes and you need to be able to find them. It’s handy to have a timer to help manage the costs. And you need a map on the go just to find the docking stations. You need an app.

TfL have been happy to take the credit for the indie cycle hire app and analysis work that they’ve done next to nothing to support.

And now we get the final confirmation of where TfL really stands on indie developers and open data: This week Barclays launched official iPhone and Android apps for the scheme.

These free apps (with all of Barclays/TfL’s marketing support behind them) wipe out the largest markets for indie apps at a stroke.

 

Moreover, Barclays own apps will doubtless be using a private API to which they have privileged access. So their apps get good quality data while everyone else struggles along with the leftovers.

I’m told, unofficially, that an official cycle hire API is coming soon. But I’ve heard that story before.

When it comes — if it comes — it’ll be useful for the people doing data analysis and building cycle hire data into novel apps and games like Chromaroma.

But for the mass market — indie developers making and selling standard find a bike/dock apps — TfL just doesn’t need you any more.

The parallels with Twitter’s attitude to its API are clear: Having built a successful service on the back of indie developers’ labour, it’s now time to take the good stuff in house and reap the rewards. At least Twitter provided a proper API.

The question remains: Who’s driving Barclays Cycle Hire, Barclays or the mayor?

Perhaps the clue’s in the name.


7
Jan 11

TfL’s information doesn’t want to be free

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.


1
Aug 10

Boris Bikes — A gift to the city

IMG_1087

If you’ve ever wanted to whistle up a pair of wheels while walking around London, now you can. Friday’s launch of the Barclays Cycle Hire scheme puts 6000 short-hire bikes at 300 docking stations within a few hundred metres of any point in the centre of the city. No matter where you are, you shouldn’t be more than a few minutes’ walk from a hire bike.

Continue reading →


20
Apr 09

Comments not allowed at your council website? Here’s how to answer back

UPDATE 27 Feb 2010: The Boris Backchat blog mentioned in this post has served its demonstration purpose and has now been deleted.

A few people have raised the objection that what Mash the State is currently doing with council RSS feeds is really just helping councils to deliver their PR (or as those critics often like put it, “propaganda”).

In one sense, they’re right. A council’s press releases or “news” are just their own side of the story. You’d have to be pretty naive to think otherwise.

But getting any kind of information out into the open where it can be scrutinised, compared, cross-referenced and easily discussed is always an advantage. Here’s how to build a discussion blog around your local council’s news. Of course, if they don’t have an RSS feed this isn’t possible, which is why Mash the State exists in the first place.

Time required: Around 15 minutes.

Skills required: Just basic web use stuff. No programming or HTML. Anyone online should be able to do this.

Here’s one I made earlier: Boris Backchat. Got something to say to the London mayor? Just leave a comment.

Apologies to those outside London — I had to choose something!

Here’s how I did it:

1. I registered a new blog on WordPress.com. This is free and only took a moment.

2. I found the URL (web address) of Boris’s RSS feed. Visit your local council or other government website and hover your mouse over the RSS feed link or icon. Right-click and choose “Copy shortcut” (Internet Explorer) or “Copy link location” (Firefox) or whatever your browser gives you in the right-click menu.

In this particular case it was easier to grab the feed URL from the Greater London Authority Mash the State page.

gla-screenshot

3. I signed up at xFruits which has a whole set of free tools to do things with RSS feeds. This is free.

4. I used the “RSS to my blog” tool on xFruits which automatically copies the contents of an RSS feed into a blog, making a new blog post for each item in the feed.

xfruits-rss-to-blog

First I typed a title for the new blog site and a few tags.

xfruits-step-1

Then I pasted in the feed URL that I’d copied in step 2.

xfruits-step-2

To configure this I also needed the URL of my new blog’s “API endpoint”. This is the address which other programs can use to push data into your blog.

The API endpoint URL for this blog is:

http://borisbackchat.wordpress.com/xmlrpc.php

The format is the same for all blogs on WordPress.com:

http://yourblogname.wordpress.com/xmlrpc.php

I also had to type in my WordPress username and password, and as I’ve got several blogs on WordPress, had to choose the right one to send the RSS feed to from the drop-down menu.

xfruits-step-3

5. And that’s pretty much it. I went into the WordPress settings and set the time zone correctly and edited the site description. Now we’re ready to go.

To close the loop, if you want to keep up with the latest posts on Boris Backchat you can subscribe to both the new posts (articles) and comments in your RSS reader.

xFruits will work with most popular blog systems including Blogger, TypePad, Movable Type and WordPress hosted on your own server.

Welcome to open government. :)

Thanks to Jon Bounds on Twitter for tipping me off about xFruits. It’s a great set of tools. Jon has just set up a similar site for Birmingham City Council.

… and as I always like to say about these things, it’s taken longer to write about it than to do it!