Acknowlegements and trademarks

General

What are our obligations?

As a licensee, when making OS information (including derived data) available to others, you are expected to attach the approprate attribution statements that acknowledges our intellectual property rights (IPR) interests in the data that you are using.

The acknowledgement used will depend on whether you are making OS OpenData or OS Licenced Data available, as the obligations are different.

With OS OpenData, as we use the Open Government Licence, then you just need to acknowledge our copyright interests and the source of the data. 

With OS Licensed Data, the starting point is a standard acknowledgement that exists in our Style Guide. You will find that this is referred to the Member Licence (Section 5) . The reason for this is to ensure consistency with all of our other commercial licences.

You then need to build on that standard acknowledgement, depending on the activity you are undertaking, there is other wording that you need to add.

You should also note that:

  • where licensed data is used, you should prefix or suffix your licence number with the letters "EUL" (which stands for End User Licence)
  • as some of our products include 3rd party data (such as our addressing datasets), we (as a licensee) are obliged to pass their requirements on, so you will need to add their acknowledgements.
  • similarly, if you are republishing other 3rd party data, they may also require you to acknowledge their IPR. 

To save you the time of looking through the various sections of the licence, we have provided the information under the relevant activity headings.

We have also have provided the appropriate Welsh language translations for those that need to meet those obligations.

What is your OS OpenData acknowledgement?

It doesn't matter in which format you are publishing OS OpenData products, then you just need to acknowledge OS' interests in the data by including the following attribution statement:

‘Contains OS data © Crown copyright [and database right] [year]’.

'Cynnwys data OS © Hawlfraint y Goron [a hawliau cronfa ddata] OS [flwyddyn].'

This includes data derived from OS OpenData products, 'Free to use data' and your derived datasets that have been notified to us under the 'presumption to publish' arrangements or been granted an exemption (see the derived data and derived data exemptions section).

You must include the same attribution acknowledgement requirement in any sub-licences of the data that you grant (and that of any further sub-licences to do the same)

Please note: if you are incorporating other data, such as Licensed Data, then you need to use the highest appropriate level of acknowledgement. For example, if you are overlaying a derived dataset that has been granted an exemption on terms equivalent to OS OpenData on to OS VectorMap Local, then the acknowledgement to use is the ‘Licensed data’ one and not the OS OpenData one.

Do we need to acknowledge OS if we are publishing our own data?

If you are publishing your own data that has been created independently of OS data (i.e. independently sourced data), no acknowledgement to OS is required as OS do not claim intellectual property rights (IPR) in your data.

If your data is being included with other data (such as OS OpenData or Licenced Data), then you should use the highest appropriate level of acknowledgement.

For example, if you are overlaying your Licensees Data on to OS VectorMap Local, then the acknowledgement to use is the ‘Licensed data’ one.

What acknowledgement is required for OS Licenced Data?

As mentioned above, with OS Licensed Data, the starting point is the standard acknowledgement that exists in our Style Guide

You then build on that according to the form that 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).

The following sections contain the various statements.

Please note: 

  • where licensed data is used, you should prefix or suffix your licence number with the letters "EUL" (which stands for End User Licence)
  • as some of our products include 3rd party data (such as our addressing datasets), we (as a licensee) are obliged to pass their requirements on, so you will need to add their acknowledgements.
  • similarly, if you are republishing other 3rd party data, they may also require you to acknowledge their IPR. 
Which OS data products have 3rd party licences included?

They are:

  • All AddressBase products
  • Code-Point and Code-Point with polygons
The additional requirements are shown below
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) into the base acknowledgement being used:

'© Local Government Information House Limited copyright and database rights [year of supply or date of publication]'

'© Hawlfraint a hawliau cronfa ddata cyfyngedig Tŷ Gwybodaeth ar Lywodraeth Leol [blwyddyn cyflenwi neu ddyddiad cyhoeddi]'

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’

'Mae’r cynnyrch hwn yn cynnwys data a grëwyd ac a gynhelir gan Lywodraeth Leol yr Alban'

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, supporting the Government vision of having one single definitive national addressing database for the public sector.

What do we have to add when using Code-Point or Code-Point with Polygons?

You need to add the following statement into the base acknowledgement being used:

'Contains National Statistics data © Crown copyright and database right 20nn'

'Mae’n cynnwys data Ystadegau Cenedlaethol © Hawlfraint y Goron a hawl cronfa ddata 20nn'

[an error occurred while processing this directive]