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
  • Generalisation Techniques
  • But how do we decide how to generalise things?
  • Computer generalisation

Was this helpful?

  1. Geographic Data Visualisation
  2. Guide to cartography

Generalisation

PreviousText on mapsNextCoordinate reference systems

Last updated 10 months ago

Was this helpful?

As maps represent reality at a very reduced scale, no map, even at large scales, can show everything. It would be totally illegible and very chaotic if we did. This is because there is a reduced amount of space available on a page/screen to represent features compared to the real world and this space reduces as the scale decreases.

Before jumping into generalisation, it is important to think carefully about the purpose of the map, who the user is and how the map will be used, as this will help determine the scale of your map and what features will be required to meet the requirements of the user. The smaller the scale of your map, the less information you’ll be able to show. For example, on a map of the world, you won’t be able to show every building outline or every road. A larger scale map of the same area will require more space, which may not be possible. It’s a balancing act but the general rule is that if the feature is not critical to the purpose or understanding of the map, it should be removed.

Once you’ve decided what features you need on the map, you will likely need to generalise them (reduce their complexity) in order to maintain their legibility when moving to a smaller scale. There are many techniques which can be deployed to achieve this aim. Here are a few of the techniques cartographers use to generalise a map:

Generalisation Techniques

  • Elimination: Removing certain features which are not necessary at the new scale such as removing a small building from a built-up area or removing individual bus stops. It might also include removing certain classes of features such as removing all minor roads and keeping just the major ones – this may not work for every use case as a minor road in a rural area may be more important than in an urban area – selective elimination, at the discretion of the cartographer, may therefore be required.

  • Amalgamation (or combination): The joining together of adjacent objects of the same type, such as merging individual buildings into a single built-up area, or multiple patches of woodland into a single wooded area.

  • Simplification: Makes features legible by removing some of the variation such as smoothing out meanders in a river or removing some of the smaller tributaries of a river network. The key is to maintain the general characteristics of the feature you are simplifying.

  • Exaggeration: Small or narrow features can be increased in size in order to maintain their legibility whilst retaining a defining feature. For example, maintaining a visible opening to a bay or showing roads wider on the map than their true scale to make them visible.

  • Displacement: Moving features apart to ensure clarity, such as moving a road and river apart to prevent them overlapping and create visible separation between the features when the scale is reduced.

  • Collapse: Similar to amalgamation but may result in the change of dimension of a feature such as a polygon to a point symbol. For example, a city may be shown as a polygon at large scales but as a single point at smaller scales. Similarly, dual carriageways shown with a central reservation may be reduced to just a single line road feature.

But how do we decide how to generalise things?

Still to this day, the method of generalisation and level of generalisation is down to the discretion of cartographers. It is a cartographer’s job to understand what the user requirements are and the purpose of the map and then select and symbolise the data appropriately. It is often quite subjective and varies from place to place (and cartographer to cartographer). For example, a small building in an urban area may be eliminated due to its size, however the same sized building in a very rural area, where it is the only building for miles and thus a key feature of the landscape, would be retained. Features are also interrelated, making generalisation complex. For example, if you simplified a river network by ‘smoothing’ out a few of the meanders, the contours would have to be simplified in a way that they match the river network such that rivers appear at the lowest point in the topography and flow downhill.

Successful generalisation ensures that the graphic legibility of features are retained, the general characteristics of the features are retained, and the relative importance of features and the spatial relationships between them are considered.

Computer generalisation

More recently, computer algorithms have been developed which allow automatic generalisation, based on a set of pre-programmed rules. However, the success of these is still quite varied and often human judgement gives more pleasing results.

Generalisation Techniques