1. Training an AI to generate FixMyStreet reports

    Artificial intelligence and machine learning seem to be everywhere at the moment – every day there’s a new story about the latest smart assistant, self-driving car or the impending take over of the world by robots. With FixMyStreet having recently reached one million reports, I started wondering what kind of fun things could be done with that dataset.

    Inspired by a recent post that generated UK place names using a neural network, I thought I’d dip my toes in the deep learning sea and apply the same technique to FixMyStreet reports. Predictably enough the results are a bit weird.

    I took the titles from all the public reports on fixmystreet.com as the training data, and left the training process to run overnight. The number crunching was pretty slow and the calculations had barely reached 5% in the morning. I suspect the training set was a bit too large, at over 1M entries, but end result still gives enough to work with.

    The training process produces checkpoints along the way, which you can use to see how the learning is progressing. After 1000 iterations the model was starting to be aware that it should use words, but didn’t really know how to spell them:

    Mertricolbes
    Ice does thrown campryings
    Sunky riking proper, badger verwappefing cars off uping is!
    Finst Knmp
    Lyghimes Jn fence
    Moadle bridge is one descemjop
    

    After 15000 iterations it’s starting to get the hang of real words, though still struggling to form coherent sentences.

    Untaxed cacistance.
    Broken Surface in ARRUIGARDUR. Widdy movering
    Cracked already nail some house height avenue.
    Light not worky
    I large pot hole
    Dumped shood road nod at street.
    Grim
    Dog man
    Ongorently obstructing sofas. This birgs.
    Serious Dirches
    

    After 68000 iterations there seems to be enough confusion in the training data that things start to go south again with the default parameters:

    Urgely councille at jnc swept arobley men.
    They whention to public bend to street? For traffic light not working
    

    Tweaking the ‘temperature’ of the sampling process produces increasingly sensible results:

    Large crumbling on pavement
    Potholes all overgrown for deep pothole
    Very van causing the road
    Very deep potholes on pavement
    Weeds on the pavement
    Several potholes in the road
    Rubbish Dumped on the road markings
    Potholes on three away surface blocking my peride garden of the pavement
    Potholes and rubbish bags on pavement
    Poor road sign damaged
    Poor street lights not working
    Dog mess in can on road bollard on pavement
    A large potholes and street light post in middle of road
    

    As well as plenty of variations on the most popular titles:

    Pot hole
    Pot hole on pavement
    Pot holes and pavement around
    Pot holes needings to path
    Pothole
    Pothole dark
    Pothole in road
    Pothole/Damaged to to weeks
    Potholes
    Potholes all overgrown for deep pothole
    Potholes in Cavation Close
    Potholes in lamp post Out
    Potholes in right stop lines sign
    Potholes on Knothendabout
    Street Light
    Street Lighting
    Street light
    Street light fence the entranch to Parver close
    Street light not working
    Street light not working develter
    Street light out opposite 82/00 Tood
    Street lights
    Street lights not working in manham wall post
    Street lights on path
    Street lights out
    

    It also seems to do quite well at making up road names that don’t exist in any of the original reports (or in reality):

    Street Light Out - 605 Ridington Road
    Signs left on qualing Road, Leave SE2234
    4 Phiphest Park Road Hasnyleys Rd
    Apton flytipping on Willour Lane
    The road U6!
    

    Here are a few of my favourites for their sheer absurdity:

    Huge pothole signs
    Lack of rubbish
    Wheelie car
    Keep Potholes
    Mattress left on cars
    Ant flat in the middle of road
    Flytipping goon!
    Pothole on the trees
    Abandoned rubbish in lane approaching badger toward Way ockgatton trees
    Overgrown bush Is broken - life of the road.
    Poo car
    Road missing
    Missing dog fouling - under traffic lights
    

    Aside from perhaps generating realistic-looking reports for demo/development sites I don’t know if this has any practical application for FixMyStreet, but it was fun to see what kind of thing is possible with not much work.


    Help us innovate in Civic Technology
    Donate now


    Image: Scott Lynch (CC by/2.0)

  2. The big one million: celebrating FixMyStreet

    This month, FixMyStreet.com sent one more report off to a council. There was nothing to distinguish it from all the other reports of fly-tipping, potholes and graffiti… except that it was the one millionth to be sent since the site began.

    Back in 2007, when mySociety first launched FixMyStreet, we had a feeling it’d be useful — but we couldn’t have foreseen the take-up it’s had not only here in the UK, but across the world and in many forms. One million seems like a real milestone, so in celebration, here’s a whistle-stop tour of FixMyStreet’s life so far.

    First through the doors

    The first report ever sent to a council through FixMyStreet was this one, concerning a broken streetlight.

    It was created by a mySociety staff member during beta testing of the site, and sent off to Oxford City Council — who fixed the streetlight. Proof of concept, and we were off.

    Official launch

    Once it was clear that everything was working smoothly, FixMyStreet had its official launch that March.

    Those who know and love FixMyStreet may be surprised to hear that in this first incarnation, it was given the slightly less snappy title of Neighbourhood Fix-It.

    Some might suggest that names have never been mySociety’s strong point. Personally I think we got much better at that later.

    Early take-up

    Just a week after launch, users had already filed over 1,000 reports — a sign that there really was a need for this site.

    The reasons for its popularity? After all, all councils these days provide a fault-reporting system themselves, so why the enthusiastic take-up of a site that duplicates this functionality? We think the reasons are twofold:

    • You don’t have to worry about which council is responsible for an issue: FixMyStreet just automatically sends it off to the right one. There are lots of reasons why you may not know where to send a street report, not least the UK’s two-tiered system of local authorities.
    • We make the reporting process as simple as possible. It’s that whole ‘swans looking graceful but paddling like crazy under the waterline’ thing: we put in an awful amount of work to make sure that you don’t even notice the issues FixMyStreet has to deal with to make the user experience super-smooth. Back in 2012 we blogged about some of the thinking behind the site; for example here’s why FixMyStreet begins by asking just one simple question.

    Name change

    By June we’d realised that Neighbourhood Fix-It wasn’t the snappiest of names, and thus was born FixMyStreet as we know and love it.

    Early app-dopters

    In June 2008, Apple launched their app store.

    Our developers saw the future, it seems: by December that year, we’d launched a FixMyStreet app (NB, the links in that 2008 post don’t work any more: if you’d like current versions of the app, you’ll find them here for Apple and here for Android).

    The FixMyStreet apps have been downloaded more than 40,000 times, and we’re seeing a real growth in those who use it to make their reports: in the last year it accounted for 27% of reports. This reflects a general increase in the use of mobile (you can also use your mobile’s browser to access www.fixmystreet.com) — 55% of our visitors came via a phone or tablet in the last year.

    Open for re-use

    Like most mySociety software, the code that FixMyStreet runs on is Open Source: that means that anyone can pick it up for free, and run their own site on it.

    In March 2011, a group of coders in Norway were the very first to do this, with their version FiksGataMi (it means FixMyStreet in Norwegian. They could have gone for Nabolaget Fikser Det, which means Neighbourhood Fix-It, but, well, you know…).

    Since then, we’ve made real efforts to make the code easier for others to deploy, and ensured that the improvements we add to our own FixMyStreet are also available for all the others: just recently we rolled out version 2.1 of the codebase.

    Taking a peek to see what’s being reported around the world is one of our favourite, if non-standard, means of armchair travelling.

    For example:

    FMS around the world

    A Norwegian puddle-prone footbridge gets in the way of christenings, confirmations and school meetings; meanwhile in Spanish city Alcalá de Henares, a resident complains about the smell created by rubbish lorries while allowing us a splendid view across the rooftops; and in Malaysia, a pack of stray dogs is causing problems for one reporter.

    FixMyStreet Professional

    We’d wanted to provide a reporting system that bettered those offered by local councils: in June 2012 that goal was seemingly affirmed when some councils purchased the system to place on their own websites.

    We officially launched FixMyStreet for Councils, with Bromley and Barnet being the very first local authorities to implement it. Since then, we’ve been in a continual process of improvement, driven by input and collaboration with many councils around the country. Several more have become clients, too. We’ll have more news on the latest developments soon (and meanwhile, if you are from a council, you can learn more here).

    Diverse uses

    One of the nicest things about a codebase like FixMyStreet is that it can be deployed in many — sometimes surprising — ways. If you’ve followed our blog over the years, you’ll have seen the Channel 4 collaboration Empty Homes Spotter; the bicycle incident-reporting platform Collideoscope; and a project fighting corruption in Malaysia.

    Bringing out the poetry in potholes

    There’s something about FixMyStreet that inspires some users to exercise their powers of descriptive prose: we celebrated many of them in this 2014 post.

    Then there are the reports which attract comments from other users. Lots of them, year in, year out. This one about seagulls in Brighton, for example, has become a one-stop forum for people all around the country to come together in their mutual despair of and/or love for our coastal avian friends.

    Ever more reports

    stats page fms

    You can track the progress as we head towards the next million reports on our new stats page; where you might also be interested to see which councils are currently responding to issues most quickly, and what categories of problem are most-reported at any given time.

    As you can see, at the moment the site is handling around 4,000 reports a week: but you can expect that to rise when the weather gets colder — we always get a lot more pothole reports in the winter.

    And, are you wondering just what that millionth report was about? Nothing is ever simple: because some reports are made and then subsequently deleted at the user’s request, or because they contravene FixMyStreet’s house rules, we can’t just identify report number 1000000 as the millionth. Those deleted reports retain their original numbers, even though they’re not live.

    But doing a quick bit of calculation, we suspect that the rightful millionth report might be this utterly unremarkable one in Knowsley. Long live the unsensational reports that simply get things fixed.


    Help us run our citizen-empowering sites
    Donate now


    Image: Alison Benbow (CC by/2.0)

  3. Find FixMyStreet Pro on GCloud 9

    We are happy to confirm that FixMyStreet Professional (the service formerly known as FixMyStreet for Councils) has been accepted onto the GCloud9 procurement framework.

    Why is this important?

    Using GCloud9, which is overseen by the Crown Commercial Service, removes much of the admin burden from public sector teams who are seeking to procure cloud based software and makes it easier to get down to the question of who has the best product for their needs.

    What is FixMyStreet Pro?

    FixMyStreet Pro represents the outcome of our co-design project with Oxfordshire County Council to take our popular FixMyStreet platform and build in a new set of features that genuinely made it as useful as possible for their staff (and Council staff all over the UK).

    With a focus on retaining the user focused design and approach FixMyStreet was known for we have added or improved functionality for Council customer service staff and introduced a whole new set of tools to support Council inspectors including the ability to manage their tasks from within the app and to work offline when out and about.

    This project has also made some improvements to the wider user experience for citizens with new front-end features being added all the time based on user research and feedback.

    Want to learn more?

    You can find out more about the service over on the GCloud Digital Marketplace or check out our own product pages where you can also get in touch with us if you would like to see a demonstration of the service or learn more about how we might be able to help.

  4. What I learned from 20,000 dog poops

    When working with data that you didn’t set out to gather you have to be careful to think about what the data actually means, rather than what it seems to be saying. As an example, one of the “interesting” side effects of FixMyStreet is a database of places people have reported dog poop (or “dog fouling” as it tends to be called academically). We now have over 20,000 locations across the UK where nature’s call has both been heard, and reported.

    My first thought when learning about this data was “that’s a lot of dog poop!” but it turns out 20,000 dog poops is not a lot of dog poop at all. There are an estimated 8.5 million dogs in the UK, assuming (on average) each one poops once a day, they’ll produce over 3.1 billion poops a year.

    So actually, 20,000 poops over nine years is nothing compared to the amount of pooping going on. But just because our data is a drop in the bucket doesn’t mean we can’t learn interesting things from it. The first question to ask is if we have a representative sample of where all this dog fouling is going on. The answer, sadly, is no. But the reasons for that answer raise further questions – which is interesting!

    When you map the location of dog poo complaints in England against the Index of Multiple Deprivation [1], you get this:

    FixMyStreet Dog Fouling Reports

    This tells us that reports about dog fouling are roughly parabolic – there are more in areas in the middle than those that are either very deprived or very not.

    This is interesting because when Keep Britain Tidy actually went out into the world and checked (p. 14), they found this:

    LEQSE Dog Fouling

    This graph tells a very different story, where dog fouling gets worse the more deprived the area. But why is this? And why doesn’t our data tell the same story?

    One reason we would expect more dog poop in the most deprived areas is that the most deprived areas are more urban. Taking the same IMD deciles and using the ONS’s RUC categories to apply a eight point ‘ruralness’ scale (where 1 is ‘Urban major conurbation’ and 8 is ‘Rural village and dispersed in a sparse setting’) lets us see the average ‘ruralness’ of each decile. While this reflects that deprivation is spread across urban and rural areas – the most deprived areas tend to be more urban.

    Ruralness vs IMD Decile

    As urban areas have fewer natural places to dispose of dog waste, and the most deprived areas are more urban, we would expect the most deprived areas to have more dog fouling.[2] We also know that measures that contribute to IMD scores (such as crime levels) are related to trust and social cohesion in an area.[3] When social cohesion is lower, we would expect more dog fouling because owners feel less surveyed and are less concerned with the opinion of neighbours. The real world increase reported by the Keep Britain Tidy survey supports these relationships.

    The drop off in our reported data compared to the real world can be explained by features of the general model for understanding FixMyStreet reports — some measures of deprivation are correlated with increased reports (because they relate to more problems) and others with decreased reports (because they hurt the ability or inclination of people to report). We would also expect areas with worse deprivation to have fewer reports because of disengagement with civic structures.

    Quickly checking the English dog fouling data (so only 17,103 dog poops) against the same model confirms that significant relationships exist for the same deprivation indexes as the global dataset with the largest effect size of a measure of deprivation being for health – as health deprivation in an area goes up, reports of dog fouling increase.

    What this tells us is that our dog data (and probably our data more generally) is clipped in areas of the highest deprivation. We’re not getting as many reports as the physical survey would suggest and so our data has very real limits in identifying the areas worse affected by a problem.

    This is a lesson in being careful about interpreting datasets you pick up off the ground – if you used this data to conclude the most deprived areas had a similar dog poop problem to the least deprived areas you would be wrong. Because we have an independent source of the real world rate of problems, we can see there is a mismatch between distribution in reports and reality. Using this independent data of ‘actual problems’ for one of our categories makes us more aware that there is negative pressure on reports in highly deprived areas.


    If you’d like to learn more about the history of dealing with dog poo on the street (and who wouldn’t want to learn more about that!) – I’ve very generously gone into more detail here.

    [1]: An index that combines thirty-seven indicators from seven domains (income, health, crime, etc) to provide a single figure for an area that is indicative of its level of deprivation relative to other areas.

    [2]:This is relative. Rural areas still have problems with bagged dog poo (“the ghastly dog poo bauble” hanging from branches – as MP Anne Main put it). There is also a risk to the health of cows from dog fouling in farmland – so there are unique rural dog poo problems.

    [3]: Ross et al. found “People who report living in neighborhoods with high levels of crime, vandalism, graffiti, danger, noise, and drugs are more mistrusting. The sense of powerlessness, which is common in such neighborhoods, amplifies the effect of neighborhood disorder on mistrust.”

    Header image: https://www.flickr.com/photos/scottlowe/3931408440/

  5. Happy birthday FixMyStreet

    On Friday the 2nd of February, 2007, the very first public report was sent through FixMyStreet. It concerned a broken light on a canal footbridge in Oxford.

    It’s a little-known fact that FixMyStreet was originally called Neighbourhood Fix-It. Launching the site was a good idea, but changing that name may be the next best thing we ever did.

    Ten years on, the site has processed over 900,000 reports, sending them to every local authority in the UK. In doing so, it helps citizens take an active part in keeping their own local communities clean, safe and functional. Meanwhile it ensures that you, the user, never have to give a second thought to which council needs to receive which type of report.

    But it’s not just a local success: FixMyStreet’s codebase has also been used to set up similar sites in more than 20 countries worldwide, from the Maldives to Malaysia and beyond.

    It’s been adopted as several councils’ primary fault-reporting interface on their own websites, from Bristol to Oxfordshire and even Zürich, and we’ve worked in partnership with these authorities to develop new features that make it as useful and simple to use as possible. Watch this space, as we’ll be talking a lot more about these soon.

    FixMyStreet continues to surprise even us. Thanks to its remarkable flexibility, the codebase has also been used to underpin a number of other projects, including Collideoscope, where you can report cycling collisions and near misses, and the Channel 4 tie-in, the Empty Homes Spotter. We know there will be many more to come.

    So, here’s to FixMyStreet. At heart, it’s a little site that matches a pin on a map with the body that’s responsible for that location. But when you consider what it’s achieved — getting communities fixed up, making council reporting interfaces more user-friendly, empowering people to take their first steps into local participation, even challenging corruption — well, we hope you’ll see why we’re proud of how far FixMyStreet has come.


    Image: S. (CC by-sa/2.0)

  6. Multi-selectin’ fun on FixMyStreet

    You might already be enjoying one of the usability improvements that FixMyStreet version 2.0 has brought, though it’s possible that you haven’t given it much thought.

    multi-selectIn these days of eBay and department store shopping, we’re all quite used to refining results through the use of multiple checkboxes.

    But for FixMyStreet, we hadn’t given much thought to letting you filter reports by more than one dimension, until Oxfordshire County Council suggested that it would be a useful feature.

    For quite some time, you’d been able to filter by category and status (“Show me all pothole reports” or “Show me all ‘unfixed’ reports”), but this new functionality is more flexible.

    You can now select multiple categories and multiple statuses simultaneously (“show me all pothole and graffiti reports that are unfixed or in progress”) — and all through the power of tickboxes.

    If you’re a non-technical person, that’s all you need to know: just enjoy the additional flexibility next time you visit FixMyStreet. But if you are a coder, you might like to read more about how we achieved this feature: for you, Matthew has written about it over on the FixMyStreet Platform blog.

  7. Better-looking emails for FixMyStreet

    If you’ve used FixMyStreet recently — either to make a report, or as a member of a council who receives the reports — you might have noticed that the site’s automated emails are looking a lot more swish.

    Where previously those emails were plain text, we’ve now upgraded to HTML, with all the design possibilities that this implies.

    It’s all part of the improvements ushered in by FixMyStreet Version 2.0, which we listed, in full, in our recent blog post. If you’d like a little more technical detail about some of the thought and solutions that went into this switch to HTML, Matthew has obliged with in a blog post over on FixMyStreet.org.

  8. FixMyStreet: Why do some areas report more than others?

    I’m just a few weeks into my position of Research Associate at mySociety and one of the things I’m really enjoying is the really, really interesting datasets I get to play with.

    Take FixMyStreet, the site that allows you to report street issues anywhere in the UK. Councils themselves will only hold data for the issues reported within their own boundaries, but FixMyStreet covers all local authorities, so we’ve ended up with probably the most comprehensive database in the country. We have 20,000 reports about dog poop alone.

    Now if you’re me, what to do with all that data? Obviously, you’d want to do something with the dog poop data. But you’d try something a bit more worthy first: that way people won’t ask too many questions about your fascination there. Misdirection.

    How does it compare?

    So, starting with worthy uses for that massive pile of data, I’ve tried to see how the number of reports in an area compares against other statistics we know about the UK. Grouping reports into ONS-defined areas of around 1,500 people, we can match the number of reports within an area each year against other datasets.

    To start with I’m just looking at English data (Scotland, Wales and Northern Ireland have slightly different sets of official statistics that can’t be combined) for the years 2011-2015. I used population density information, how many companies registered in the area, if there’s a railway station, OFCOM stats on broadband and mobile-internet speeds, and components from the indices of multiple deprivation (various measures of how ‘deprived’ an area is, such as poor health, poor education prospects, poor air quality, etc) to try and build a model that predicts how many reports an area will get.

    The good news: statistically we can definitely say that some of those things have an effect! Some measures of deprivation make reports go up, others make it go down. Broadband and mobile access makes them go up! Population density and health deprivation makes them go down.

    The bad news: my model only explains 10% of the actual reports we received, and most of this isn’t explained by the social factors above but aspects of the platform itself. Just telling the model that the platform has got more successful over time, which councils use FixMyStreet for Councils for their official reporting platform (and so gather more reports) and where our most active users are (who submit a disproportionate amount of the total reports) accounts for 7-8% of what the model explains.

    What that means is that most reasons people are and aren’t making reports is unexplained by those factors. So for the moment this model is useful for building a theory, but is far from a comprehensive account of why people report problems.

    Here’s my rough model for understanding what drives areas to submit a significantly higher number of reports to FixMyStreet:

    • An area must have a problem

    Measures of deprivation like the ‘wider barriers to housing deprivation’ metric (this includes indicators on overcrowding and homelessness) as well as crime are associated with an increase in the number of reports. The more problems there are, the more likely a report is — so deprivation indicators we’d imagine would go alongside other problems are a good proxy for this.

    • A citizen must be willing or able to report the problem

    Areas with worse levels of health deprivation and adult skills deprivation are correlated with lower levels of reports. These indicators might suggest citizens less able to engage with official structures, hence fewer reports in these areas.

    People also need to be aware of a problem. The number of companies in an area, or the presence of a railway station both increase the number of reports. I use these as a proxy for foot-traffic – where more people might encounter a problem and report it.

    Population density is correlated with decreased reports which might suggest a “someone else’s problem” effect – a slightly decreased willingness to report in built-up areas where you think someone else might well make a report.

    • A citizen must be able to use the website

    As an online platform, FixMyStreet requires people to have access to the website before they can make a report. The less friction in this experience makes it more likely a report will be made.

    This is consistent with the fact that an increased number of slow and fast home broadband connections (and fast more than slow ones) increases reports. This is also consistent with the fact that increased 3G signal in premises is correlated with increased requests.

    Reporting problems on mobile will sometimes be easier than turning on the computer, and we’d expect areas where people more habitually use mobiles for internet access to have a higher number of reports than broadband access alone would suggest. If it’s slightly easier, we’d expect slightly more – which is what this weak correlation suggests.

    Other factors

    Not all variables my model includes are significant or fit neatly into this model. These are likely working as proxy indicators for currently unaccounted for, but related factors.

    I struggle, for instance, to come up with a good theory why measures of education deprivation for young people are associated with an increase in reports. I looked to see if there was a connection between an area having a school and having more reports on the basis of foot-traffic and parents feeling protective over an area – but I didn’t find an effect for schools like I did for registered companies.

    So at the moment, these results are a mix of “a-hah, that makes sense” and “hmm, that doesn’t”. But given that we started with a dataset of people reporting dog poop, that’s not a terrible ratio at this point. Expanding the analysis into Scotland and Wales, analysing larger areas, or focusing on specific categories of reports might produce models that explain a bit more about what’s going on when people report what’s going wrong.

    I’ll let you know how that goes.

    Image: Dave_S (CC-by/2.0)

  9. Something in the middle: how Bristol connects

    This year, Bristol Council did something unusual and admirable. As far as we’re aware, they’re the first UK council to have taken such a step.

    Working with mySociety on custom Open311 ‘middleware’ while adopting FixMyStreet as their fault-reporting system, they now enjoy full flexibility, no matter what the future holds.

    Thanks to this open approach, Bristol will extract more value from their existing systems and lower operating costs. With integrated, open solutions, and the raised quality of report formatting that Open311 brings, everyone will benefit.

    Improving flexibility

    Councils are increasingly understanding the value of flexibility when it comes to service providers.

    Contracts that lock them into a single provider for many years mean that, often, there’s no opportunity to benefit when technology advances, and disproportionate costs can be charged for implementing the slightest changes.

    This desire for flexibility was a strong factor in Bristol City Council’s decision to adopt FixMyStreet for Councils — and that opened the door for a conversation about Open311.

    We’ve always advocated integration via Open311, to the extent that we offer free hook-up with FixMyStreet to any councils who support it.

    Because Open311 is an open standard, it supports the entire landscape of providers like FixMyStreet. Right now, Bristol can accept street fault reports not just from us, but from a full range of services — in other words, any site or app that cares to connect with them can do so. No-one knows what the future will hold: if a game-changing system emerges in the future, it makes sense that you’d be able to accept its reports.

    All well and good: but when Bristol City Council implemented FixMyStreet as their fault-reporting system, the concept was taken a little bit further. With our collaboration, Bristol created their own Open311 ‘middleware’, sitting between the two systems and talking to both.

    Via this method, their existing CMS, Confirm, can hook up to reports coming through from FixMyStreet. That all works smoothly — but, just as importantly, if Bristol ever decide to replace their CRM provider, they’ll be able to do so with no knock-on effect to FixMyStreet reports. And if they ever decide to replace FixMyStreet with a different provider, or indeed to accept reports from a range of providers, they can do that too.

    Bristol found us via the GCloud procurement system, and are the first metropolitan unitary authority to install FixMyStreet.

    Future plans

    Bristol launched its FixMyStreet service to the public in the summer of 2016.

    This autumn, they added asset-based reporting, meaning that known council properties such as streetlights, grit bins and gullies are all marked on FixMyStreet’s maps. Residents can pinpoint and report the location of faults with these assets far more accurately as a result.

    There’ll be a phased rollout across departments, starting with Highways and moving across departments as Bristol extend their own middleware. We’ll be watching with great interest.

    Find out more about FixMyStreet for Councils.

    Image: Adam Heath (CC by-sa/2.0)

  10. Catching up with Collideoscope

    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.

    Image by Rob. A road sign showing a cyclist being thrown off his bike because of an uneven road surfaceThe 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.

    Data quantity

    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.

    Changes afoot

    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.


    Images:
    This hill is dangerous by John Kennedy (CC by-nc/2.0)
    Falling off bike sign by Rob (CC by-nc-sa/2.0)