As Zarino explained in his recent blog post, we’ve recently spent time talking to road safety advocates and cycling groups, as we prepare for some big improvements to Collideoscope.

This has resulted in a shortlist of the tickets we’ll be working on, which you’re welcome to browse (and comment on, though this requires a Github account).

Collideoscope, like many mySociety projects, is a website of two halves. On the one hand, it invites those involved in a cycling collision or near miss to contribute information to a database; on the other, it provides an output of all that aggregated data for planners, researchers, campaigners and anyone else who will find it useful.

We’ll shortly be making some changes to the site so that its purpose and functionality are crystal clear; but in the meanwhile the next important step was to import the most recent batch of STATS19 data.

STATS19 is the form the police fill in when road accidents are reported, lending its name to the dataset released annually by the Department of Transport. We include this data on Collideoscope alongside our users’ reports: we just take the reports which refer to cycling incidents, and with this latest update we’re now displaying everything from 2013 up to 2016, the most recent data available.

That means, when you browse the site, you can see at a glance how many incidents have occurred in a specific area, not just from our users but from the primary national accident database too. Just click the checkbox (‘show reports from the Department of Transport’) at the top of the page to include them on the map.

So that’s our most recent bit of housekeeping; now watch this space for some bigger changes to Collideoscope.

Image: Charisse Kenion

Original source – mySociety

Comments closed