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
  • Latitude, longitude and ellipsoid height
  • Cartesian coordinates
  • Geoid height (also known as orthometric height)
  • Mean sea level height
  • Eastings and northings

Was this helpful?

  1. Deep Dive
  2. A Guide to Coordinate Systems in Great Britain
  3. What is position?

Types of coordinates

PreviousWhat is position?NextWe need a datum

Last updated 4 months ago

Was this helpful?

Latitude, longitude and ellipsoid height

The most common way of stating terrestrial position is with two angles, latitude and longitude. These define a point on the globe. More correctly, they define a point on the surface of an ellipsoid that approximately fits the globe. Therefore, to use latitudes and longitudes with any degree of certainty, you must know which ellipsoid you are dealing with.

The relationship between the ellipsoid and latitude and longitude is simple (see diagram below). North-south lines of constant longitude are known as meridians, and east-west lines of constant latitude are parallels. One meridian of the ellipsoid is chosen as the prime meridian and assigned zero longitude. The longitude of a point on the ellipsoid is the angle between the meridian passing through that point and the prime meridian. Usually, the scale of longitude is divided into eastern and western hemispheres (hemiellipsoids, actually!) from 0 to 180 degrees West and 0 to 180 degrees East. The equator of the ellipsoid is chosen as the circle of zero latitude. The latitude of a point is the angle between the equatorial plane and the line perpendicular to the ellipsoid at that point. Latitudes are reckoned as 0 to 90 degrees North and 0 to 90 degrees South, where 90 degrees either North or South is a single point – the pole of the ellipsoid.

So latitude and longitude give a position on the surface of the stated ellipsoid. Since real points on the ground are actually above (or possibly below) the ellipsoid surface, we need a third coordinate, the so-called ellipsoid height, which is simply the distance from the point to the ellipsoid surface along a straight line perpendicular to the ellipsoid surface. The term ‘ellipsoid height’ is actually a misnomer, because although this is an approximately vertical measurement, it does not give true height because it is not related to a level surface. It does, however, unambiguously identify a point in space above or below the ellipsoid surface in a simple geometrical way, which is its purpose.

With the coordinate triplet of latitude, longitude and ellipsoid height, we can unambiguously position a point with respect to a stated ellipsoid. To translate this into an unambiguous position on the ground, we need to know accurately where the ellipsoid is relative to the piece of ground we are interested in. How we do this is discussed in and Realising the datum definition with a Terrestrial Reference Frame below.

Cartesian coordinates

Rectangular Cartesian coordinates are a very simple system of describing position in three dimensions, using three perpendicular axes X, Y and Z. Three coordinates unambiguously locate any point in this system. We can use it as a very useful alternative to latitude, longitude and ellipsoid height to convey exactly the same information.

We use three Cartesian axes aligned with the latitude and longitude system (see diagram above). The origin (centre) of the Cartesian system is at the centre of the ellipsoid. The X axis lies in the equator of the ellipsoid and passes through the prime meridian (0 degrees longitude). The negative side of the X axis passes through 180 degrees longitude. The Y axis also lies in the equator but passes through the meridian of 90 degrees East, and hence is at right angles to the X axis. Obviously, the negative side of the Y axis passes through 90 degrees West. The Z axis coincides with the polar axis of the ellipsoid; the positive side passes through the North Pole and the negative side through the South Pole. Hence it is at right angles to both X and Y axes.

We are making some reasonable simplifications here. We assume that the level surfaces passing through our points of interest are parallel to the Geoid. This is not actually true, but the difference is negligible.

Geoid height (also known as orthometric height)

The term ellipsoid height is misleading because a distance above a reference ellipsoid does not necessarily indicate height – point A can have a greater ellipsoid height than point B while being downhill of B. As we saw in the 'Shape of the Earth' page, this is because the ellipsoid surface is not level – therefore a distance above the ellipsoid is not really a height at all. The reference surface that is everywhere level is the Geoid. To ensure that the relative height of points A and B correctly indicates the gradient between them, we must measure height as the distance between the ground and the Geoid, not the ellipsoid. This measurement is called ‘orthometric height’ or simply ‘Geoid height’.

(We are making some reasonable simplifications here. We assume that the level surfaces passing through our points of interest are parallel to the Geoid. This is not actually true, but the difference is negligible.)

The relationship between ellipsoid height H and Geoid height (orthometric height) h is:

where N is (reasonably enough) the ‘Geoid-ellipsoid separation’.

some authors use the letters h and H the other way round

Here we assume that the Geoid is parallel to the ellipsoid (actually it diverges by about 0.002° in Britain with respect to the GRS80 ellipsoid, which is negligible here) and that there is negligible curvature in a plumb-line extended to the Geoid.

Because the Geoid is a complex surface, N varies in a complex way depending on latitude and longitude. A lookup table of N for any particular latitude and longitude is called a Geoid model. Therefore, you need a Geoid model to convert ellipsoid height to Geoid height and vice-versa. The figure below shows these quantities for two points A and B. The orthometric height difference between A and B is:

Because both GNSS determination of H and Geoid model determination of N are more accurate in a relative sense (differenced between two nearby points) than in a global ‘absolute’ sense, values of will always be more accurate than either or . This is because most of the error in is also present in and is removed by differencing these quantities. Fortunately, it is usually that we are really interested in: we want to know the height differences between pairs of points.

The development of precise Geoid models is very important to increasing the accuracy of height coordinate systems. A good Geoid model allows us to determine orthometric heights using GNSS (which yields ellipsoid height) and equation (1) (to convert to orthometric height). The GNSS ellipsoid height alone gives us the geometric information we need, but does not give real height because it tells us nothing about the gravity field. Different Geoid models will give different orthometric heights for a point, even though the ellipsoid height (determined by GNSS) might be very accurate. Therefore, orthometric height should never be given without also stating the Geoid model used. As we will now see, even height coordinate systems set up and used exclusively by the method of spirit levelling involve a Geoid model, although this might not be stated explicitly.

Mean sea level height

We will now take a look at the Geoid model used in OS mapping on the British mainland, although most surveyors might not immediately think of it as such. This is the Ordnance Datum Newlyn (ODN) vertical coordinate system. Ordnance Survey maps state that heights are given above ‘mean sea level’. If we’re looking for sub-metre accuracy in heighting this is a vague statement, since mean sea level (MSL) varies over time and from place to place, as we noted in the previous section.

ODN corresponds to the average sea level measured by the tide‑gauge at Newlyn, Cornwall between 1915 and 1921. Heights that refer to this particular MSL as the point of zero height are called ODN heights. ODN is therefore a ‘local geoid’ definition as discussed in the previous section. ODN heights are used for all British mainland Ordnance Survey contours, spot heights and bench mark heights. ODN heights are unavailable on many offshore islands, which have their own MSL based on a local tide‑gauge.

A simple picture of MSL heights compared to ellipsoid heights is shown in the figure below. It shows ODN height as a vertical distance above a mean sea level surface continued under the land.

ODN orthometric heights have become a national standard in Britain, and are likely to remain so for some considerable time. It is important to understand the reasons for the differences that might arise when comparing ODN orthometric heights with those obtained from modern gravimetric geoid models. These discrepancies might be as much as 1 metre, although the disagreement in in equation (2) is unlikely to exceed a few centimetres. There are three reasons for this:

  • The ODN model assumes that mean sea level at Newlyn coincided with the Geoid at that point at the time of measurement. This is not true – the true Geoid is the level surface that best fits global mean sea level, not MSL at any particular place and time. MSL deviates from the Geoid due to water currents and variations in temperature, pressure and density. This phenomenon is known as sea surface topography (SST). This effect is important only in applications that require correct relationships between orthometric heights in more than one country; for all applications confined to Britain, it is irrelevant. The ODN reference surface is a local geoid model optimised for Britain, and as such it is the most suitable reference surface for use in Britain.

  • Due to the ODN geoid model only being tied to MSL at one point, it is susceptible to ‘slope error’ as the lines of spirit levelling progressed a long distance from this point. It has long been suspected that the whole model has a very slight slope error, that is, it may be tilted with respect to the true Geoid. This error probably amounts to no more than twenty centimetres across the whole 1000 km extent of the model. This error might conceivably be important for applications that require very precise relative heights of points over the whole of Britain. For any application restricted to a region 500 km or less in extent, it is very unlikely to be apparent.

Eastings and northings

The last type of coordinates we need to consider is eastings and northings, also called plane coordinates, grid coordinates or map coordinates. These coordinates are used to locate position with respect to a map, which is a two-dimensional plane surface depicting features on the curved surface of the Earth. The ‘map’ might be a computerised geographical information system (GIS) but the principle is exactly the same. Map coordinates use a simple 2-D Cartesian system, in which the two axes are known as eastings and northings. Map coordinates of a point are computed from its ellipsoidal latitude and longitude by standard formulae known collectively as a map projection. This is the coordinate type most often associated with the Ordnance Survey National Grid.

It is clear that any position uniquely described by latitude, longitude and ellipsoid height can also be described by a unique triplet of 3-D Cartesian coordinates, and vice versa. The formulae for converting between these two equivalent systems are given in .

It is important to remember that having converted latitude and longitude to Cartesian coordinates, the resulting coordinates are relative to a set of Cartesian axes that are unique to the coordinate system concerned. They cannot be mixed with Cartesian coordinates associated with any other coordinate system without first applying a transformation between the two systems (see ' and ). When considering using coordinates from different sources together, beware that one named coordinate system can have several different realisations (see ), which are not necessarily compatible with each other.

Similarly, having converted Cartesian coordinates to latitude, longitude and ellipsoid height, the resulting coordinates are relative to the ellipsoid chosen, and also to the Cartesian reference system of the input coordinates. They cannot be used together with latitudes, longitudes and ellipsoid heights associated with any other ellipsoid or coordinate system, without first applying a suitable transformation (see ).

H=h+N(1)H=h+N (1)H=h+N(1)
∆hAB=hB−hA=∆HAB−∆NAB(2)∆h_AB=h_B-h_A= ∆H_AB-∆N_AB (2)∆hA​B=hB​−hA​=∆HA​B−∆NA​B(2)

What does it mean to continue mean sea level under the land? The answer is that the surface shown as a dotted line in the figure above is actually a local geoid model. The lower-case ‘g’ indicates a local geoid model as opposed to the global Geoid, as discussed in . It was measured in the first half of the 20th century by the technique of spirit levelling from the Newlyn reference point, which resulted in the ODN heights of about seven hundred thousand Ordnance Survey bench marks (OSBMs) across Britain, the most important of which are the two hundred fundamental bench marks (FBMs). Hence, we know the distance beneath each bench mark that, according to the ‘ODN geoid model’, the geoid lies. By measuring the ellipsoid height of an Ordnance Survey bench mark by GNSS, we can discover the geoid‑ellipsoid separation N according to the ODN model at that point.

Most importantly, we have the errors that can be incurred when using bench marks to obtain ODN heights. Some OSBMs were surveyed as long ago as 1912 and the majority have not been rigorously checked since the 1970s. Therefore, we must beware of errors due to the limitations in the original computations, and due to possible movement of the bench mark since it was observed. There is occasional anecdotal evidence of bench mark subsidence errors of several metres where mining has caused collapse of the ground. This type of error can affect even local height surveys, and individual bench marks should not be trusted for high-precision work. However, ODN can now be used entirely without reference to bench marks, by precise GNSS survey using OS Net in conjunction with the National Geoid Model OSGM15. This is the method recommended by Ordnance Survey for the establishment of all high-precision height control. See the page for more details.

A map projection cannot be a perfect representation, because it is not possible to show a curved surface on a flat map without creating distortions and discontinuities. Therefore, different map projections are used for different applications. The map projections commonly used in Britain are the Ordnance Survey National Grid projection, and the Universal Transverse Mercator projection. These are both projections of the Transverse Mercator type. Any coordinates stated as eastings and northings should be accompanied by an exact statement of the map projection used to create them. The formulae for the Transverse Mercator projection are given on the and the parameters used in Britain are on the .

In geodesy, map coordinates tend only to be used for visual display purposes. When we need to do computations with coordinates, we use latitude and longitude or Cartesian coordinates, then convert the results to map coordinates as a final step if needed. This working procedure is in contrast to the practice in geographical information systems, where map coordinates are used directly for many computational tasks. The Ordnance Survey transformation between the GNSS coordinate system and the National Grid works directly with map coordinates – more about this on the .

Converting between 3D cartesian and ellipsoidal latitude, longitude and height coordinates
Myths about coordinate systems
The shape of the earth
Ordnance Survey coordinate systems
Transverse Mercator projections page
Datum, ellipsoid, and projection information page
geodetic transformations page
We need a datum
We need a datum
Realising the datum definition with a terrestrial reference frame
Geodetic transformations
We need a datum
An ellipsoid with graticule of latitude and longitude and the associated 3-D Cartesian axes. This example puts the origin at the Geocentre (the centre of mass of the Earth) but this is not always the case. This system allows position of point P to be stated as either latitudeφ , longitude λ, and ellipsoid height H or Cartesian coordinates X, Y and Z – the two types of coordinates give the same information.
Ellipsoid height H and orthometric height h of two points A and B related by a model of Geoid-ellipsoid separation N.
A simple representation of the ODN height of a point p – that is, its height above mean sea level. The dotted MSL continued under the land is essentially a geoid model.
The relationship between the Geoid, a local geoid model (based on a tide-gauge datum), mean sea level, and a reference ellipsoid. The ODN geoid model is an example of a local geoid model.
An ellipsoid with graticule of latitude and longitude and the associated 3-D Cartesian axes. This example puts the origin at the Geocentre (the centre of mass of the Earth) but this is not always the case. This system allows position of point P to be stated as either latitudeφ , longitude λ, and ellipsoid height H or Cartesian coordinates X, Y and Z – the two types of coordinates give the same information.
Ellipsoid height H and orthometric height h of two points A and B related by a model of Geoid-ellipsoid separation N.
The relationship between the Geoid, a local geoid model (based on a tide-gauge datum), mean sea level, and a reference ellipsoid. The ODN geoid model is an example of a local geoid model.
A simple representation of the ODN height of a point p – that is, its height above mean sea level. The dotted MSL continued under the land is essentially a geoid model.