ASBOs went away this week.
The asborometer is still considered the epitome of the simple hack day app – plot some stuff on a map and it relates to where you are, or where you would like to be. For simple, clear, tangibly useful outputs, it’s one of the few things that is both within the scope of a hack day (if the data lets you) and immediately understandable by the wider world. For external conversations, it’s still used for those purposes.
2 years ago, at the first hack the government day, this was advanced; a year ago, it was still pretty; by now, we should have moved on. We do have a better examples to use.
When open data was a bunch of people from outside throwing perl scripts against the walls to see if they would magically crack, that was ok. We had no power, and were doing what we could in the hope that someone would notice. In those times, it was completely OK to give little consideration to anything beyond building something that someone might notice. Because might notice was a win.
But now, we’ve moved on in terms of influence.
As a community, we’re no longer on the outside throwing python scripts on github.
We have real power now.
Cabinet Ministers are expending political capital on getting data to us.
Should we still consider the asborometer as the pinnacle of what we do? We still act as if it is.
The issue isn’t code any more, or necessarily access to data; it’s the data we choose to include. The awesometer is a counter-point; but we should no longer laud an app with a fear-mongering selection of data, as if there’s no clear comparison to some of the Daily Mail lunacy we mock on twitter 5 minutes later.
It’s ok to screwup – even community friends at the Guardian DataBlog sometimes use data to create a post that’s at best a rewrite of an agenda pushing press release. Not everything will be suitable for examples – but the solution is to think about what is used as a laudable example.
Crime Maps
There are various narratives about the crime maps. The best and most well considered is the Guardian’s Editorial. On twitter, the people I follow include disparate groups of people who are technical, and who are activisty or policy types who aren’t. The response of the first group to the crime maps was overwhelmingly negative (not wishing to single anyone out). But it was mostly for technical reasons – “I could have built a website which did that at scale”.
In some comments, what was missed was the point of the exercise. Harry somewhat agrees (possibly for different reasons). But this is something that needs more discussion.
Not that commentary was necessarily completely wrong on some levels – the website did collapse under 750k hits/hour doing interactive searches – a load that needs some serious infrastructure (it was EC2) and good design behind it. That’s not the point. The underlying point of crime maps, asborometer, and the thing we produce, is what tools do we think are important (there are many answers), and what do we use them to do? Different answers to those questions have different constraints.
Asborometer was built to see the reasons you could be afraid. And it’s still a canonical example of what we think open data is for. Some of the same people who use that as their laudable example also wondered on twitter why they didn’t get privileged advance access to a media sensitive crime dataset.
If open data is to remain in the centre of the agenda in a sustainable way, we must consider the examples we use from the perspectives of everyone. And some of the apps that were built, which were valuable in their own way, may need replacing as examples which are slightly more inclusive.
If the open data community hasn’t outgrown the asborometer, then we don’t deserve access to other, better data. And that’d be even more embarrassing.
In the week that the Government ditched ASBOs, the community should ditch the asborometer.