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
  • Two boundary data sets?
  • Who is responsible for the boundaries?
  • Data Comparison
  • Why are the 2 products different sometimes?
  • Which boundary data should I use?

Was this helpful?

  1. Demonstrators
  2. Addressing & location demonstrators

Why are there differences in boundaries?

PreviousWhat are Vertical Streets?NextContextual demonstrators

Last updated 1 year ago

Was this helpful?

Two boundary data sets?

Boundaries are shown in two OS products:

  • Boundary-Line​

  • OS MasterMap Topography Layer

Boundaries have been shown on Ordnance Survey Mapping for over 100 years. These were then digitised as lines into Land-Line from the 1970s and subsequently into OS MasterMap Topography Layer since 2001. They were captured and maintained at large-scale (1:1250/1:2500 scale).

Since the mid 1990s Boundary-Line has existed as an authoritative polygonised dataset of political and administrative boundaries initially captured and maintained at 1:10000 scale although more recently being maintained to large-scale data.

Boundary-Line shows only boundaries that are Operative and is the authoritative dataset for boundaries in Great Britain. OS MasterMap Topography Layer may show boundaries before they are Operative, or there may be a slight delay before being updated after they are Operative.

Who is responsible for the boundaries?

In Great Britain there are three national Boundary Commissions, one each with responsibility for England (BCE), Wales (BCW) & Scotland (BCS). These are responsible for UK Parliamentary constituency boundaries.

Local government electoral arrangements are reviewed by the Local Government Boundary Commission for England, the Local Democracy and Boundary Commission for Wales and Boundaries Scotland. These include making changes to wards and electoral districts. LDBCW and Boundaries Scotland also look after the Scottish and Welsh devolved parliaments. Local Authorities are responsible for Parish and Community boundaries.

The outputs of these organisations (changes to boundaries published in Statutory Instruments, Boundary Orders and maps) all then come to Ordnance Survey to be included into Boundary-Line and OSMasterMap Topography Layer

Data Comparison

  • The authoritative boundaries dataset for Great Britain

  • Initially captured at 10:000 scale, currently maintained against larger-scale OS MasterMap data

  • Contains Administrative and Political Boundaries

  • All data is polygonised and themed by boundary type (County, Districts, Unitary Authorities, Parishes, Westminster Constituencies, and so on.)

  • All polygons include attribution such as name, type and links to ONS codes for the different boundaries

  • Published twice a year in May and October

  • Available as Open Data for anyone to use

  • Captured at large scale (1:1250 - urban, 1:2500 - rural or 1:10,000 – mountain and moorland)

  • Contains administrative and political boundaries

  • Five different themed/coloured lines are used. There is a hierarchy so that the most important boundary is shown by its symbol and all other coincident boundaries are described by text descriptions. The hierarchy and five lines used are County, District/Unitary Authority, Parish, Parliamentary and Electoral District/Ward.

  • Lines contain limited attribution, and nothing about the boundary feature they define, such as name, ONS codes, and so on

  • Polygons can be created from these lines by a user, however Mean Low Water would also be required to complete polygons that have a coastal boundary

  • Contains historic details of what the boundaries are mered to (1.2m Root of Hedge (RH), Face of Wall (FW), Centre of Road (CR), and so on) and where that mereing changes. Since 2002 any new or amended boundaries are not mered and it's assumed that their alignment is the centre of the underlying topography detail.

  • Maintained within 1 year of the Operative date of the boundary and published as part of the 6-weekly cycle of OS MasterMap Topography Layer releases

  • Available as part of OS MasterMap Topography Layer

Why are the 2 products different sometimes?

The main reason for differences between boundaries in Boundary-Line and OS MasterMap Topography Layer is to do with the scale they were captured at:

  • “Boundary-Line for England and Wales was initially digitised from Ordnance Survey’s boundary record sheets at 1:10 000 scale (or, in some cases, at 1:10 560 scale).” OS Website

  • “OS MasterMap Topography Layer provides the most detailed and accurate large-scale representation of Great Britain available from Ordnance Survey.“ – OS MasterMap Topography Layer Technical specification document

As these show, Boundary-Line was initially captured at a smaller scale than OS MasterMap Topography Layer. Boundary-Line is still the authoritative dataset and although these slight differences exist in places, they are normally no more than a few meters and addresses (and therefore citizens) should not fall inside the wrong Ward, County, Parish, etc.

Which boundary data should I use?


More detail can be found on the

More detail can be found on the

This content has been developed from what was originally a Lightning Talk PowerPoint slide set. These slides are available to PSGA members to view and download from the

Boundary-Line pages of the OS website
OS MasterMap Userguide
PSGA members area of the OS website
Page cover image
Historic Ordnance Survey map showing boundary data on the map and in the marginalia
Boundary-Line Parish dataset
OS MasterMap boundaries
Boundary-Line (in black) and OS MasterMap Topography Layer (in pink) showing a typical size of discrepancy
Cover

I want to understand the percentage of woodland by Local Authority – use Boundary-Line

Cover

I want to assess addresses per Ward – use Boundary-Line

Cover

I want to match statistics to boundaries for a choropleth map – use Boundary-Line

Cover

I want to report incidents (pot-holes, fly-tipping, etc.) by Ward – use Boundary-Line

Cover

I want to understand what a boundary is linked to on the ground – use OS MasterMap Topography Layer