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
  • Drive and walk time analysis
  • OS Multi-modal Routing Network (OS MRN)
  • Processing
  • Filtering the data to be suitable for walking
  • Routing
  • Visualising the output
  • Benefits

Was this helpful?

  1. Tutorials
  2. GIS

Walktime analysis using OS Multi-modal Routing Network and QGIS

PreviousBasic routing with OS Open Data and QGISNextCreating 3D Symbols for GIS Applications

Last updated 1 month ago

Was this helpful?

Drive and walk time analysis

Drive and walk time analysis are concepts used to determine which locations are accessible from a point, within a certain time or distance, either on foot or using a vehicle. This is based on a network, as opposed to a straight line ‘as the crow flies’.

However, this doesn’t only apply to driving on roads. Routing analysis can be undertaken along path, rail/tram or ferry networks.

In this tutorial, we will be focusing on walktime analysis, using the OS Multi-modal Routing Network dataset.

OS Multi-modal Routing Network (OS MRN)

OS MRN is a fully connected routable network. It is made up of road, rail, path and ferry networks and therefore dedicated for multi-modal routing .

Processing

  • Find OS MRN on the OS Data Hub and click ‘Add Data Package’.

  • Select your area of interest and choose GeoPackage format.

  • Extract the GPKG file and load into QGIS.

  • MRN is available in the geographic coordinate system, WGS84 (EPSG:4326). The routing plugin wants the network data to be in a projected coordinate system. Therefore, you may need to re-project the dataset to British National Grid (EPSG:27700).

  • MRN contains three feature types: transport_link, transport_node and turn_restriction. In this example, we will be using the transport_link.

The data contains various attributes which indicate what type of transport can use a particular link (e.g., on foot, bicycle, coach). As a result, you can filter the data by these attributes, to keep only the links that are suitable for your mode(s) of travel.

In this exercise, we will do this for walking, but the filtering steps would be the same for other modes of travel.

Filtering the data to be suitable for walking

For this analysis, we are only interested in routes that are navigable on foot.

· In QGIS, right click on the transport_link layer and select ‘Filter’.

· In the ‘Provider Specific Filter Expression’ section, copy and paste the following code

· "foot" = 'designated' OR "foot" = 'yes'

We only want the transport links which have values of ‘designated’ or ‘yes’ under the ‘foot’ attribute, denoting them as being accessible by pedestrians, to be included in the analysis.

You will also need a point dataset, which the routing tool will use as starting points for the analysis. The one used here contains two starting points.

Routing

QGIS has built in tools for network analytics such as service area and shortest path. However, for a visually clearer output, we will be using a plugin called QNEAT3.

Select ‘Plugins’ > ‘Manage and Install Plugins’ and search for ‘QNEAT3’. Select ‘Install Plugin’.

Once the plugin is installed, it will appear in the processing toolbox. The tool offers various analysis options, but for now select QNEAT3 – Qgis Network Analysis Toolbox > Iso-Areas > Iso-Area as Polygons (from Layer).

Populate the fields as shown below (However, feel free to experiment with your own values!).

The ‘size of Iso-Area (distance or time value)’ field allows you to specify the max distance or time (in seconds) for the walktime analysis. In this exercise, we have specified a max walktime of 3,600 seconds (60 minutes), with intervals of 900 seconds (15 minutes).

As this analysis is for walking, we can accept the default speed value of 5 km/h, further down in the menu. If you were to conduct analysis using different modes of travel, MRN does include average road speeds.

If you wish to save the output polygon, you can do so at the bottom of the menu.

Once you are happy, select ‘run’.

Visualising the output

Right click the output polygon and select ‘Properties’.

· Select ‘Symbology’

· At the top, select ‘Categorised’

· In ‘Value’, select ‘1.2 cost_level’

· Select a suitable colour ramp

· Select ‘Classify’

· Untick the symbol for ‘all other values’

Add a base map of your choice. We have used the OS Maps API Light Style and made it slightly transparent so that the walktime analysis output polygons show underneath.

We have also converted the cost level from seconds to minutes in the legend.

Benefits

  • Analysis using multiple modes of travel possible by manipulating one dataset

  • Compatible with open-source software and plugins

  • Simple routing analysis using this data is straightforward

  • Versatile dataset- research of various contexts for different use cases possible

OS Multi-modal Routing Network | OS Download Products' Documentation
Logo
Walk times shown over the OS Maps API Light style