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
  • The OSGB36 datum
  • The OSGB36 TRF
  • Relative accuracy of OSGB36 control points

Was this helpful?

  1. Deep Dive
  2. A Guide to Coordinate Systems in Great Britain
  3. Ordnance Survey coordinate systems

National Grid and the OSGB36 TRF

PreviousETRS89 realised through OS NetNextOrdnance Datum Newlyn

Last updated 4 months ago

Was this helpful?

The coordinates of all features shown on OS maps are determined with respect to a TRF called OSGB36 (Ordnance Survey Great Britain 1936). This is what land surveyors would call a ‘traditional triangulation datum’ (as we saw before, this is strictly a misuse of the term ‘datum’ – OSGB36 consists of a datum and a TRF). OSGB36 is usually used with National Grid easting and northing coordinates (see Transverse Mercator map projections) using the formulae given in .

The OSGB36 datum

OSGB36 was not created in quite the logical way specified in traditional surveying textbooks for the establishment of a geodetic coordinate system. Those textbooks say one should first choose an astronomical observatory as the ‘initial point’ at which the datum will be defined. Here one measures the latitude and the direction of north by astronomy, and defines the direction towards the centre of the mapping ellipsoid . By defining an ellipsoidal latitude, longitude and ellipsoid height for the initial point, the mapping ellipsoid and Cartesian axes of the coordinate system is fixed in space relative to that point – that is, the datum is defined. This is the traditional procedure we outlined in .

The centre of the mapping ellipsoid is defined in terms of the angle between it and the local direction of gravity.

The original triangulation of Britain was carried out between 1783 and 1853 and is known as the ‘Principal Triangulation’. However, when the country was entirely retriangulated between 1936 and 1953 to create OSGB36, the datum definition (the arbitrary position and orientation of the ellipsoid relative to the primary control stations) was adopted from the original triangulation using the average of 11 old primary control station coordinates. Therefore, OSGB36 does not have an initial point – the datum is defined implicitly by the primary control station coordinates. This is an equally acceptable way of defining a datum: the datum being a matter of convenience, it does not matter much how you define it.

SOSGB36 was an early example of a network with a datum defined by an average at a selection of stations. This procedure is now universally used in GNSS networks.

The ellipsoid used in the OSGB36 datum is that defined by Sir George Airy in 1830 (later Astronomer Royal). Its defining constants are a = 6377563.396m and b = 6356256.909m (see annex A for a summary of datum constants). Hence the Airy 1830 ellipsoid is a bit smaller than GRS80 and a slightly different shape. Also, it is not geocentric as GRS80 is: it is designed to lie close to the Geoid beneath the British Isles. Hence only a tiny fraction of the surface of the ellipsoid has ever been used – the part lying beneath Britain. The rest is not useful. So, the Airy ellipsoid differs from GRS80 in size, shape, position and orientation, and this is generally true of any pair of geodetic ellipsoids.

If we want to convert latitudes and longitudes on one ellipsoid to those quantities on another ellipsoid, we need to take account of the differences in position and orientation of the ellipsoids as well as the differences in size and shape.

The OSGB36 TRF

Before the 1950s, coordinate system TRFs contained many angle measurements but very few distance measurements. This is because angles could be measured relatively easily between hilltop primary control stations with a theodolite, but distance measurement was very difficult. A consequence of this was that the shape of the TRF was well known, but its size (scale) was poorly known. The distance between primary control stations was established by measuring just one or two such distances, then propagating these through the network of angles by trigonometry (hence the name ‘trig pillars’).

When the OSGB36 triangulation TRF was established, no new distance measurements were used. Instead, the overall size of the network was made to agree with that of the old 18th century Principal Triangulation using the old coordinates of the 11 control stations mentioned in the previous section. Hence the overall scale of the TRF still used for British mapping came to be derived from the measurement of a single distance between two stations on Hounslow Heath in 1784 using eighteen-foot glass rods! The error thus incurred in OSGB36 is surprisingly low – only about 20 metres in the length of the country (which is approx. 20 ppm).

The 326 primary control stations of the OSGB36 TRF cover the whole of Great Britain, including Orkney and Shetland but not the Scilly Isles, Rockall or the Channel Islands. It is also connected to Northern Ireland, the Irish Republic, and France. This primary control network was densified by the addition of 2 695 secondary control stations, 12 236 tertiary control stations and 7 032 fourth order control stations. Hence until recently the ‘official OSGB36’ included more than 22 000 reference points. In continuous survey work over the decades, Ordnance Survey surveyors added many tens of thousands more ‘minor control’ points, which were used in map revision.

OSGB36 coordinates are latitudes and longitudes on the Airy 1830 ellipsoid. Ideally, ellipsoid heights relative to the Airy ellipsoid would be added to give complete three-dimensional information. Unfortunately, no easy method of measuring ellipsoid height was available before the late 1980s, so we only have horizontal information in OSGB36. The coordinates (National Grid eastings and northings) of a large number of OSGB36 trig pillars are available from the Ordnance Survey website.

In 2002 the definition of OSGB36 underwent a fundamental change with the release of the Definitive Transformation OSTN02™. OSTN02 was updated in August 2016 to OSTN15. OSTN15, in combination with the ETRS89 coordinates of the OS Net stations, rather than the fixed triangulation network, now define the National Grid. This is a subtle change in definition only and does not mean that existing OSGB36 coordinates need to be changed in any way.

Relative accuracy of OSGB36 control points

Relative accuracy of control stations within the OSGB36 coordinate system.

Type of OSGB36 horizontal control station
Expected accuracy (m) (1 standard error)
Within circular area of diameter (km)

Primary control station

Error free

N/A

Secondary control station

0.06

15

Tertiary control station

0.05

7

Minor control station

0.04

3

Chain survey station

0.08

3

Map detail station

0.06

2

The following table is a statistical statement of the accuracy of OSGB36 control points relative to surrounding control stations of the same type. The primary layer of the OSGB36 TRF consists of the primary triangulation stations, which are considered error-free within the OSGB36 coordinate system. The Ordnance Survey ETRS89–OSGB36 transformation (see ) describes the real distortions in OSGB36 that are not considered here. The table below shows the expected accuracy of control station positions in relation to other control stations of the same type within a circular area of the given diameter.

Converting between grid eastings and northings and ellipsoidal latitude and longitude
We need a datum
National Grid Transformations OSTN15