- I understand we are a licensee of OS - what are our obligations?
When sharing OS information (including derived data), you must include an attribution statement; otherwise known as a copyright acknowledgement.
The acknowledgement you use will depend on the type of OS data you are using and medium you are using (that is, paper, pdf, web mapping or data).
To save you the time of looking through the various sections of the Member Licence, we have provided the acknowledgements you need to use in the sections below.
We have also have provided Welsh language translations for those that need them.
- Why do we need to add an acknowledgement?
Is to ensure that any recipient of information is made aware of the limitations of use.
It also helps us to know the source when investigating a potential infringement by a third party.
- Do we need to acknowledge OS if we are publishing our own data?
If you have not used any OS data when creating the data, then we don't claim any intellectual property (IP) in it. The Member Licence defines this as independently sourced data.
If this is the only data being published, then you don't need to acknowledge OS.
If your data is included with OS data, then you should use the highest appropriate level of acknowledgement.
For example, if you are overlaying your non-OS based data on to OS VectorMap Local, then the acknowledgement to use is the Licensed data one.
- Where and how must the acknowledgement(s) be shown?
You must clearly show it in a legible font and in a conspicuous position on reproductions of OS data, for example:
- on a plot or view of data,
- the contents page of a book,
- the opening screen of a device,
- within terms and conditions of a service,
- as part of a 'read me' file when supplied as data.
- Acknowledging OS OpenData (all forms of publishing)
This only applies when you are using OS OpenData products (including creating derived data from them). If Licensed Data is being incorporated, then you need to use the appropriate Licensed Data acknowledgement - and the OS OpenData acknowledgement is not required.
We use the Open Government Licence (OGL) for OS OpenData. Under the terms of that licence, we are allowed to use our own attribution statement.
So, it doesn't matter whether the mapping is on paper or in digital form, if you are just publishing OS OpenData (or an 'exempted' dataset), you just need to include this attribution statement:
Contains OS data © Crown copyright [and database right] [year].
Welsh language version:
Cynnwys data OS Ⓗ Hawlfraint y Goron [a hawliau cronfa ddata] OS [flwyddyn].
- The same attribution acknowledgement should be included in any sub-licences of the data that you grant (or any other further re-use).
- If you are using Code-Point Open you need to add an additional statement because that product contains additional 3rd party rights.
- Are there other occasions when we can use the OS OpenData acknowledgement?
You can use it with your derived datasets that have been notified to us under the 'presumption to publish' arrangements or where you been granted an exemption from the Member Licence
For more information on this see the derived data and derived data exemptions section.
- Why is part of the acknowledgement in square brackets [ ]?
For example "Contains OS data © Crown copyright [and database rights][year]".
With [year], you insert the year that you are publishing the OS data.
With [and database rights], this statement is needed when you are publishing OS vector data, raster data stored in a database environment and addressing products. You can delete this statement on other occasions.
For example, if you are publishing OS Open Map - Local and or Boundary-Line data the acknowledgement is:
"Contains OS data © Crown copyright and database rights 2017"
- Which OS data products don't need 'and database rights' included?
Our raster products, for example, 1:50 000 Scale Colour Raster and 1:25 000 Scale Raster.
All of our vector, addressing and Code-Point products need it included.
Note: If you are overlaying a raster layer with vector data, you need to include it.
- Some acknowledgements contain 'EUL', what does this mean?
EUL means 'End User Licence'.
You should include EUL in the acknowledgement where an End User Licence is being used.
This will be where you are publishing Licenced data to a 3rd party, including where it being displayed on your website.
Note: you don't need to use an End User Licence in other circumstances.
More about publishing your information.
- What if we are incorporating other OS data?
You need to use the highest appropriate level of acknowledgement.
As examples, you are:
- combining OS OpenData with OS VectorMap Local, or
- overlaying a derived dataset that has been granted an exemption on terms equivalent to OS OpenData onto OS MasterMap Topography Layer.
In both cases, the acknowledgement to use is the ‘Licensed data’ one and not the 'OS OpenData' one.
- What acknowledgement is required for OS Licenced Data?
You need to use:
© Crown copyright [and database rights] [insert year] OS [licence number]
This needs to be shown in a legible font and in a conspicuous position.
You may then need to add further information, depending on how you are publishing your information in (i.e. on paper, in electronic documents, on the web, or as a data file that can be used in a GIS).
Welsh language version:
Ⓗ Hawlfraint y Goron a hawliau cronfa ddata [mewnosod y flwyddyn] OS [rhif y drwydded]
- Which OS data products have additional 3rd party licensing included?
PSMA / OSMA Licensed Data
- All AddressBase products
- Code-Point Open, Code-Point and Code-Point with polygons
Other OS products (for more information on these acknowledgements see our Style Guide
- AddressBase Islands
- Points of Interest
- OS MasterMap Imagery Layer
- What do we have to add when using an AddressBase product?
Whenever you are displaying or reproducing any AddressBase product, you need to include the following statement(s):
© Local Government Information House Limited copyright and database rights [year of supply or date of publication]
In addition, wherever data relating to Scotland is included, this statement also needs to be incorporated:
This product contains data created and maintained by Scottish Local Government
© Crown copyright and database rights (insert year) OS (licence number), © Local Government Information House Limited copyright and database rights and contains data created and maintained by Scottish Local Government [year of supply or date of publication].
Note: AddressBase products also includes AddressBase Incremental Change Supply (ABICS), which used to be known as the National Land and Property Gazetteer (NLPG) before it was rebranded.
Welsh language versions:
Ⓗ Hawlfraint a hawliau cronfa ddata cyfyngedig Tŷ Gwybodaeth ar Lywodraeth Leol [blwyddyn cyflenwi neu ddyddiad cyhoeddi]
Mae’r cynnyrch hwn yn cynnwys data a grëwyd ac a gynhelir gan Lywodraeth Leol yr Alban
- What do we have to add when using a Code-Point product?
The Code-Point products are:
- Code-Point Open
- Code-Point with Polygons
You need to add the following statement to the base acknowledgement being used:
Contains National Statistics data © Crown copyright and database rights 20nn
© Crown copyright and database rights [insert year] OS [licence number] and contains National Statistics data © Crown copyright and database rights 20nn
Welsh language version:
Mae’n cynnwys data Ystadegau Cenedlaethol Ⓗ Hawlfraint y Goron a hawl cronfa ddata 20nn