CycleStreets makes heavy use, as many people will know, of OpenStreetMap data as the basis of our street/path network for route planning. For us, the ability of the community of cyclists and others to contribute to this data is an important part of the effectiveness of CycleStreets.
But, lesser-known, is that we also make use of several OS OpenData datasets for various parts of the site.
OS OpenData is part of the many datasets offered by the Ordnance Survey. But unlike many commercial datasets, they are open data, allowing not-for-profit groups like ourselves to use them. The first release of OS OpenData was announced on 1st April 2010, a decision by the government and the OS that has been widely welcomed.
We thought we'd outline the datasets we use in various ways.
Firstly, the postcode database, Code-Point Open®. This enables us to translate postcodes to a point on the map. We were the first users of this open data – implementing the postcodes within hours of it being released. MySociety have helpfully converted the Code-Point Open dataset into latitude/longitudes rather than grid co-ordinates.(Code-Point Open is not to be confused with the Postcode Address File (PAF), which is a commercial product of Royal Mail, and which we do not have funds to purchase. The PAF enables individual house/address locations to be accurately located.)
Secondly, we use the Boundary-Line™ dataset to enable photos added to the Photomap to be assigned automatically to London boroughs and soon other boundaries around the UK. This dataset will also come in useful soon for our Cycle campaigner toolkit project.
Next, the OS Street View® dataset is being used by some OpenStreetMap volunteers to augment areas of OSM in the UK whose level of completion of street coverage is lacking.
Lastly, we're using a projection of the Street View dataset in our Android app and forthcoming mobile web site.
The OS OpenData datasets have enabled us to improve the facilities on CycleStreets. The postcode data in particular has been invaluable. It has helped us as a community organisation create a useful facility at low cost.
Update, Sunday 31st July: The Street View tileset is also now available as an option on the main site – just click on the blue (+) button in the top-right corner of the map panel:
PS Steven Feldman: here's one for you: OS OpenData™ :)
3 thoughts to “Using OS OpenData”
Glad to see you are making good use of OS OpenData(no attrib from me)
I love the way your post is littered with (R) and (TM) I am increasingly tempted to test the extent that you can take two words in normal use and apply a restriction to their use, maybe its, the capitalisation, lack of a space or insertion of a hyphen that gives it the edge.
If I wrote "I walked along the boundary line between the two properties" I presumably wouldn't need a (TM) but if I mispelt it as "boundary-line" would I? Or is it only when I capitalise the words, or do i have to append the letters OS (which could stand for Open Source or Operating System or even Old Socks"
Enough on this topic for now but look out for a blog post ranty piece when I get back from hols.
I'm surprised that OS Street View is being used to augment OSM. The OS's Open data licence seems fairly clear: "You must always use the following attribution statement to acknowledge the source of the information: Contains Ordnance Survey data © Crown copyright and database right [year]" – is that acceptable to OSM?
In addition, where's the acknowledgement in this blog post :-)
Have a look at the OSM Copyright page on the OSM Wiki, which lists this acknowledgement, as well as this posting on talk-gb in relation to the new OSM license.