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
  • Myth 1: ‘A point on the ground has a unique latitude and longitude’
  • Myth 2: ‘A horizontal plane is a level surface’
  • Myth 3: ‘The true coordinates of a ground point do not change’
  • Myth 4: ‘There are exact mathematical formulae to change between coordinate systems’

Was this helpful?

  1. Deep Dive
  2. A Guide to Coordinate Systems in Great Britain

Myths about coordinate systems

PreviousA Guide to Coordinate Systems in Great BritainNextThe shape of the Earth

Last updated 4 months ago

Was this helpful?

Myth 1: ‘A point on the ground has a unique latitude and longitude’

For reasons that are a mixture of valid science and historical accident, there is no one agreed ‘latitude and longitude’ coordinate system. There are many different meridians of zero longitude (prime meridians) and many different circles of zero latitude (equators), although the former generally pass somewhere near Greenwich, and the latter is always somewhere near the rotational equator. There are also more subtle differences between different systems of latitude and longitude which are explained in this document.

The result is that different systems of latitude and longitude in common use today can disagree on the coordinates of a point by more than 200 metres. For any application where an error of this size would be significant, it’s important to know which system is being used and exactly how it is defined.

The figure below shows three points that all have the same latitude and longitude (approximately N50 56 18, W001 28 11), 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 fact that any system of ‘absolute coordinates’ is always arbitrary. Standard conventions ensure only that different coordinate systems tend to agree to within half a kilometre or so, but there is no fundamental reason why they should agree at all.

Myth 2: ‘A horizontal plane is a level surface’

Of course it cannot be, because the Earth is round – any gravitationally level surface (such as the surface of the wine in your glass, or the surface of the sea averaged over time) must curve as the Earth curves, so it cannot be flat (that is, it cannot be a geometrical plane). But more than this, a level surface has a complex shape – it is not a simple curved surface like a sphere. When we say ‘a level surface’ we mean a surface that is everywhere at right angles to the direction of gravity. The direction of gravity is generally towards the centre of the Earth as you would expect, but it varies in direction and magnitude from place to place in a complex way, even on a very local scale. These variations, which are too small for us to notice without specialist measuring equipment, are due to the irregular distribution of mass on the surface (hills and valleys) and also to the variable density of the Earth beneath us. Therefore, all level surfaces are actually bumpy and complex.

This is very important to coordinate systems used to map the height of the ground, because the idea of quantified ‘height’ implies that there is a level surface somewhere below us which has zero height. Even statements about relative height imply extended level surfaces. When we casually say ‘Point A is higher than point B’, what we really mean is ‘The level surface passing through point A, if extended, would pass above point B’ So to accurately quantify the height difference between A and B, we would need to know the shape of the level surface passing through point A. In fact we choose a general ‘reference level surface’ of zero height covering the whole country to which we can refer all our measured heights. However, this reference level surface is not flat.

Myth 3: ‘The true coordinates of a ground point do not change’

They certainly do, due to the continuous deforming motions of the Earth. Relative to the centre of the Earth, a point on the ground can move as much as a metre up and down every day just because of the tidal influences of the sun and moon. The relative motion of two continents can be 10 centimetres a year, which is significant for mapping because it is constant year after year – after 50 years a region of the earth may have moved by 5 metres relative to a neighbouring continent. Many other small effects can be observed – the sinking of Britain when the tide comes in over the continental shelf (a few centimetres), the sinking of inland areas under a weather system ‘high’ (about 5 millimetres), and the rising of the land in response to the melting of the last Ice Age (about 2 millimetres per year in Scotland, up to 1 centimetre per year in Scandinavia). Generally, as the size of the region of the Earth over which we want to use a single coordinate system increases, the more these dynamic Earth effects are significant.

The modern trend is to use global coordinate systems even for local applications. Therefore, it is important to realise that in a global coordinate system, the ground on which we stand is constantly moving. This leads to subtleties in coordinate system definition and use.

Myth 4: ‘There are exact mathematical formulae to change between coordinate systems’

Exact formulae only apply in the realm of perfect geometry – not in the real world of coordinated points on the ground. The ‘known coordinates’ of a point in one coordinate system are obtained from a large number of observations that are averaged together using a whole raft of assumptions. Both the observations and the assumptions are only ever approximately correct and can be of dubious quality, particularly if the point was coordinated a long time ago. It will also have moved since it was coordinated, due to subsidence, continental plate motion and other effects.

The result is that the relationship between two coordinate systems at the present time must also be observed on the ground, and this observation too is subject to error. Therefore, only approximate models can ever exist to transform coordinates from one coordinate system to another. The first question to answer realistically is ‘What accuracy do I really require?’ In general, if the accuracy requirements are low (5 to 10 metres, say) then transforming a set of coordinates from one coordinate system to another is simple and easy. If the accuracy requirements are higher (anywhere from 1 centimetre to half a metre, say), a more involved transformation process will be required. In both cases, the transformation procedure should have a stated accuracy level.

Three points with the same latitude and longitude in three different coordinate systems. The map extract is approximately 300m wide.
Three points with the same latitude and longitude in three different coordinate systems. The map extract is approximately 300m wide.