LogoLogo
OS Docs HomeOS NGDOS APIsOS Download ProductsMore than MapsContact Us
  • More than Maps
  • Geographic Data Visualisation
    • Guide to cartography
      • Introduction to cartography
      • Types of maps
      • Symbology
      • Colour
      • Text on maps
      • Generalisation
      • Coordinate reference systems
      • Projections
      • Scale
      • Map legends
      • Map layout
      • Relief representation
      • North arrows
    • Guide to data visualisation
      • Introduction to data visualisation
      • GeoDataViz design principles
      • Types of visualisation
      • Thematic mapping techniques
      • Data visualisation critique
      • Accessible data visualisation
      • Ethical data visualisation
      • Software
      • Data
    • GeoDataViz assets
      • GeoDataViz basemaps
      • Stylesheets
      • GeoDataViz virtual gallery
      • Equal area cartograms
      • How did I make that?
        • Apollo 11 Landing
        • North York Moors National Park, 70 years
        • Snowdonia National Park, 70 years
        • Great Britain's National Parks
        • Great Britain's Islands
        • Great Britain's AONB's and National Scenic Areas
        • Famous shipwrecks of Pembrokeshire
        • Trig pillars today
        • Britain's most complex motorway junctions
      • #30DayMapChallenge
  • Data in Action
    • Examples
  • Demonstrators
    • 🆕Product Viewer
    • Addressing & location demonstrators
      • Address Portfolio overview
      • Which address product should you use?
      • AddressBase
      • AddressBase Core
      • AddressBase Plus
      • AddressBase Premium
      • Address Classifications
      • Addressing Lifecycle
      • OS Emergency Services Gazetteer
      • What are Vertical Streets?
      • Why are there differences in boundaries?
    • Contextual demonstrators
    • Customer best practice
      • Channel Shift
      • Data Management and OS Data Hub
      • End User Licence vs Contractor Licence
      • 🆕 IDs vs Spatial Relationships
      • Why we should capture good quality addresses at source
      • Why we Snap and Trace
    • Network Demonstrators
      • OS Detailed Path Network
      • OS Multi Modal Routing Network
        • OS Multi Modal Routing Network
      • Water Networks overview
      • OS MasterMap Highways Network and OS NGD Speeds
      • OS MasterMap® Highways Network and OS Open Roads™
    • OS MasterMap Generation APIs
      • Using the OS Features API
      • Using the OS Features API Archive
      • Using the OS Downloads API
      • Using OS APIs in ESRI Software
    • 🆕OS NGD (National Geographic Database)
      • OS NGD Address
      • OS NGD Boundaries
      • 🆕OS NGD Buildings
        • 🆕Building and Building Access Feature Types
        • Building Part and Building Line Feature Types
      • 🆕OS NGD Geographical Names
      • OS NGD Land
      • OS NGD Land Cover enhancements
      • 🆕OS NGD Land Use
      • OS NGD Land Use enhancements
      • 🆕OS NGD Structures
        • 🆕OS NGD Structures
        • Field Boundaries
      • 🆕OS NGD Transport Features
      • 🆕OS NGD Transport Network
      • OS NGD Transport RAMI
      • OS NGD Water Features
      • OS NGD Water Network
      • OS NGD API - Features
      • Ordering OS NGD data
      • Change only updates
      • OS NGD Versioning
      • Creating a topographic map from OS NGD Data
      • Analytical styling for OS NGD data
    • OS MasterMap® demonstrators
    • 🆕Product & API Comparisons
      • 🆕Comparison of Water Network Products
  • Tutorials
    • GeoDataViz
      • Thematic Mapping Techniques
      • Downloading and using data from the OS Data Hub
      • How to download and use OS stylesheets
      • How to use the OS Maps API
      • Creating a bespoke style in Maputnik
    • GIS
      • Analysing pavement widths
      • Basic routing with OS Open Data and QGIS
      • Walktime analysis using OS Multi-modal Routing Network and QGIS
      • Creating 3D Symbols for GIS Applications
      • Constructing a Single Line Address using a Geographic Address
      • Creating a Digital Terrain Model (DTM)
      • Visualising a road gradient using a Digital Terrain Model
      • Visualising a road gradient using OSMM Highways
    • 🆕APIs
      • 🆕Using OS APIs with EPC API
      • 🆕OS APIs and ArcGIS
  • Deep Dive
    • Introduction to address matching
    • Guide to routing for the Public Sector
      • Part 1: Guide to routing
      • Part 2: Routing software and data options
      • Part 3: Building a routable network
    • Unlocking the Power of Geospatial Data
    • Using Blender for Geospatial Projects
    • A Guide to Coordinate Systems in Great Britain
      • Myths about coordinate systems
      • The shape of the Earth
      • What is position?
        • Types of coordinates
        • We need a datum
        • Position summary
      • Modern GNSS coordinate systems
        • Realising WGS84 with a TRF
        • The WGS84 broadcast TRF
        • The International Terrestrial Reference Frame (ITRF)
        • The International GNSS Service (IGS)
        • European Terrestrial Reference System 1989 (ETRS89)
      • Ordnance Survey coordinate systems
        • ETRS89 realised through OS Net
        • National Grid and the OSGB36 TRF
        • Ordnance Datum Newlyn
        • The future of British mapping coordinate systems
        • The future of British mapping coordinate systems
      • From one coordinate system to another: geodetic transformations
        • What is a geodetic transformation?
        • Helmert datum transformations
        • National Grid Transformation OSTN15 (ETRS89–OSGB36)
        • National Geoid Model OSGM15 (ETRS89-Orthometric height)
        • ETRS89 to and from ITRS
        • Approximate WGS84 to OSGB36/ODN transformation
        • Transformation between OS Net v2001 and v2009 realisations
      • Transverse Mercator map projections
        • The National Grid reference convention
      • Datum, ellipsoid and projection information
      • Converting between 3D Cartesian and ellipsoidal latitude, longitude and height coordinates
      • Converting between grid eastings and northings and ellipsoidal latitude and longitude
      • Helmert transformation worked example
      • Further information
  • Code
    • Ordnance Survey APIs
    • Mapping
    • Routing with pgRouting
      • Getting started with OS MasterMap Highways and pgRouting
      • Getting started with OS MasterMap Highways Network - Paths and pgRouting
      • Getting started with OS NGD Transport Theme and pgRouting
      • Getting started with OS NGD Transport Path features and pgRouting
  • RESOURCES
    • 🆕Data Visualisation External Resources
Powered by GitBook

Website

  • Ordnance Survey

Data

  • OS Data Hub
On this page
  • Coordinate systems
  • Vertical coordinate reference systems
  • What does this all mean for the map I’m creating?
  • Further Information

Was this helpful?

  1. Geographic Data Visualisation
  2. Guide to cartography

Coordinate reference systems

PreviousGeneralisationNextProjections

Last updated 4 months ago

Was this helpful?

Let’s start with the shape of the Earth. Unfortunately, it’s not a perfect sphere as that would make life too simple. It’s actually an uneven and slightly squashed sphere which is flattened at the poles and bulges around the equator. This irregular and lumpy shape is represented by a surface known as the geoid. The geoid is related to the naturally differing force of gravity and is close to mean sea level and represents the best averaged shape of the Earth, ignoring the topography of mountain heights and sea depths.

The shape of the geoid however is too complicated for the calculations required to make a map, so simpler mathematical models, which best estimate the geoid, have been created and are known as reference ellipsoids. These models can be designed to achieve a best fit to the geoid globally or to best fit the Earth’s surface at a specific location for mapping a single country.

In addition to an ellipsoid there are other parameters that, when all collectively adopted, constitute a “Coordinate Reference System” (CRS). There are many CRSs but they all aim to achieve the same thing - a model used for describing positions on the Earth. As such the coordinates of a physical point on the Earth will differ depending on the underlying CRS or, vice versa, the same coordinates will appear in different locations depending on the underlying CRS.

For example, the diagram below shows the physical position of three points that all have the same coordinates but in three different coordinate systems (OSGB36, WGS84 and ED50). Each one of these coordinate systems is widely used and fit for its purpose, and none of them is wrong. The differences between them are just a result of the different conventions (ellipsoid, etc…) adopted by the coordinate systems.

To go between different CRSs a coordinate transformation must be used. This is a mathematical process that can range from a simple shift in values to a complex “rubber sheet” operation that aims to model variances in one or both of the CRSs. For example, ETRS89 coordinates from a GNSS positioning process should pass through the OSTN15 transformation model (a “rubber sheet” process) in order to become OSGB36 National Grid coordinates.

Coordinate systems

Now that we have our model of the Earth (the CRS) we need some coordinates to describe positions within the CRS. A coordinate system allows us to identify a position on the Earth’s surface and relate it to a position on a map, and vice versa. The two most common coordinate systems are latitude/longitude or a national grid system.

Latitude and longitude are theoretical lines, superimposed on a 3D model of the Earth. Lines of latitude run parallel to the Equator whereas lines of longitude run from pole to pole. Together, these form what we call a ‘graticule.’ Latitude is measured as the number of degrees, minutes, and seconds a place is north or south of the equator whilst longitude is the number of degrees, minutes, and seconds a place is east and west of an arbitrary ‘zero’ line – almost always the Greenwich Prime Meridian.

Often, to make navigation and defining a position easier, many countries have developed their own National Grid Coordinate System which comprises a regular grid, projected up from the curved surface of the ellipsoid.

For Great Britain, Ordnance Survey created the British National Grid as a way of defining locations across GB. This coordinate system only applies to GB and is used on all OS maps. The origin of this grid (bottom left corner) is just west of the Isles of Scilly meaning that all grid references on the GB landmass are positive. Coordinates are stated as the distance east (Eastings) of the origin, followed by the distance north (Northings) of the origin. A position in the UK can be easily communicated by providing a grid reference using this national grid system.

Always remember: Along the corridor (eastings) then up the stairs (northings).

For those wondering what happened to Northern Ireland, Ordnance Survey is the national mapping agency for Great Britain only. Ordnance Survey Northern Ireland (OSNI) is responsible for mapping in Northern Ireland and they use the Irish National Grid to define positions.

To make referencing map squares a little easier the UK is split into 100km squares, each with a two-letter identifier. These 100km square are split into ten 10x10km squares and split again into 1x1km squares. These squares are the blue lines on OS Landranger and Explorer maps. A map tile reference can be given using the 100km square ID and the eastings and northings within the 100km square.

  • OSGB36 National Grid, EPSG::27700. The CRS used for OS map data.

  • ETRS89, EPSG::4258 (2D) and EPSG::4937 (3D). The CRS commonly used across Europe for data collected using GNSS positioning methods.

  • WGS84, EPSG::4326 (2D) and EPSG::4979 (3D). The native datum of the US GPS GNSS system. Data collected using GPS can often be flagged as WGS84 even though it may be ETRS89. The difference between ETRS89 and WGS84 can be ignored for most purposes.

Vertical coordinate reference systems

We’ve defined how horizontal coordinate systems work but maps also show height. For this, we need to define where zero is. Generally, it’s mean sea level. For GB, zero is defined as mean sea level measured at the Newlyn tide gauge in Cornwall between 1915 and 1921 and is known as Ordnance Datum Newlyn (ODN). All heights on OS maps, are vertical heights above (or below) this known benchmark.

What does this all mean for the map I’m creating?

What does this mean for your maps? Well, if you’re creating a map in a GIS which will be used for navigation, you’ll probably want to include some way that the user can define where they are, and someone else to be able to work out where this is. As such, in your GIS, it’s wise to pick a sensible coordinate reference system – one that works for the locality you’re mapping. For this kind of map you will probably want to define this information somewhere on your map so that it is clear which coordinate system the map uses.

It is often helpful to include the grid and/or a graticule on your map in some way to help users define their location.

Also, it may be that some of the data you are importing into your GIS has been collected in a certain coordinate reference system. You’ll need to make sure you import your data in the right coordinate reference system in order for them to load in their correct geographical position. If you have lots of data in difference coordinate systems, you may need to apply some transformations to ensure that all data is in the same CRS.

Further Information

Tip: On the , if you hold your finger on the location you want a grid reference for, it will display the National Grid reference.

CRSs are often identified with a unique number – a SRID (Spatial Reference System Identifier). A common SRID Authority is the EPSG registry (). The SRID is usually in the format “EPSG::xxxx”. CRSs in common use in Great Britain, and their EPSG codes, are:

For a much more in-depth discussion of coordinate systems, we recommend reading our

If you’re creating a thematic map where defining exact location is not important, the coordinate system you use won’t matter so much. Make sure you think carefully about the you use though if you’re creating a small-scale map.

For a more in depth look at Coordinate reference systems and projections please take a look at

OS Maps App
https://epsg.org/home.html
guide to the coordinate systems of Great Britain
projection
A Guide to Coordinate Systems in Great Britain
The physical position of three points that all have the same coordinates in three different coordinate systems.
The graticule – lines of latitude and longitude
Coordinate systems of Great Britain: the graticule shown in grey and the British National Grid shown in blue
British National Grid
Technical information note