UK police crime map website: Who's the victim here?
Do a man dirt, yourself you hurt
Analysis Earlier this week the Home Office unveiled its crime-mapping website, which was developed by Leicester-based ad agency Rock Kitchen Harris for £300,000.
Immediately following the site’s launch, Police.uk suffered a serious bout of stage nerves as it wobbled under the demand from UK residents seizing the chance to find out what crime was being committed in their neighbourhoods.
A Home Office spokesman, who didn’t quite grasp what an API was*, told The Register at the time that Police.uk was taking between four and five million hits an hour, hence its inability to keep up with demand. For many, that explanation didn’t square given the hundreds of thousands of pounds pumped into the project. Worse still, the whole thing runs atop an Amazon Web Services EC2 box, which ought to have allowed it to scale, even when fielding millions of hits from street stalkers and property pervs across the land.
As we were quick to report, ahead of the alarmist cries of “website down” from the mainstream press, the site itself offered the first conclusive smack in the face to open source and open standards developers in Blighty, who have largely welcomed the ConDem’s approach to what is seen by many to be a thoroughly sensible panacea for the handling of government data online.
Then step forward one man who grabbed the data and created his very own police crime-spewing stats website in eight hours flat. Software architect Rob West’s Crimesearch.co.uk portal might lack the kind of prettiness, bandwidth or scale that Police.uk supposedly boasts, but it does demonstrate what one bored coder can do in response to a fantastical cash splurge by a government apparently obsessed with keeping costs down.
“At my reckoning and at Home Office rates [£300,000] they should have paid me £37,000 per hour!”, West told us.
He echoed what other developers have been asking about Police.uk since its data release, endorsed by the Information Commissioner’s Office, on Tuesday: why did it have to cost so much?
Sadly, the Home Office hasn’t been willing to provide a comprehensive answer, instead preferring to tell us that it couldn’t say much about the £100,000 backend and £200,000 development costs for “commercial reasons”. But the government’s agenda to be more “transparent” about its data just took a small yet arguably significant blow.
“If the Home Office wanted to keep control of this project and specify the website functionality, all they needed to do was pass this piece of work onto a small web development company, who could have done it for less than a tenth of the price,” opined West. “Then they could have done their own PR. I suppose their issue with a small company is it might be viewed as high risk. ‘Nobody got sacked for buying IBM’ sort of thing.
“Better still if they had released the raw data and let someone pick it up. Yes, they wouldn't be able to specify the functionality, but wouldn't the functionality be defined by evolution? The best functionality would get the most hits, and therefore would survive.
"I am sure there are many developers out there that would do this sort of thing for the good of the community. I know I have banner ads on my website, but believe me they don't generate that much revenue.
Sponsored: DevOps and continuous delivery