LogoLogo
OS Docs HomeOS NGDOS APIsOS Download ProductsMore than MapsOS Data Hub
  • Introduction to OS APIs
  • Core Concepts
    • Getting started with an API project
    • Authentication
    • Error codes
    • Rate-limiting policy
    • OS API branding
    • Service level agreements
    • Service availability dashboard
  • Accessing OS APIs
    • OS Maps API
      • Layers and styles
      • Getting started
        • ESRI ArcGIS Online
        • ESRI ArcGIS Pro
        • ESRI ArcMap
        • Cadcorp SIS
        • MapInfo Pro
        • QGIS
      • Technical specification
        • ZXY
        • WMTS
      • Code examples
    • OS Vector Tile API
      • What data is available?
      • Getting started
        • ESRI ArcGIS Pro
        • Cadcorp SIS
        • QGIS
        • Create a web application using the OS Vector Tile API
      • Technical specification
        • Service Metadata
        • Stylesheet
        • Tile request
      • Code examples
      • Stylesheets
    • OS NGD API – Tiles
    • OS NGD API – Features
    • OS Features API
      • OS Product Archive
      • What data is available?
      • Getting started
        • ArcGIS Online
        • ArcGIS Pro
        • ArcMap
        • Cadcorp SIS
        • MapInfo Pro
        • QGIS
      • Technical specification
        • getCapabilities
        • describeFeatureType
        • getFeature
        • Filtering
        • Paging
        • Empty values
      • Code examples
    • OS Names API
      • Getting started with example queries using Node.js
      • Technical specification
        • Find
        • Nearest
      • Code list
      • Code examples
    • OS Linked Identifiers API
      • What data is available?
      • Getting started with implementing a look-up application
      • Technical specification
        • Identifier
        • Identifier Types
        • Feature Types
        • Product Version Information
      • Code examples
    • OS Places API
      • Getting started with example queries using Node.js
      • Technical specification
        • Find
        • Postcode
        • UPRN
        • Nearest
        • BBOX
        • Radius
        • Polygon
      • Datasets
      • Code lists
      • Code examples
    • OS Match & Cleanse API
      • End of Life Information
      • Getting started with an example match query using Node.js
      • Technical specification
      • Datasets
      • Code lists
    • OS Downloads API
      • Getting started
        • Automating OS OpenData downloads
        • Automating OS Premium data downloads
      • Technical specification
        • OpenData products
        • OpenData product details
        • Download an OpenData product
        • OpenData product image
        • Data packages
        • Data package ID
        • Data package version
        • Data package version ID
        • Download a data package
    • OAuth 2 API
      • Getting started
      • Technical specification
  • Additional resources
    • OS API Wrappers
      • JavaScript
      • Python
      • R
  • Extra Links
    • Accessibility
    • Contact us
    • PSGA Product Summary
    • Terms and conditions
Powered by GitBook
On this page
  • The importance of our brand
  • Why is this important to us?
  • Helpful links:
  • Logo and copyright overview
  • Full colour API logo
  • White API logo
  • Copyright
  • Positioning
  • Exclusion zone - Minimum clear space
  • Minimum and Maximum
  • Prohibited use

Was this helpful?

  1. Core Concepts

OS API branding

PreviousRate-limiting policyNextOS Maps API

Last updated 6 months ago

Was this helpful?

The importance of our brand

It is important that our brand is applied correctly and consistently by you and adheres to the terms and conditions of our API solutions. It is also imperative that the nature of our roles are correctly communicated through the application of our logo and the correct explanation of our relationship.

This document provides guidance for you, as our API solution users, on the application of our branding. For these applications the API logo is used within our APIs only.

Why is this important to us?

Our brand is our personality, it represents who we are, so it’s extremely important that we protect our credibility and reputation. If you are using our API solutions it’s important that our brand is applied correctly. Through following these guidelines and applying the correct logo to our API solutions we can ensure that our brand is being represented correctly.

If you have any further questions about the use of our brand on your applications please

Helpful links:

  • - Branding for users developing solutions using OS data supplied via our APIs.

  • - Download the OS API logo from our Brand Portal.

Logo and copyright overview

To ensure our logo stands out on a map application, there is a keyline ‘blur’ added to both logo versions to ensure readability. These logo versions can only be used on a digital map application.

Full colour API logo

Our full colour logo is the preferred application option on a digital map.

Examples

Our coloured API logo is to be used on any illustrated map as shown below.


White API logo

The white logo with a grey keyline is the alternative application option on a digital map.

Examples

Our white API logo is to be used on any satellite, photographic or illustrated map as shown below.

Copyright

A downloadable asset is available. This includes the copyright statement and links for both error reporting and OS terms and conditions on a tinted bar. This should be edited to the correct date while retaining all original links.

Positioning

Copyright statement

Our copyright statement, terms and conditions and error reporting link should be positioned within the the embedded map across your web applications. This information should still be present within your mobile applications however this should sit within your menu bar, rather than on the map itself, to ensure that the limited view is not obscured.

Logo

Our logo should be positioned in the embedded map window across all your digital applications. This positioning should also be followed on a web and mobile application.

Exclusion zone - Minimum clear space

The logo exclusion zone is defined by the size of the ‘O’ from the word ‘Ordnance’ in the wordmark. The dimensions of the ‘O’ should be used on all sides of the logo to ensure clear space. No other element should encroach into this space, such as typography or graphic elements.

Minimum and Maximum

Minimum size

Minimum sizes have been set to ensure legibility for digital applications. The logo should remain the same size at all times, this is a fixed asset on a scalable map.

Minimum print size

Minimum digital size

Maximum size

Maximum sizes have been set as a guide to not exceed on any application.

Maximum print size

Maximum digital size

Prohibited use

Don’t stretch or distort the logo.
Don’t apply transparency and ensure contrast is sufficient.
Don’t add drop-shadows or any other effects.
Don’t separate the logomark and the wordmark.
Don’t change the colours in any way.
Don’t use the white logo on illustrated maps.
Don’t use the coloured logo on satellite or photographic styled maps.
Don’t place on a block colour background.

contact our Support Team
OS API Branding on GitHub
OS API logo download (ZIP)
Full colour API OS logo
Example 1 of the OS coloured logo on top of a map
Example 2 of the OS coloured logo on top of a map
Example 2 of the OS coloured logo on top of a map
White API OS logo
Example 1 of the OS white logo on top of a map
Example 2 of the OS white logo on top of a map
Example 3 of the OS white logo on top of a map
Copyright statement and links for both error reporting and OS terms and conditions on a tinted bar.
Copyright statement, terms and conditions and error reporting link positioned within the the embedded map across a web application.
White OS logo positioned in the bottom left of a web or mobile application.
OS colour logo highlighting the exclusion zone around all sides of the logo to ensure there is enough clear space.
OS logo with the minimum print size
OS logo with the minimum digital size
OS logo with the maximum print size
OS logo with the maximum print size