It’s been a while since we looked in on Collideoscope, our project for reporting and collating data on cycling collisions and near misses, developed in collaboration with ITP. But what better time than now, when days are short and accidents have unfortunately, as always at this time of year, taken a sharp upturn.
So, let’s have a catch-up, and a reminder that you should use the service. Of course, we hope you won’t experience any problems, but remember that Collideoscope is there if you do.
Previously on Collideoscope…
As you may recall, Collideoscope is a site for reporting cycling incidents, collisions and near misses. Because it’s built on the FixMyStreet platform, it offers all the same functionality for the user: it’ll help you to pinpoint the precise location of the incident you’re reporting, and then send the details off to the relevant authorities.
When cyclists make a report, they’re contributing to an open dataset that improves the quality of the evidence base on cycling incidents.
While FixMyStreet sends reports off to councils, Collideoscope sends reports to local authorities’ highways departments, with the aim of highlighting potential accident blackspots.
The data, after going through an anonymisation process, is also shared with campaign groups.
Finally, the anonymised data is also available for anyone to download via Socrata, to be used for any purpose. One potential project we’d love to see, for example, would be route-planning applications to help cyclists avoid going through areas with a high density of incidents.
The data is also available to researchers, town planners and the police: when cyclists make a report, they’re contributing to an open dataset that improves the quality of the evidence base on cycling incidents.
So, that’s the model. Let’s have a look at how well it has stood up.
Collideoscope launched in October 2014 and users have thus far made a total of 1,195 reports.
In order to provide a more complete dataset with the clearest possible indicators of accident hotspots, we also imported STATS19 data from the annually-updated open police database of accidents, meaning that Collideoscope now contains data points on over 20,000 incidents across the UK.
Here’s what we’ve learned
Steering a project from concept to reality is always a learning process. Here are some of the key lessons that emerged:
- Collideoscope sends each report to authorities as it is submitted. It became clear that a bulk dataset would be easier for highways authorities to handle and to draw conclusions from, and this is now available.
- Originally, we’d believed that it would be useful if Collideoscope could forward reports to local police forces, so that they could be actioned where suitable. However, this proved impractical, because the Road Traffic Act states that collisions must be reported to a police officer in person. Collideoscope’s data would not be sufficient for police to take action on those cases which merited it.
- There was some concern that reports made via Collideoscope would replicate, rather than complement, the police force’s official STATS19 data. Happily, once enough reports had come into Collideoscope, a comparison was run and found that there is very little overlap between the two datasets.
While STATS19 data tends to cover serious incidents, it doesn’t hold much on the near miss or minor incidents that Collideoscope encourages users to also report — and which make up 90% of the Collideoscope database. One of the underlying beliefs behind Collideoscope has always been that near miss data can tell us a lot about accident prevention.
ITP have now stepped away from Collideoscope: we’re extremely grateful for their collaboration and support with the development and running of Collideoscope in its first couple of years. This move will mean that we can pursue funding from charitable grant foundations.
As you may recall from prior updates, the site was also supported by the Barts Bespoke campaign, a multi-pronged initiative to reduce accidents for cyclists. This support, and a further research grant from the Department for Transport, came to an end last month. As a result, we’ll no longer be asking people about injuries sustained when they file a Collideoscope report.
Collideoscope will keep on rolling: we’re open to potential partners and have plenty of ideas for further development, including the possibility of a public API, or incident-reporting forms that could be placed on any website.
If you’re from a local government, third sector or private company, and you’re interested in using Collideoscope data to enable better decision making on cycle safety, this’d be a great time to get in touch.
This hill is dangerous by John Kennedy (CC by-nc/2.0)
Falling off bike sign by Rob (CC by-nc-sa/2.0)