Publishing OS Derived Data

If you use OS data to create a dataset, there are times when you’ll want to share and publish this. Here are the ways that you can do it.

What is derived data and what does it mean for me?

Derived data is new information or datasets that are created from existing data. It’s the data you create for your organisation using OS data as a source. 

You can use most OS data licensed to you under the Public Sector Geospatial Agreement (PSGA) to create new geographic datasets of your own.

How do I publish a derived dataset?

If you’re using OS OpenData supplied under the PSGA to make the dataset, this is covered by Open Government Licence – meaning you can publish anything created from this and all we ask is you acknowledge your use of OS OpenData (PDF).

For our other data, your public sector Member Licence lets you publish and share your data under Open Government Licence if you meet our publishing criteria, all you need to do is tell us you're going to publish your dataset. Read the criteria and tell OS about your dataset.

You do not need to use the click-to-accept End User Licence if you’re publishing or sharing OS OpenData. You may need to use this if you’re publishing other products.

Make sure you keep a log of who the data owner is and the source of your material.

What datasets can I publish that include OS data?

These are common categories of datasets our customers can publish using our presumption to publish criteria. Even if your data is not covered there, you can request an exemption.

Planning

Presumption to publish data includes the following types of information in local plans:

infrastructure plans,
action zones,
restrictive areas,
conservation areas where they’re under the Listed Buildings and Conservation Areas Act 1990, and
brownfield sites where they comply with the National Planning Policy Framework criteria and the requirements of The Housing and Planning Act 2016.

Various planning application data captured by Local Authorities also fall within the presumption to publish, as follows:

a co-ordinate of the location of the planning application

a polygon depicting the extent of the feature which is planned to be built (i.e. the extension), and
a polygon depicting the extent of the entire property boundary.

Note that a polygon depicting the extent of the original building (i.e. the building to which an extension is being added), or a polygon depicting the extent of the altered building (e.g. a house as extended/altered), do not fall within the presumption to publish.

You can see visual examples below.

Areas for development

Areas where planning permission has been requested or granted for large-scale housing, employment or mixed-use developments.

Well-established presumption to publish data includes where you’re the authority responsible for granting planning permission and the areas relate to: 

Creating 10 or more residential units; and/or  
A residential development on a site of 0.5 hectares or more; and/or 
A non-residential development on a site of at least one hectare; and/or 
A change of use of 1,000 square metres or more of gross floor space (not including housing).

Citizen services

Business administration

Electoral administration

Culture

Safety

Health

Environment

Travel

Public Rights of Way

Third-party data

Many OS products have data from third parties, like Royal Mail, and they own its intellectual property. You'll also need permission from these third parties to use their data.

Products with third-party data include:

Address data (e.g. AddressBase)
OS MasterMap Highways Network (Roads, RAMI and Paths)
OS MasterMap Highways Network with speed data
OS MasterMap Water Network Layer
1:25 000 Scale Colour Raster and 1:50 000 Scale Colour Raster
Code-Point and Code-Point with Polygons

(Address data can be made available under various terms under the PSGA, for instance the End User Licence or using the licensee's obligations for public viewing).