Every road user relies on signs, so keeping them tip-top is in everyone’s interest. Now Transport Focus have launched their Sort My Sign campaign, asking road users to help them do just that.
They’d like everyone to report any signs they spot that are dangerous, dirty, broken, or obscured.
To support this programme digitally, Transport Focus came to mySociety, asking if we could help create a simple and intuitive mapping interface where these issues could be reported.
Keep your eyes on the road
Specifically, the scheme covers signs on roads managed by Highways England, which means motorways and some A roads.
FixMyStreet was the obvious starting point — we already have a data layer for these roads, which means that your everyday FixMyStreet reports can be routed to Highways England rather than the council if they are the responsible body.
Plus, as we’ve detailed many times before, the FixMyStreet platform can be repurposed for any project dealing with location-based reports, and has in the past been put to all sorts of uses, from reporting empty homes to helping fight corruption.
Nonetheless, we perceived one potential challenge when it came to setting up sign reporting.
Don’t report and drive!
FixMyStreet is generally well-suited for people making reports on the go — in fact, thanks to the ‘use my location’ functionality, it is ideal for reporting issues like potholes or broken pavements on your mobile while out on a walk. But obviously, road signs are a slightly different matter. If you are driving, you certainly mustn’t be fiddling with your mobile phone, so ‘use current location’ is only helpful if you have an amenable passenger to make the report.
That’s fine — you can always make the report later of course: but that means you’ll need to know roughly where you were when you saw the sign, something that’s a bit trickier on a long drive than it might be on a stroll around your neighbourhood. FixMyStreet allows you to find any UK location with the input of a postcode or street name, but these are details you’re unlikely to have to hand if you have simply driven through.
After some thought we realised that, on a motorway, the location identifier most people will find easiest to recall will probably be the junction number.
So that set us a challenge: how could we best enable ‘search by junction number’?
Sign here…and here
Ideally, we wanted a user to be able to visit the Sort My Sign site and enter the name of a junction, just as they’d enter a postcode or street on the FixMyStreet homepage — and then to be taken to a map centred on that point.
But sourcing a mapping between motorway/junction number and co-ordinates proved surprisingly tricky. mySociety developer Matthew takes over the story.
“I first looked at OpenStreetMap data — its geocoder, Nominatim, worked really well for some junction numbers, but didn’t work at all for others. If a junction has been assigned a name (like J23 on the M6, which is known as ‘Haydock’) it can only be looked up by that name, not by number. But we wanted users to be able to look up junctions by number.
“I could also export all the junction data from OpenStreetMap, but the junction nodes alone aren’t linked to the motorway, so that looked like it would prove tricky to match up.”
FOI to the rescue
“But by a stroke of luck, I then discovered that someone had used another of mySociety’s services, our Freedom of Information site WhatDoTheyKnow, to make a request to Highways England asking for the positions of all the driver location signs (the repeaters every 100m or 500m along the motorways giving the name and distance from start).
“In response, Highways England had provided that information, so I knew I could use that to at least provide a mapping between location sign and geographic co-ordinates.
“Each sign also had information about what junction it was nearest or between, so by constructing an average of all the location sign co-ordinates associated with a particular junction, I came up with a pretty good estimate for the location of the junction itself.
“I added all the sign and junction data into a small SQLite database (which means it’s portable and doesn’t need to be associated with the main database) and wrote a little bit of code to spot when someone entered a junction name in any of a variety of different formats, then look up the matching location in this database”.
Signed, sealed, delivered
To test this out, Matthew had all his colleagues name their favourite junction… perhaps not to be recommended as a party game, but it did at least prove that his code had cracked the problem.
Something much appreciated by Head of Strategy at Transport Focus, Guy Dangerfield, who says, “mySociety has been excellent in understanding what we needed and finding ways to achieve our objectives.”
You can give the new system a go here — and perhaps bookmark the site so that you know where to report a sign next time you see one that needs fixing.
Once you’re safely off the road, that is.
If you’re reporting an issue on Buckinghamshire Council’s FixMyStreet installation, you might have seen yellow dots appearing on the map. These represent items such as streetlights, bins or drains, and we blogged about it when we first added the feature.
When it comes to assets like streetlights, it can save the council considerable time and effort if your report tells them precisely which light needs fixing: it’s far quicker to find an identified light than it is to follow well-meaning but perhaps vague descriptions like ‘opposite the school’!
But even when the assets are marked on a map, it’s not always easy for a user to identify exactly which one they want to report, especially if they’ve gone home to make the report and they’re no longer standing right in front of it.
After the system had been in place for a few weeks, the team at Buckinghamshire told us that users often weren’t pinpointing quite the right streetlight. So we thought a bit more about what could be done to encourage more accurate reports.
As you might have noticed, streetlights are usually branded with an ID number, like this:Buckinghamshire, as you’d expect, holds these ID numbers as data, which means that we were able to add it to FixMyStreet. Now when you click on one of the dots, you’ll see the number displayed, like this:
The same functionality works for signs, Belisha beacons, bollards and traffic signals, as well as streetlights. Each of them has their own unique identifier.
So, if you’re in Bucks and you want to make a report about any of these things, note down the ID number and compare it when you click on the asset. This means the correct information is sent through the first time — which, in turn, makes for a quicker fix. Win/win!
This type of functionality is available to any council using FixMyStreet Pro: find out more here.
Header image: Luca Florio
With funding from the Consumer Data Research Centre (CDRC) we’ve been working with researchers from the University of Sheffield and University of Stirling to open up FixMyStreet data for researchers.
For an example of the kind of thing that can be done with this data, this group have produced maps for every local authority in the UK, mapping FixMyStreet reports against indices of deprivation (a few examples: Sheffield, Harrogate and Cardiff). These can be explored on our mini-site, where for each authority you can also download a printable poster with additional statistics.
If you’d like to know more about what these maps mean and what we learned from the process, there’s a report exploring what we learned here.
Research Mailing List
Sign up to our mailing list to hear about future research.
It’s something we’ve been wanting for a long time, and it’ll very soon be a reality: FixMyStreet reports will, where appropriate, be channeled to Highways England. Look out for this functionality in the coming week.
My way or the highway
Previously, if you reported a problem on one of the country’s motorways or major A roads, we had no way of identifying whether it was the responsibility of the government department rather than the council. We had to rely on whichever council the report fell within, and hope that they would forward it on.
But now, we can send reports off to just the right authority. What’s changed to make this improvement possible?
Well, FixMyStreet uses our MapIt software, which matches points (in this case, the pin you put in the map when you make a report) with the boundaries they fall within (mainly, until now, council boundaries). That’s how it knows which council to send your issue to, even if you have no idea yourself when you make the report.
Motorways and A roads have boundaries too, of course, but that data wasn’t previously available under an open licence that would allow us to use it on the site. That all changed with GOV.UK’s release of the Highways England Pavement Management System Network Layer — just what we needed!
So now, if you make a report that falls within a small distance from one of the relevant roads, FixMyStreet will use MapIt in combination with this data layer. You’ll see a message asking for confirmation that your report actually does pertain to the highway: where roads cross a motorway, for example, a pin could relate to the road on a bridge, or the motorway below.
Confirm either way and boom: off it goes to either Highways England or to the council, as appropriate.
So that’s a big thumbs up for open data: thanks, GOV.UK! It’s also a good example of how our commercial work, providing FixMyStreet Pro to councils as their default street reporting system, has a knock-on benefit across the open source FixMyStreet codebase that runs not only FixMyStreet.com, but sites run by other folk around the world.
As you may remember, we recently added red routes to Bromley for FixMyStreet Pro, and it was this bit of coding that paved the way for the highways work. We can only prioritise not-for-profit development if we have the funding for it; but being able to improve FixMyStreet for everyone on the back of work done for commercial clients is a win for everyone.
Or, as our developer Struan says, in a metaphor perhaps better suited to shipping routes than highways, “a rising tide raises all boats”.
Image: Alex Kalinin
Our most recent improvement to FixMyStreet means that users in Bromley will experience some clever routing on their reports.
It’s something quite a few FixMyStreet users have requested, telling us that they’d reported a street issue in London, only to have a response from their authority to say that it was located on a ‘red route‘ — roads which are the responsibility of TfL rather than the council.
Of course, most councils have systems set up so that they can easily forward these misdirected reports to the right place, but all the same, it wasn’t ideal, and added another step into a reporting process we’ve always tried to keep as simple and quick as possible.
Thanks to some development for Bromley council, we’re now glad to say that within that borough, reports on red routes will automatically be forwarded to TfL, while other reports will be sent, as usual, to the relevant council department.
As a user, you don’t have to do a thing (although you can see this automated wizardry in action by watching changes in the text telling you where the report will be sent, as you click on the map in different places and select a different category – give it a go!).
Note that this functionality has not yet been extended to the FixMyStreet app; however in the meantime it will work if you visit fixmystreet.com via your mobile browser.
A new layer
As you’ll know if you’re a frequent FixMyStreet user, the site has always directed reports to the right UK council, based on the boundaries within which the pin is placed.
And equally, even within the same area it can discern that different categories of report (say, streetlights as opposed to parking) should be sent to whichever authority is responsible for them: that’s an essential in a country like the UK with its system of two-tier councils.
So this new innovation just meant adding in a map layer which gives the boundaries of the relevant roads that are designated red routes, then putting in extra code that saw anything within the roads’ boundaries as a new area, and TfL as the authority associated with road maintenance categories within that area.
FixMyStreet has always been flexible in this regard: you can swap map layers in or out as needed, leading to all sorts of possibilities. Yesterday, we showed how this approach has also averted one common time-waster for councils, and the same set-up is behind the display of council assets such as trees and streetlights that you’ll see for some areas on FixMyStreet.
The integration of red routes is available for any London Borough, so if you’re from a council that would like to add it in, get in touch. And to see all the new innovations we’re working on to make FixMyStreet Pro the most useful street reporting system it can be, check out the website.
Image: Marc-Olivier Jodoin
We, and Open Knowledge International, are looking for the digital files that hold electoral boundaries, for every country in the world — and you can help.
Yeah, we know — never let it be said we don’t know how to party.
But seriously, there’s a very good reason for this request. When people make online tools to help citizens contact their local politicians, they need to be able to match users to the right representatives.
So head on over to the Every Boundary survey and see how you can help — or read on for a bit more detail.
Data for tools that empower citizens
If you’ve used mySociety’s sites TheyWorkForYou — or any of the other parliamentary monitoring sites we’ve helped others to run around the world — you’ll have seen this matching in action. Electoral boundary data is also integral in campaigning and political accountability, from Surfers against Sewage’s ‘Plastic Free Parliament’ campaign, to Call your Rep in the US.
These sites all work on the precept that while people may not know the names of all their representatives at every level — well, do you? — people do tend to know their own postcode or equivalent. Since postcodes fall within boundaries, once both those pieces of information are known, it’s simple to present the user with their correct constituency or representative.
So the boundaries of electoral districts are an essential piece of the data needed for such online tools. As part of mySociety’s commitment to the Democratic Commons project, we’d like to be able to provide a single place where anyone planning to run a politician-contacting site can find these boundary files easily.
And here’s why we need you
Electoral boundaries are the lines that demarcate where constituencies begin and end. In the old days, they’d have been painstakingly plotted on a paper map, possibly accessible to the common citizen only by appointment.
These days, they tend to be available as digital files, available via the web. Big step forward, right?
But, as with every other type of political data, the story is not quite so simple.
There’s a great variety of organisations responsible for maintaining electoral boundary files across different countries, and as a result, there’s little standardisation in where and how they are published.
How you can help
We need the boundary files for 231 countries (or as we more accurately — but less intuitively — refer to them, ‘places’), and for each place we need the boundaries for constituencies at national, regional and city levels. So there’s plenty to collect.
As we so often realise when running this sort of project, it’s far easier for many people to find a few files each than it would be for our small team to try to track them all down. And that, of course, is where you come in.
Whether you’ve got knowledge of your own country’s boundary files and where to find them online, or you’re willing to spend a bit of time searching around, we’d be so grateful for your help.
Fortunately, there’s a tool we can use to help collect these files — and we didn’t even have to make it ourselves! The Open Data Survey, first created by Open Knowledge International to assess and display just how much governmental information around the world is freely available as open data, has gone on to aid many projects as they collect data for their own campaigns and research.
Now we’ve used this same tool to provide a place where you can let us know where to find that electoral boundary data we need.
Where to begin
Thanks for your help — it will go on to improve citizen empowerment and politician accountability throughout the world. And that is not something everyone can say they’ve done.
Image credit: Sam Poullain
When you consider that FixMyStreet has been running for over a decade, it’s not really surprising that the maps in some areas are a little over-crowded with pins.
That can be a problem for anyone trying to make a new report — even when you zoom right in, we were beginning to find that in some very congested areas, it was difficult to place a new pin without clicking on an existing one.
We’ve tried to remedy this in various ways in the past. For a while we only displayed newer reports by default, a decision which we discarded when we brought in pagination, allowing users to click through batches of reports rather than seeing them all in one long list on a single page.
For some time now we’ve also provided the option to hide the pins completely, via this button both on the desktop and app versions:
And there’s also a ‘hide pins’ option at the foot of the map:
But even so, arriving at a map absolutely covered in pins and having to look around for that button doesn’t exactly seem like a nice, smooth user journey, so we’ve revisited the matter.
Why not just delete the old reports?
We’ve always had a policy of keeping every report live on FixMyStreet (unless it’s reported to us as abusive, or its maker contacts us to ask us to remove it — and even in this latter case we’d prefer to retain the content of the report while anonymising it).
This is because the reports made to councils build up to create an invaluable archive of the issues that various regions of the country face, through time.
The historic collection of reports allows planners to understand recurring or seasonal problems; and researchers use this data as well, to get insights into all sorts of issues. For examples, see Réka Solymosi’s presentation at TICTeC on using FixMyStreet data to understand what counts as ‘disorder’ in the environment, or mySociety’s own research on why some areas of the country report on FixMyStreet more than others.
And so here’s what we’ve done
- When you visit a map page on the main FixMyStreet site, by default, you’ll again only see reports that are less than six months old, and that are still open.
A report remains ‘open’ until the council marks it as ‘closed’, or a user or the council marks it as ‘fixed’. ‘Closed’ means that the council doesn’t intend to do further work on the issue, which can be for reasons such as the issue not falling within their responsibilities or because it is part of their regular maintenance schedule and will be seen to in time.
- You can still opt to see closed and fixed reports by selecting from the dropdown at the top of the list:
- And you can also still see reports older than six months by clicking the checkbox:
- The two filters work together, giving you the options of displaying:
- Open reports less than six months old (the default)
- Open reports of any age
- All reports less than six months old
- All reports of any age
- Any combination of open/closed/fixed reports less than six months old
- Any combination of open/closed/fixed reports of any age
To keep things simpler for app users, the display there is set to only show newer, open reports, so if you want the full range of options, you’ll need to switch to viewing the site on a desktop.
Additionally, reports that have been closed for six months without any update being made will now no longer allow updates. If you need to update an issue that falls into this category, we recommend starting a new report (possibly linking to the old one for reference if it provides useful information for the council).
But you might not see this everywhere
Some councils use FixMyStreet Pro as their own fault-reporting software. These councils can opt whether or not to adopt these defaults, so your experience may be slightly different when visiting FixMyStreet via your local council’s own site.
We think that we’ve arrived at a more intuitive solution than those we tried before — and we hope that these options will suit everyone, whether you’re a user in a hurry coming to make a quick report, or someone who’d like to see a more in-depth history of the area. Give it a go, and then let us know your thoughts.
So we’re pleased to announce the (quiet) beta launch of our latest little site, Keep It In The Community, which we hope will become an England-wide register of Assets of Community Value (ACVs).
The Localism Act 2011 was introduced with a great hope. Its provision for giving groups the right to bid on buildings or land that contribute to community life would allow the protection these assets, potentially taking them into direct community control should they come up for sale.
Sadly, as currently implemented, the law hasn’t yet delivered on that promise.
In Scotland, the legislation comes with an actual right to buy, but in England, that’s not the case, and with developers finding ways around the legislation more often than not, often the best the Act can bring about is the delay of an inevitable change of control. For the moment we’re not expecting the legislation to be given any more teeth.
With Keep It In The Community we intend to at least help support a greater takeup of registration by local communities.
In yet another project built on the flexible FixMyStreet Platform, Keep It In The Community has three main roles:
1. We’re gathering together existing asset listings from the 300+ English councils who hold them, to provide a single synchronised and complete record of all listed and nominated ACVs.
2. We’re providing a straightforward route for established community groups to nominate new ACVs in their community.
3. We’ll allow community members to provide more details, photographs, and useful anecdotes about each registered asset, beyond that required by the legal listing process.
Plans for the summer
So far we have data from around 20 local authorities on the live service, with another 50 or so due to be added over the next few weeks. The remaining councils will be added over the summer. All the data is drawn directly from each local authority and as new assets are nominated or their status changes we’ll update their status on Keep It In The Community.
Whilst we complete final testing we’re restricting the ability of community groups to nominate assets, but hope to fully switch that on shortly, once more of the existing assets are displayed on the site.
The initial process for connecting each council listing is fairly low tech, relying on the scraping of a commonly formatted spreadsheet hosted on each council website.
So for the moment. there will still be a fair amount of manual tweaking to keep things in sync. This is one of those important elements that will be fine to manage when the service is starting out, but may start to creak further down the line if it becomes well used – a classic ‘known known’ issue we’ll need to keep on top of.
Over the summer we’ll be working with a representative set of community groups to extend the features of Keep It In The Community to improve how to submit assets for nomination, and how best to celebrate the listed assets by adding all sorts of local detail and background.
Have a look and let us know what you think so far.
In addition to the initial grant from Power To Change, this project has been implemented with the support of the Plunkett Foundation and the Ministry of Housing, Communities and Local Government.
In 2014, along with Integrated Transport Planning (ITP), we created Collideoscope — a service based on our FixMyStreet Platform to map collisions and near misses between motor vehicles and cyclists.
Since the launch of Collideoscope, cycling has seen even more of an increase in popularity, and we suspect that there have been numerous new initiatives and campaigns developed to highlight and tackle the dangers faced by cyclists through insufficient provision of safe cycling infrastructure and dangerous driving.
So a recent approach from the Merseyside Road Safety Partnership (MRSP) was of great interest: they wanted to explore how we might revisit this task and determine if Collideoscope still has a role to play — or whether some other approach might be more beneficial.
Over the next three months, with the help of funding from MRSP, we plan to carry out a fresh discovery exercise to identify up to date user needs around collision prevention, and also determine how well served these issues are already by other similar initiatives around the country.
In addition to speaking to cyclists, campaign groups and safety experts, we’ll also be working with MRSP and in particular the Cycling Safety team within Merseyside Police to better understand how submission of reports can actually contribute to the development of actionable policy.
We’d also like to better understand the process of evidence submission, especially video evidence, in cases of near misses and collisions, and improve how that might lead to appropriate enforcement action.
For the moment we’re approaching all of this with a very open mind. We’re not going to assume that Collideoscope as it currently exists is necessarily the correct approach, and even if it does have a role to play we suspect it may need to be substantially altered to cater to any newly identified user needs.
Whilst this exploratory part of the project is going to be centred on Merseyside, we’re keen to hear from groups across the country and if you’d like to be consulted or participate in the research we would be keen to hear from you.
In the meantime, ride safe and we’ll update with progress reports over the next few weeks.
If you visit FixMyStreet and suddenly start seeing spots, don’t rush to your optician: it’s just another feature to help you, and the council, when you make a report.
In our last two blog posts we announced Buckinghamshire and Bath & NE Somerset councils’ adoption of FixMyStreet Pro, and looked at how this integrated with existing council software. It’s the latter which has brought on this sudden rash.
At the moment, you’ll only see such dots in areas where the council has adopted FixMyStreet Pro, and gone for the ‘asset locations’ option: take a look at the Bath & NE Somerset installation to see them in action.
What is an asset?
mySociety developer Struan explains all.
Councils refer to ‘assets’; in layman’s language these are things like roads, streetlights, grit bins, dog poo bins and trees. These assets are normally stored in an asset management system that tracks problems, and once hooked up, FixMyStreet Pro can deposit users’ reports directly into that system.
Most asset management systems will have an entry for each asset and probably some location data for them too. This means that we can plot them on a map, and we can also include details about the asset.
When you make a report, for example a broken streetlight, you’ll be able to quickly and easily specify that precise light on the map, making things a faster for you. And there’s no need for the average citizen to ever know this, but we can then include the council’s internal ID for the streetlight in the report, which then also speeds things up for the council.
So, how do we get these assets on to the map? Here’s the technical part:
The council will either have a map server with a set of asset layers on it that we can use, or they’ll provide us with files containing details of the assets and we’ll host them on our own map server.
The map server then lets you ask for all the streetlights in an area and sends back some XML with a location for each streetlight and any associated data, such as the lamppost number. Each collection of objects is called a layer, mostly because that’s how mapping software uses them. It has a layer for the map and then adds any other features on top of this in layers.
Will these dots clutter up the map for users who are trying to make a report about something else?
Not at all.
With a bit of configuration in FixMyStreet, we associate report categories with asset layers so we only show the assets on the map when the relevant category is selected.
We can also snap problem reports to any nearby asset which is handy for things like street lights as it doesn’t make sense to send a report about a broken street light with no associated light.
Watch this space
And what’s coming up?
We’re working to add data from roadworks.org, so that when a user clicks on a road we’ll be able to tell them if roadworks are happening in the near future, which might have a bearing on whether they want to report the problem — for example there’s no point in reporting a pothole if the whole road is due to be resurfaced the next week.
Then we’ll also be looking at roads overseen by TfL. The issue with these is that while they are always within a council area, the council doesn’t have the responsibility of maintaining them, so we want to change where the report is going rather than just adding in more data. There’s also the added complication of things like “what if the issue is being reported on a council-maintained bridge that goes over a TFL road”.
There’s always something to keep the FixMyStreet developers busy… we’ll make sure we keep you updated as these new innovations are added.
From a council and interested in knowing more? Visit the FixMyStreet Pro website