Home

Follow Skinkers.

Recieve all the updates from Skinkers via email:

 

Posts Tagged ‘Article’

0

Local government data: how to make it really open

July 7th, 2010 | Data, From The Guardian | Tim Heyes

Powered by Guardian.co.ukThis article titled “Local government data: how to make it really open” was written by Simon Rogers, for guardian.co.uk on Wednesday 7th July 2010 07.00 UTC

We all thought Coins was going to be the government’s promised “tsunami of data”, but the real data storm is going to come when local government (under Downing Street duress) will release every spending item over £500.

This should be a moment to celebrate, for developers, journalists and everyone concerned with how councils spend our council tax. Instead, campaigners are united in anxiety that what we might get could just be more of the same.

And it all started so well. Local government secretary Eric Pickles told councils that:

“I don’t expect everyone to get it right first time, but I do expect everyone to do it”.

Well getting it wrong might be the default position for some local authorities. CountCulture’s Chris Taggart is concerned about data company Spikes Cavell’s SpotlightOnSpend muscling in on local government data (you can see his latest post on the issue here).

The upshot seems to be this, councils hand over all their valuable financial data to a company which aggregates for its own purposes, and, er, doesn’t open up the data, shooting down all those goals of mashing up the data, using the community to analyse and undermining much of the good work that’s been done.

Paul Bradshaw reports that a Help Me Investigate page has been set up over the issue, to see how widespread it really is.

Spikes Cavell has been stung by the furore – chief executive Luke Spikes has pledged to allow raw data downloads, according to Information Age.

As it is, there is a real fear that councils could get it clangingly wrong. Openlylocal’s data scoreboard shows that only 15 out of 434 local councils are publishing open data at the moment – only seven of them in a truly open format.

There seems to be a panic up and down the country among councils suddenly faced with releasing data they’ve previously kept to themselves – presumably combined with beffudlement over why they have to do it at all. If that panic translates into a default position of outsourcing the task, then we have real problems.

The thing is, there are no shortage of official guidelines showing exactly how to release the data. The Local Data Panel has a concise and clear set of principles for local data release – worth reading for their clarity alone. The Open Knowledge Foundation does too.

Essentially, they boil down to some pretty simple ideas:

1. Make it open

No T&Cs about not using the data for commercial use, no restrictions on access. Make the data available to anyone to do whatever they want to with it. That’s the only way that the data information revolution is going to work.

2. Make it readable for computers

The data needs to be in a format that any computer can use – no more PDFs, thank you very much. If developers can’t build applications and campaigners can’t analyse it, what use is it?

3. Make it granular

The days when we only wanted official statisticians to just put the numbers together in a way we could understand are gone. Now we also want the full, disaggregated data too. It’s the only way it will ever be useful for someone wanting to gather the true local picture of local spending. Let us worry about whether the dataset is too big or not. It’s not your problem anymore.

4. Make it quick

Just get the stuff out there. We’d rather have it as it is – and then get it revised later than have to wait months for it to be finalised. The government has provided express permission for local authorities to do this. So just do it.

5. Make it easy to find

There’s no point hiding this stuff away. If we can’t find it, it may as well not exist. It should be easy to discover and simple to access.

That’s a manifesto we can sign up to. What do you think?

Can you do something with our data?

Flickr Please post your visualisations and mash-ups on our Flickr group or mail us at datastore@guardian.co.uk

World government data

Search the world’s government datasets

More environment data
Get the A-Z of data
More at the Datastore directory

Follow us on Twitter

guardian.co.uk © Guardian News & Media Limited 2010

Published via the Guardian News Feed plugin for WordPress.

0

Live tube map halted as TfL hit by 50-fold growth in web calls

July 2nd, 2010 | From The Guardian, Tech | Tim Heyes

Powered by Guardian.co.ukThis article was written by Charles Arthur, for guardian.co.uk on Friday 2nd July 2010 11.27 UTC

Stop all the tubes, cut off the API. Transport for London has had to stop its supply of data about the movements of Underground trains due to “overwhelming demand” from demonstrations of what can be done with that data such as Harry Metcalfe’s Matthew Somerville’s maths-and-magic live tube map. (If you try to go to that site now it just hangs.)

The reason: after opening up the API, requests for data ballooned from 180,000 to 10m. Consequently, TfL found itself a bit underprepared.

As the London Datastore – which has been the throughway for those API requests – notes,

“Owing to overwhelming demand by apps that use the service, the London Underground feed has had to be temporarily suspended. We hope to restore the service as soon as possible but this may take some days. We will keep everyone informed of progress towards a resolution.”

Our understanding is that the London Datastore is now encouraging TfL to serve API requests directly, rather than proxied through the data store, because that will mean that TfL gets a clearer idea of who the customers and developers for its data actually are, and where they’re based.

In the comments to the blogpost, there are some useful suggestions for TfL about how to improve the service while easing the strain on its (well, the LDS’s) servers: more partitioning of feeds with less data per feed, and more caching. Obvious to developers – not so obvious to an organisation which has lived its life functioning, as one developer described it to me, as “a black box that people pour money into and which then spits out travel”.

But for TfL, the lesson is clear: there’s real, eager demand for its data via an API. There are people who have positive, helpful suggestions for how to improve its servicing. And it’s being advised to hold those customers/developers closer, rather than at arm’s length. It’s going to be interesting to see how it progresses.

Now, can we have the live tube map back please? Soon?

guardian.co.uk © Guardian News & Media Limited 2010