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
  • Key points
  • What to include
  • How to lay out a legend
  • Legend placement
  • Considerations for web and mobile maps

Was this helpful?

  1. Geographic Data Visualisation
  2. Guide to cartography

Map legends

PreviousScaleNextMap layout

Last updated 9 months ago

Was this helpful?

An important part of most maps is a legend (or key) which provides an explanation of the symbols on the map and helps the map user to understand and interpret the map. A well-designed, logically presented legend will help achieve effective map communication.

Key points

It is really important when putting together a legend that the size, shape, colour and orientation of symbols in the legend are identical to those on the map. In addition, the text explaining the symbol in the legend must be kept close to the symbol itself (or linked using a series of dots or a line) so that there is no doubt which symbol the descriptive text relates to.

What to include

Which symbols to include in the legend will depend on the purpose of the map. On general purpose topographic maps, such as the Ordnance Survey 1:25 000 and 1:50 000 series maps, all features are included in the legend. On thematic maps however, self-explanatory symbols forming part of the basemap can often be omitted from the legend. This might include omitting features such as rivers, roads and the coastline if they just provide background context and their meaning is clear and does not require further explanation. If you have any overlays of data, it is imperative that all symbology describing these are included in the legend to aid user understanding.

Think about the user and what they are going to use your map for. What might they want or need explained? If the user was seeing your map for the first time, would they understand what everything was? If any feature is key to the message, use or understanding of your map, it should be included in the legend.

How to lay out a legend

Your legend needs to arrange logically so that it is quick and easy for a user to find the feature they are looking for. It is best practice to group related features together. For example, this might be placing all symbols related to railways together e.g. tracks, level crossings and stations or all tourist symbols together or all roads together, like we do for our 25k and 50k mapping series. Within these broad categories, symbols of the same symbol type (point, line or area) should be kept together. If text is used to describe features on a map e.g. a river name or a castle, use the same font type and colour in the legend. Headings and subheadings within the legend can be used to help users quickly locate the feature they’re looking for.

Another popular way of presenting information in a legend, beyond a standard list of features, is in the form of a natural legend where features are shown in context, in a simple map-like representation, showing the spatial relationship between features.

If your data is quantitative, ensure that the legend allows the user to relate the size or colour of features to its value. It is also important that you include the units in your legend as this is easily forgotten e.g. population per km2 or percentage of population.

Legend placement

Considerations for web and mobile maps

On web or mobile maps, where maximising map space is important due to small screen sizes, the legend may need to be hidden in a separate panel to maximise space for your map on the screen. It’s best to ensure that the legend is easy to access via a popup or side panel and that the icon or menu used to access the legend is clear as to what it’s going to do if clicked. A dynamic legend which only shows features which are visible to the user at each set zoom level could also be an option worth considering if space is limited.

Placing the legend on the page can be one of the hardest parts of map design – they can be quite extensive and take up lots of space. Often legends are included in boxes to one side or bottom of the map. However, this doesn’t have to be the case. Legends can just be placed in white space around your main map figure without a bounding box. Either way, the legend should be placed such that the map layout appears balanced. Read more about map layout .

here
Thematic map example
Communications and Access
Tourist and Leisure Information
Water Features
Rock Features
Quantitative map example