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
  • What is map scale?
  • Commonly used scales at OS are:
  • When to include a scale bar
  • Scale on digital maps
  • Scale bar design and placement

Was this helpful?

  1. Geographic Data Visualisation
  2. Guide to cartography

Scale

PreviousProjectionsNextMap legends

Last updated 10 months ago

Was this helpful?

All maps are reduced (scaled down) versions of the real world, but what scale to use will depend on the purpose of the map and the user’s requirements, relating to what features need to be included, the size of the area of interest and the paper (or screen) size. Also, not all maps need, or should have, a scale bar as we’ll discuss below.

What is map scale?

Scale is represented as a ratio of the map distance to the ground distance. For example, a scale of 1:100 means that one unit on the map represents 100 of the same units on the ground. Let’s say a road is 10,000cm long (100m) and you want to represent the same road as 10cm on the map, the scale can be calculated by dividing the real-world distance by the map distance. In this case giving 1,000. The scale is therefore 1:1,000 with 1cm on the map representing 1,000cm on the ground.

Commonly used scales at OS are:

1:10,000 where 1cm on the map = 10,000cm on the ground (100m)

1:25,000 where 1cm on the map = 25,000cm on the ground (250m)

1:50,000 where 1cm on the map = 50,000cm on the ground (500m)

The scale of a map is often represented by a ratio (e.g. 1:10,000) or as a statement in words such as ‘one inch to one mile’ but is also often represented by a scale bar, allowing users to visually assess distances on the map. A statement in words or ratio only hold true for a printed map if the print size is controlled. Any map that is enlarged or shrunk when printed will render the statement and ratio incorrect.

The choice of map scale is intrinsically linked to the purpose of the map and what it needs to show, to meet the users’ requirements. For example, if you are planning a driving route around Scotland, you’ll want a map which shows a large area (possibly the whole of Scotland) but don’t need details of every building, bus stop, and café. This is known as a small-scale map. On the other hand, if you are making a map for a walking tour around a village, you would want a map of a small area but with lots of detail. This is known as a large-scale map.

To explain small scale and large scale a bit better and help you get your head around it:

  • Small scale maps require a small sheet of paper to show an area with a smaller amount of detail.

  • Large scale maps require a larger sheet of paper for the same area and show a much larger amount of detail.

When to include a scale bar

Scale on digital maps

Digital zoomable maps are slightly different as the scale varies dependent on the level of zoom. You also don’t know what screen size your user will be viewing your map on – it could be a phone or it could be a wide-screen monitor. As such, a statement that 1cm on the map = 25,000cm on the ground won’t work. As such, on digital maps, scale bars are the best way to indicate scale. On a slightly separate note, when designing a zoomable map, think carefully about what features show at each zoom level, taking care not to clutter your map.

Scale bar design and placement

Scale bars should be designed so that they are simple and easy to read and understand. Their design, in terms of the look and feel and complexity, should be in keeping with the design of your overall map. For example, a simple locator map probably only needs a simple scale bar. It is up to the cartographer as to whether the scale bar is metric or imperial, or includes both distance conventions. It is general practice to place the distance values above the scale bar, ensuring that the maximum illustrated values are round e.g. 1000m to allow easy halving and distance estimation. A distance of 973m is hard work with – what’s half of 973? Or even worse….. 753.3m. Including various intervals can also help users to estimate distances.

Similar to north arrows and data sources, scale bars should be subtle and should not attract too much attention. They should appear relatively low in the visual hierarchy of the map but should be easy to locate and use if required by the user. This can be achieved by keeping the linework relatively fine and the text relatively small (but still readable). It is best practice to place the scale bar somewhere close to the mapped area (but not a hard-fast rule), where the user can easily use it to relate the scale bar to distances on the map. Generally, it is placed below the mapped area, where the user is likely to be accustomed to finding it but is often also placed with the title or the legend. Take care when placing a scale bar if you’ve got inset maps, making sure that the scale bar doesn’t look too much like it relates to the inset map. Your inset map may need its own scale bar.

As mentioned earlier, scale has a huge impact on what features we show and how the same feature might be depicted differently at different scales. For example, take an airport: on a large-scale map, you would show the airport boundary, runway detail, buildings, car parks and more. However, on a small-scale map, you would perhaps only show a single point symbol. Linked to scale is the process of which is the process a cartographer (or more recently, a computer algorithm) undertakes to alter the way in which features are represented in order to maintain legibility as the map scale decreases.

Explore map scales further here:

Not all maps need a scale bar, particularly if it is of a familiar area or is at the continent or global scale. The distortion to distance caused by a map means a scale bar (or ratio, or statement in words) placed on a map covering large regions or countries may only be correct for one line on the map. On maps at these scales, scale bars are either omitted, a statement is made that the stated scale is only correct along a certain latitude or longitude (such as the equator), or a variable scale bar could be used which shows graphically how scale varies across the map. Scale bars are also sometimes omitted from thematic maps where scale is not important to the message or theme of the map. As a general rule however, scale should be indicated on most large scale maps to aid user understanding.

generalisation
A beginners guide to understanding map scales
projection
Map scale
Scale bar