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
  • Things to remember when giving critique
  • Useful criteria to remember when giving critique

Was this helpful?

  1. Geographic Data Visualisation
  2. Guide to data visualisation

Data visualisation critique

PreviousThematic mapping techniquesNextAccessible data visualisation

Last updated 11 months ago

Was this helpful?

Critique is a really powerful way of making better maps and data visualisations, and a useful tool in any visualiser’s arsenal. It’s not about picking holes in a map or data visualisation – but instead more of a holistic look at the overall design and message. Sometimes it can feel awkward or harsh, but when done right it is simply a constructive helpful tool. After all, once you’ve done all the data collection, cleaning, prep, analysis and ultimately visualisation, you don’t want all your work to go to waste if people then don’t engage with what you’ve made!

It's important to remember too that not everybody has access to critique – such as people who work on their own as a freelancer, or don’t have any colleagues with geographic data visualisation knowledge. Therefore, having the ability to get your work critiqued is a privilege and can even give you an advantage.

Things to remember when giving critique

When delivering critique to someone, it can also be helpful to frame it between some things you like about the piece This helps to keep the critique constructive, whilst also highlighting the good work which has gone into the map or data visualisation.

Here are some more tips to keep in mind when delivering critique to somebody:

  1. It’s Not About You – keep your points focused on the map and how the designer can improve or alter it to better serve it’s purpose. The map should be critiqued on it’s own merit and not examined by personal bias toward any design element or concept.

  2. Maintain Respect and Honesty - Remember that the map designer has put in a lot of time, thought and care into constructing the design. Honesty is a great tool in a design critique. The designer needs to hear the truth and understand the reasons why a map design is either working or not.

  3. Avoid Meaningless Words and Phrases - It’s much better to have a thorough explanation rather than using vague meaningless phrases like,“the map needs to be more sexy”. Don’t hold back on the description of why something works or doesn’t work — the more info the better.

  4. Be Specific - The point of the critique is to examine the map and see if it meets its intended message and goal. If explanations aren’t specific, the communication of the critique will suffer, and in turn the map and map designer will suffer as well.

  5. Bear in mind the Cartographic Design Principles - Always refer back to our cartographic design principles before entering into any map critique (see ). When giving critique these can be good to centre your points around.

  6. Ask Why - A good map critique should ask questions like “Why did you use the darker shade of blue for your water fill versus a lighter one?”. This kind of questioning allows the map designer to verbally explain why a decision was made and allows for a better understanding of the map and the design choices made.

  7. Offer Suggestions - Suggestions should be welcome but this goes along with point number two above: be respectful and honest. Be respectful with your suggestions and make sure that you don’t just try to implement your own personal style or design ideas.

Useful criteria to remember when giving critique

Purpose

Designing the concept of a map is where you should ideally begin and those ideas are driven by the maps purpose. What is the map's intention? Is it achieving it?

Content

Is the content right? Is the data right? Has any analysis been done correctly? There is nothing worse than spending a lifetime perfecting and refining your map only to find out you have the wrong data!

Projection

Remember the Earth is curved. Map projections flatten our curved Earth and always add distortion. They transform the sphere on a plane. So, has the best map projection been used to represent the chosen map? Has the correct map projection been used for the map's intended medium?

Method
Legend

Legends tell the map reader what the polygons, lines and points represent. They are one of the most important map elements to consider during map making. Does the legend depict everything it should? Does it depict too much? Where is the legend? Is it in the way? Too big? Too small?

Colour

Colour catches the eye. Its used to clarify features. Are the colours right? Is water blue? Should it be blue? Is the palette colour-blind friendly?

Layout

How does the overall map look? Do all the elements of the map work together?

Title

Does the map title reflect the purpose of the map? It usually should include the map's theme and geographic location

Labels, Fonts, Symbology

Labels should be placed with purpose. Is the map cluttered with labels? Make sure they are readable and that the most appropriate fonts, colours and sizes are used. Don’t use gimmicky fonts just because you can. Stick to tried and tested. Are the symbols easy to interpret? Are they depicted at the correct scale?

Scale

A scale bar is a map element that graphically shows the distance of units on a map. Does the map have one? Does it need one?

Have they used the correct mapping technique? This is especially relevant to where the technique used is really important.

here
thematic mapping