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
  • Example 1: The Y axis
  • Example 2: Visualisation method and use of colour

Was this helpful?

  1. Geographic Data Visualisation
  2. Guide to data visualisation

Ethical data visualisation

PreviousAccessible data visualisationNextSoftware

Last updated 11 months ago

Was this helpful?

There’s a common saying – “A picture can paint a thousand words” – and in a way, it’s true, good data visualisations can effectively summarise and communicate a message that would take many words to describe or explain. Humans also process visual information much faster than written information and retain the information for longer. So, there is no doubt that data visualisations are powerful ways to communicate information. However, they need to be used wisely and ethically, as they can also be used to misinform and sometimes don’t show the whole picture.

When creating a data visualisation, ask yourself the following questions:

  • Is my data from a reliable and trustworthy source?

  • Is there likely to be any inherent bias in the dataset?

  • What is the message of the data visualisation and is that what the data shows?

  • Does the visualisation method and/or colours used communicate a certain feeling/sentiment, and is that ok?

  • Is the projection used appropriate? Could this lead to misinterpretation of your data?

  • Could your data visualisation be misunderstood in any other way?

When viewing maps or data visualisation created by others, it’s also worth being aware that, although they may be informative, they have still been created by someone who has their own agenda and story to tell. They may not be without bias. Ask yourself:

  • What is the data source and who created the visualisation? Why might they have created the visualisation?

  • Is the visualisation potentially missing key information or oversimplifying something?

  • Are the visualisation method or colours used altering your perception of the topic?

We explore a few examples below of how data visualisations could be used to misinform.

Example 1: The Y axis

It is more common than you might think that graphs and charts are manipulated to tell a specific story; to either exaggerate or minimise a trend. Often stretching or shortening the y axis, or even truncating the y axis can give a very different picture of the same data and tell a very different story. So, think carefully about your data and whether the way you’re presenting it is honest and a true representation of the data.

Example 2: Visualisation method and use of colour

The way in which data is visualised can have a huge impact on the sentiment of the story you are telling. A good example of this are maps showing migrant movements resulting from war or natural disaster. These maps have historically (and still to this day if we look at maps portraying migrants fleeing Ukraine), used large arrows showing the movement of people from the effected country or region to other countries. These arrows are often depicted in red. So, what are the implications of these design decisions?

Firstly, the use of arrows. Arrows have been used historically in battle maps, showing the movement of invading forces. Using similarly styled arrows to show the movement of migrants into neighbouring countries makes it look as though these receiving countries are being ‘attacked’. Is this the message you intended to give across?

Now to the use of red. Red is an emotive colour and one we associate with danger (among other things). This paints migrants as being dangerous and alarms the viewer. Is this a fair representation? Could another colour be used to change the sentiment of the visualisation and present the data in a more neutral way?

Minimising the effect data trend by stretching the y-axis on a graph
Emotional effect of colours used in a visualisation