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
  • Spot heights
  • Contours
  • Hypsometric tints
  • Hill shading
  • Hachures
  • Digital

Was this helpful?

  1. Geographic Data Visualisation
  2. Guide to cartography

Relief representation

PreviousMap layoutNextNorth arrows

Last updated 10 months ago

Was this helpful?

Relief is important to many map users and is represented, in one form or another, on most topographic and some thematic maps. As a continuous 3D surface, it presents challenges to cartographers seeking to represent it in a graphical format, particularly in the form of a 2D map. Obviously with developing technology, 3 dimensional digital models are now possible. Here, however, we will focus on relief representation in 2 dimensions (i.e. on a flat map).

Even on very early maps, relief formed a key part of the composition and was commonly represented by drawings of hills and mountains. Although this did indicate the presence of hilly or mountainous terrain, it did not show very accurately the spatial extend of the hills, their height, how slope varied across them, how valleys dissected them or what other features existed within the hills in much detail. Maps now commonly use one of, or a combination of, spot heights, contours, hachures, hypsometric tints and hill shades to represent relief. Each one has its pros and cons and which technique to use will likely depend on the scale of your map and the user requirements.

Spot heights

Elevation can be measured and defined at a single point and expressed numerically as a height above or below a datum (for most people, it is best understood as a height above or below sea level). Spot heights can provide an accurate measure of elevation at a single point and are often represented by a small point symbol labelled with its elevation. Spot heights are best placed at critical points in the terrain such as the top of peaks, the bottom of depressions, on passes/saddles, at major path or road junctions and close to points of interest. Just using spot heights to represent relief however, can present a challenge to the user in visualising the terrain and how it changes between two defined points. Spot heights are therefore best used in combination with another form of relief representation.

Spot heights can be particularly useful on nautical or aeronautical charts where the user may need to know the absolute height (or depth) of certain features as this will likely influence whether they can safely pass over an area or not. For example, knowing the exact height of a mountain peak or the minimum depth of a water body.

Contours

How contour lines show a pair of small hills

How contour lines show a pair of small hills Steep slope - contours are close together

The vertical interval of contours will depend on the scale of the map but also the vertical variation within the area of interest. Areas with large vertical variation will likely require larger contour intervals (e.g. 50 or 100m intervals) than a flatter area which may need smaller vertical intervals (e.g. 5 or 10m intervals) in order to show variations in the terrain. Take care not to set your contour interval so small that they start to clutter the map and make it difficult to read and interpret.

Contours generally have an index contour, which occurs every 4/5 contours and is usually represented by a slightly thicker line. For example, for a 10m contour interval, the index contour might be every 50m (every 5th contour). This allows for better terrain visualisation and easy contour counting and tracing by the user. Contours, particularly index contours, should be labelled to aid user understanding. Labelling is best achieved by breaking the contour and placing the contour value in line with the contour, with the bottom of the number facing downhill. Contour numbers can either be placed in a ladder format or spread across the map such that if the height of a contour is to be determined by a user, a numbered contour is never that far away.

One of the key issues with contours is that on very steep slopes, contours can coalesce. Contours should never touch, so in these areas, contour lines are often broken to maintain legibility and may be replaced by steep slope or cliff symbols/ rock drawings if appropriate. The contour lines at the top and bottom of the slope and index contours should be retained where possible to do so.

Despite their common use across maps, many users find difficulty visualising the 3-dimensional nature of terrain that the contours are representing. Contours are sometimes used in combination with other methods of relief representation such as spot heights, hypsometric tints or hill shading to aid user understanding and visualisation of terrain.

Hypsometric tints

An alternative way of representing relief is via hypsometric tints/ layer colours which essentially classifies the terrain into elevation bands (area symbols). Typically, the intervals between the layers are greater than would be used for contours on a traditional topographic map. Hypsometric tints are often used where representation of relief is important to the overall purpose of the map when relief needs to be shown over large areas. As such, hypsometric tints are commonly used on small scale maps.

Various approaches exist in terms of the representation of elevation using hypsometric tints. Stepped layers can be used where a small number of layers are used with medium contrast between the layers. Alternatively, continuous/semi-continuous layers can be designed which use a large number of layers and the colours may blend from layer to layer. Both approaches are valid.

A popular colour ramp approach when using a single hue is a ‘higher the lighter’ approach – this is due to the eye visually perceiving lighter colours as being closer to the user, and therefore perceived as being higher. If using this method, care must be taken that the lower elevations aren’t so dark that other features, which are often located in the low points in the landscape, are not visible.

Other considerations in terms of hypsometric tint colours include considering the characteristics of the landscape you are mapping. For example, greens are often used for lower elevations, but this may not be appropriate for arid environments where a colour ramp using yellows, oranges and browns may be more appropriate. Similarly blues could be used for water environments.

Although hypsometric tints may help users to better visualise the terrain in 3 dimensions than contours, it is often the case that hypsometric tints are combined with hill shading to really help give an impression the terrain in 3 dimensions.

Hill shading

Hill shading is a technique used by many to really bring terrain to life and can really help users to visualise terrain in 3 dimensions on a flat map. Hill shading is based on the amount of light falling on a surface from a defined light source. This technique essentially illuminates surfaces that are facing the light source and making those which face away from the light source appear to be in shadow. The light source is normally positioned to the north-west.

Although hill shades represent slopes well, they do not show elevation very effectively. As such, hill shades are often combined with contours or hypsometric tints to better represent slope and elevation.

Hachures

Hachures are seen on many older maps, including the first Ordnance Survey Map of 1801, and are a pattern of lines which run parallel to the direction of the steepest slope. The length of the lines varies dependent on the length of the slope they are representing and steeper slopes are often depicted using thicker lines, or more densely spaced lines. The main downside of hachures is that they can make the map image quite heavy if there are lots of them and they can also clutter the map and overprint other features.

Digital

More recently, digital methods of representing relief have become common. These include the creation of digital terrain or digital surface models or triangulated irregular networks, which model the terrain in 3 dimensions. These 3D models are often created using a combination of aerial photography and/or LIDAR data.

Contours are a form of isoline; lines of constant height above or below a datum (often defined as sea level). They are commonly used on maps and are generally drawn in a neutral colour so that they are visible and usable but do not overpower other features on the map or visually influence the overall look and colour of the map. Generally, contour lines have equal vertical intervals and thus the spacing between contours indicates slope. Closer contours indicate a steeper slope whilst spread out contours represent shallower slopes. Read more about how to read contour lines .

Care should be taken when choosing your colour ramp as the colours will have a major effect on your map design and, due to the way in which colour is perceived by the human eye, the colours can also have a big influence on the meaning of your map. Colours should be sequential (see our section ) and can be of a single hue (dark to light) or of multiple hues. Common colour sequences using multiple hues start with greens and yellows in lower areas up to oranges and browns and maybe even purples and whites in higher areas.

here
colour
Spot heights
How contour lines show a pair of small hills
Shallow slope - contours are spaced well apart
Steep slope - contours are close together
Contours with a ladder approach to labelling
A hypsometric tint with a darker to lighter colour ramp combined with hill shading