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. Tutorials
  2. GIS

Analysing pavement widths

PreviousGISNextBasic routing with OS Open Data and QGIS

Last updated 1 year ago

Was this helpful?

Ordnance Survey (OS) and Transport for West Midlands (TfWM) recently completed a project exploring the creation of pavement widths data. The focus of this project was to support TfWM’s ongoing work in transport planning, road space reallocation and linear referencing.

Following on from the success of the , this piece details the output from that work, illustrating the methodology that can be used to determine pavement widths. This methodology creates transects by using data from the OS National Geographic Database (NGD), accessed using OS’s new personalised and simplified .

Pavement widths and the ability to measure them quickly and accurately has received increasing prominence in recent years. Research from Esri, using measurements from OS, revealed that , making it hard for people to socially distance during Covid-19.

However, the following methodology isn’t just suitable for pavements. Using OS data you can adapt this methodology to calculate widths of other features like rivers, roads and grass verges.

To simplify this the methodology has been broken down into three sections: Data, Published Parameters, and Method Overview. This method uses Feature Manipulation Engine, known as FME (it’s recommended that you have version 2020.0.1.0 or later) and OS NGD data.

OS NGD data is used because of its detailed attribution and ease of filtering pavements and paths from the Transport Features theme. The FME workbench uses OS data in a GeoPackage format.


How to access this OS data:

  1. Create a recipe in OS Select+Build on the OS Data Hub by expanding Transport theme > Transport Features > Road Track Or Path.

  2. Apply a filter to this data to include ‘Path’, ‘Path and Steps’, ‘Pavement’, ‘Pavement and Steps’.

  3. Create the recipe. You will then need to create a data package in a GeoPackage (GPKG) format (as this is what the FME workbench uses) for the area you require. We’ve used GeoPackage because of its plug-and-play nature, but other formats can be used if the workbench is adapted.

The published parameters are variables created to make using the workbench easier and allows values to be easily changed depending on the project. Below is an explanation of each of the parameters, along with their default values. All parameters can be changed by using the dialogue box that appears when you begin running the workbench.


  • AOI name For ease of identification, the user is prompted to give the Area of Interest a name. This is used in the file name of the dataset that is produced.

  • AOI file location A directory prompt for the location of the Area of interest (GPKG). This can be any size but smaller areas will run significantly faster.

  • NGD Paths and Pavements file location A directory prompt for the location of the Select+Build NGD pavement and path data downloaded from OS datahub. This needs to cover the whole of the area you are looking to analyse.

  • Transect Spacing The distance (metres) between transects along pavements and paths. By default, this is set to 1m as it provides a good level of granularity but can be changed if required. A lower number will result in more transects.

  • Line Extension in metres This is how long the transect lines are extended across pavements and paths before they are clipped to the underlying polygon dataset. The default has been set as 10m because it provides coverage in most situations, whilst keeping the process fast. It can be set between 5m and 30m if required which is useful when dealing with particularly wide and large pedestrian areas.

  • Allowable Overlapping Lines Due to complex geometries and how the underlying data is collected there are instances where transects pass over others, such as tight corners, dead end streets and cul-de-sacs. The analysis output can look complicated and cluttered, but by setting the maximum allowable overlaps to a low number, transects across features such as road bends can be retained whilst transects that are the result of odd shapes are removed. By default, this is set to 4 as it provides a good compromise, but this can be changed in this parameter if required.

  • Output Centre Lines This is a prompt which allows you to choose whether to extract the centre line as a line geometry.

  • Save Location A directory prompt for file save location. The file will be saved here named 'AOI Name'Pavements'todays date' as a GPKG. The format can be changed in the feature writer.

  • Advanced Analysis (optional) An optional addition to the workbench that allows you to remove any transects that do not intersect either edge of the path/pavement. Select Yes if you would like this.

This next section provides a brief overview of the methodology within the workbench.


The pavement and path GPKG from OS Select+Build and the AOI are read into the workbench.

Generating the centreline & transects

  1. A centreline is generated from the Path and Pavement polygon from OS Select+Build in order to create the transects.

  2. Transects are created at a user specified distance (see transect spacing parameter) along the centreline and rotated 90 degrees across the Path and Pavement features.

  3. Transects are extended to a user specified distance (see line extension in metres parameter) either side of the centreline so the full cross-section of the polygons are captured.

  4. Transects are then clipped to the pavement/path data and any remnants are removed.

Transect Testing

  1. Transects are tested by checking to see if a transect intersects its own centreline. If it does, then it passes.

  2. If a transect crosses too many other transects, it is removed (as set in the allowable overlapping lines parameter).

Optional Testing: Advanced Analysis

To improve the output result, you can use the Advanced Analysis tester. This allows you to refine the results by removing all transects that do not intersect a pavement or path edge with its first and last vertex. This does not slow down the workbench.

Data Output

  1. The data is appended with the transect width figure in metres based on the Transect ID.

  2. A single GeoPackage is created with a name based on the AOI Name parameter and date.

Two workbenches have been created. The first uses the FME 2020 release, and the second using FME 2022. This is due to a slight change in the transformers process between the versions.

Please note: This is a methodology and not an OS product. The methodology can be taken and adapted, but OS will not be maintaining this methodology.

If you’d like to access the detailed methodology and the FME workbench used for this project then please go to the OS page.

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

GitHub
OS Data Hub
TfWM project
OS Select+Build tool
most pavements in Great Britain were less than three metres wide
Create your recipe
The extended transects crossing their centreline.
The transects that have been clipped to the Path and Pavement polygons.
The final output, styled to show widths. Overlapping transects have been removed.
Page cover image