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
  • Points, Line and Polygons
  • Text
  • Making your map legible

Was this helpful?

  1. Geographic Data Visualisation
  2. Guide to cartography

Symbology

PreviousTypes of mapsNextColour

Last updated 10 months ago

Was this helpful?

Maps are graphic or symbolised representations of the real world. No map can show everything in the real world, as it would be really cluttered and confusing. As such, maps show just a selection of features dependent on the purpose of the map and the intended audience.

Once the data has been selected, based on the users’ requirements, symbolisation is the way in which that geographical data is classified and represented on a map. It is extremely important to the overall visual impact of the map, and how good the map is at meeting the needs of the user.

Geographical features and phenomena can generally be represented as points, lines, or polygons. Text may be included in the form of a label. Together, these are known as the ‘graphic elements.’ It’s a cartographer’s job to decide how each feature is represented. This will likely depend on the purpose of the map, and the map scale. For example, a river might be shown as a polygon on a map of a town centre, but as a simple line on a national topographic map. Similarly, a city might be shown as an area with a boundary full of buildings, car parks, and greenspaces, but in an atlas shown as a single point (more on generalisation can be found).

In order to make maps clear and legible, it’s important that the symbols are styled in a sensible way to make the map easy to understand. This is done by changing what is known in cartography as the ‘graphic variables.’ These include changing the size, shape, colour, lightness, orientation, and pattern of points, lines, and polygons. They can be applied in isolation, or used in combination depending on what you are trying to show. Text is then used to add meaning or context to the map, if required.

Points, Line and Polygons

When designing point symbols, it is important to think about what they are representing. Points can be represented simply by a geometric shape such as a circle, square, or triangle. Or points can be represented by conventional symbols such as a red cross for a hospital or an ‘i’ for information point. Alternatively point symbols can be mimetic i.e. they look like the object they are representing, such as an aeroplane for an airport or a picnic bench for a picnic site. Conventional and mimetic symbols can be used to enhance a map and give it meaning, making certain features immediately identifiable to the user without them needing to refer to the legend. On OS maps, we commonly use conventional and mimetic point symbols.

Lines can be varied in many ways, such as being dotted or dashed, and are often quite complex. Roads, for example, can be made up of a road casing with a coloured fill. Using colour can help add meaning to your map, particularly if conventional colours such as blue for water are used. Lines representing the same feature class (e.g. roads) can be varied in colour and size to reflect their relative importance. For example, a motorway would be shown to be wider than a minor road. These principles can be applied to thematic maps too, where lines can be varied in their colour, thickness or form (dotted, dashed etc.) to represent varying phenomena.

Polygons often form the background to a map but may be important symbols in their own right. Polygons can be filled with a solid colour or with a texture or pattern. The colour of polygons can be altered to give meaning to a map, particularity by using conventional colours, such as green for woodland, brown for mud, yellow for sand, and blue for water. Patterns such as trees or marsh symbols can be added to polygons to further aid user understanding and improve legibility for those who perhaps suffer from forms of colour vision deficiency. The lightness of polygons can also be altered to give a visual order to ordered or quantitative data, such as in a choropleth map where darker colours indicate a higher value or occurrence of something.

Text

Text is often categorised as another type of map symbol and, if used effectively, can add meaning to a map and help users understand what they are looking at. However, poor use of text can detract from the map, making it cluttered and difficult to read.

Making your map legible

These graphic variables can be manipulated to help create a visual hierarchy within the map, ensuring that the key information (figure) stands out, whilst other information recedes down the visual plane and into the background (ground). This is commonly referred to as the figure-ground relationship. More information on creating an effective visual hierarchy and the figure-ground relationship can be found .

Another thing to think about with point symbols is how their size can be varied to show the relative importance or size of a feature. For example, when using a point for a place, the symbol for the city could be made larger than that of the same symbol for a village. On thematic maps, points are often used to represent the occurrence of something – for example on a Dot Density map or a Proportional Symbol map. On the latter, the size of the symbol is varied in relation to a value. Read more about here.

More information about the effective use of text on maps and data visualisations can be found .

Designing your symbols in isolation may be easy but what makes the map effective is how all the symbols work together. Your map must be legible for effective communication to the user; this is one of our core . This can be achieved by ensuring sufficient contrast between features, such as between text or points over a background fill colour. Insufficient contrast will make the points and text difficult to read. Contrast between features of the same type might also be important, such as making sure the colours used in a choropleth map are perceptually different. You can read more about use of colour and legibility . Finally, features, particularly point and line symbols should be large enough for the user to see with ease but not so large that they begin to overpower the map or overlap with other features. For really effective communication and exploration of your map, it should be visually appealing with colours which work in harmony with each other (not jarring to look at) and a good visual hierarchy.

here
thematic mapping techniques
here
design principles
here
here
Extract of Ordnance Survey 1:25 000 Explorer Legend
Ordnance Survey 1:25 000 Explorer Legend
Ordnance Survey 1:25 000 Explorer Legend