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

Was this helpful?

  1. Deep Dive
  2. Guide to routing for the Public Sector

Part 1: Guide to routing

PreviousGuide to routing for the Public SectorNextPart 2: Routing software and data options

Last updated 1 year ago

Was this helpful?

Several public sector organisations use network data for optimising refuse collection routes, school transport and reorganisation of the locations of key services. Several case studies have been published demonstrating significant cost savings. As a result, more organisations are seeking to reduce costs by better use of network data. This has raised awareness of the benefits of using route analysis, and this document provides a guide to route analysis aimed at helping users understand what it is and how to get started.

Route analysis can be used to answer questions such as

  • Where is my nearest library?

  • What is the most efficient route for my deliveries?

  • Which is the best location to build a new office?

When considering these questions, a simple radius search using a buffer zone can be used to find objects within a set distance of a feature. For example, a school needs to know how many addresses are within a 1 km catchment area. The image on the left shows all the addresses highlighted within a radius buffer however addresses on the opposite side of the river are included.

To improve this analysis, the road network can be used to give a more accurate picture. Generating a polygon based on 1 km driving distance creates a better representation, returning fewer addresses as shown on the right. This demonstrates that route analysis provides a more effective method for defining catchment areas, managing location-based services and answering the questions listed earlier.

Route analysis uses either road or path networks to determine the driving or walking distances, or time, between objects and can be used to solve complex problems. These include, but are not limited to, where is my nearest facility, what is the optimal location for a new business. There are different types of analysis that can be performed on data. These are:


A to B route generation

How do I get from point A to point B? This is the simplest form of routing and is in common use in web mapping applications giving details of how to travel between 2 points, the distance and estimated journey time. Journey times can also take into consideration the type of transport used, e.g. car, bus, cycle, or by foot. Start and end points could be a grid reference, address, post code or a place name. The example shows a journey between Cardiff and Cwmbran using the quickest route and includes directions. However, it is also possible to set options to include certain types of road or go via another place en route, this is often referred to as Travelling Sales Person (TSP)


Travel time

Travel or drive time analysis is used to define how far can be traveled in either a set time or over a set distance. It works by creating a series of irregular or Voronoi polygons for each point on a network, each polygon represents either distance or timed traveled. Although it is often referred to as drive time, it can also be used to model walking or cycling time as well. The results are displayed as a series of isochrones, either as polygons or lines. This type of analysis is used to show what is within certain distances of a specific point. For instance, a hospital may want to know how many patients live within a certain travel time to the facility to help with service planning.


Closest Centre

Closest centre analysis is used to calculate the cost of travelling between several locations from a fixed point (or points) determining which are nearest to each other. The resulting analysis includes a rank of the points and corresponding locations based on the time to travel between them. This can be used for assigning the closest resource to a specific location, such as emergency responders to an incident. This analysis can also be used to help plan the location of resources such as bus stops. The example shows the location of people without cars on a housing estate and the closest bus stop to each.


Cost matrix

An origin-destination cost matrix measures the distance across a network that costs the least to travel (or least cost path) form either a single or multiple origin to multiple destinations. The results are displayed either as a table or a spider diagram linking the origin to destinations with a straight line. This type of analysis is useful when large volumes of data need to be analysed.

Using the bus stop example, it’s important to identify the distances to all stops in the area from a specific location, as we need to understand the impact of changing a route. The table shows the distance to each location ranked from closest to furthest displayed graphically as series of lines.

For more information on OS Select+Build and the OS data available to developers, business, and government, visit the .

OS Data Hub
1 km straight line buffer
1 km driving distance
A to B routing
Travelling sales person routing
Five, ten and fifteen minute travel times from Cardiff (road speed has not been incorporated).
Closest centre analysis
Cost matrix analysis
Page cover image