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
      • 🆕Comparison of Transport Network Products
        • RAMI feature types
          • Hazard
          • Highway Dedication
          • Maintenance
          • Reinstatement
          • Restrictions
          • Special Designation
          • Structure
        • Roads and Paths feature types
          • Connecting Link
          • Connecting Node
          • Ferry Link
          • Ferry Node
          • Ferry Terminal
          • Path
          • Path Link
          • Path Node
          • Road
          • Road Link
          • Road Node
          • Road Junction
          • Street
  • 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 the Emergency Services Gazetteer (OS ESG)​
  • How can you use the OS ESG​
  • What data format is the OS ESG supplied in?​
  • What is the OS ESG attribution?​
  • OS ESG Geographical Names​
  • Differences between OS ESG Geographical Names & OS NGD Named Point​
  • OS ESG Names and Numbers of Junctions​
  • OS ESG Junction compared with OS NGD Named Road Junction​
  • OS ESG Bridge Interactions​
  • OS ESG Bridge Interactions user information​
  • Parent & Child UPRN Relationship​:
  • Completeness​
  • ​OS ESG data can be used alongside OS NGD ​
  • ​Rail Station Detail​
  • LPI: Area Name and Address​
  • LPI: USRN Assigned to BLPU​
  • OS ESG Junction compared with OS NGD Named Road Junction​

Was this helpful?

  1. Demonstrators
  2. Addressing & location demonstrators

OS Emergency Services Gazetteer

A Lightning Talk

What is the Emergency Services Gazetteer (OS ESG)​

The OS Emergency Services Gazetteer product is a comprehensive and maintained gazetteer of locations including names, places, and objects.​

  • Aligned to the AddressBase Premium Format.​

  • Every feature in OS ESG will have a Unique Property Reference Number (UPRN).​

  • Coverage is England, Scotland and Wales.​

  • A set of granular classifications types. ​

  • Comprises of the Basic Land Property Unit (BLPU), Land Property Identifier (LPI) and Classification components ONLY.​

  • Published monthly in GeoPackage and CSV formats.​

How can you use the OS ESG​

The OS ESG provides a national, consistent and maintained view of the locations. Currently these are Named Junctions and Geographical Names, but with a wider range of features in future releases​

It enables quick and accurate gazetteer searches and visualisation in applications and supports incident response, planning and coordinating emergency responses, situational awareness and incident reporting.​

March 2024
Future Releases

Names and Numbers of Junctions

Bridge Interactions

Geographical Names

Tunnels

Slipways

Weirs

Motorway Marker Posts

Motorway Emergency Phones

Vernacular Names

What data format is the OS ESG supplied in?​

OS ESG will be made available via the OS Data Hub, as part of Premium Downloads.​

  • The GeoPackage format comes ready to load into the GIS package of the users choice with different gpkg files for each layer. You will need to join the data using the UPRN.

  • The CSV format is more suited for loading into a database. All of the same feature types are accessible in csv format and all the same attribution as the Geopackage, however instead of storing the geometry in a GIS ready format, ‘BLPU’ for example is stored as a POINT attribute with a co-ordinate pair for each point.​

What is the OS ESG attribution?​

​The OS ESG will align to the AddressBase Premium specification, in line with user requirements. Therefore, it will be structured as a series of relational tables:​

  • Basic Land and Property Unit (BLPU) - a real-world object that is ‘an area of land, property or structure of fixed location having uniform occupation, ownership or function’.​

  • Local Property Identifier (LPI) - a structured entry that identifies a BLPU. The AddressBase Premium data structure provides the facility to describe a BLPU by more than one LPI. In England and Scotland there will be one Approved LPI, while in Wales there will be two Approved LPIs (English and Welsh)​

  • Classification - a structured entry that provides the code for the type of feature.

OS ESG Geographical Names​

The data includes names of features and places of geographic significance, providing orientation and identity. ​

A subset of the existing OS NGD Geographical Names, such as named water and geographic features, will be provided as part of OS ESG.​

The data offers a comprehensive list of names of features such as hills, valleys, cliffs and waterfalls.​

Differences between OS ESG Geographical Names & OS NGD Named Point​

OS ESG Geographical Names is a subset of the OS NGD Named Point Feature. For example, woodlands aren’t in OS ESG as they are included within AddressBase Plus and AddressBase Premium​

OS ESG Names and Numbers of Junctions​

A named intersection between roads at a junction or roundabout. The intersection will be assigned a modelled name based on the names of the intersecting roads and may have a number or an official name. The feature will have a classification code and description also e.g. CT14MJ Numbered Motorway Junction​.

Junction features will be provided for junctions where two or more named or numbered roads intersect. The SAO Text field can include Alternate Road Names. These can be a different spelling or an alternate road name​.

OS ESG Junction compared with OS NGD Named Road Junction​

Geometry: Motorway Junctions and Roundabouts are a single point geometry in OS ESG and Multipoint geometry in OS NGD Named Junctions​

​Schema: OS ESG is in an AddressBase Premium format and OS NGD Named Junctions have an OS NGD schema​

​Attribution: OS ESG has an AREA_NAME. There is no AREA_NAME on the OS NGD Named Junction feature​

​Classification: OS ESG has a classification scheme and OS NGD Named Junction has a description​

OS ESG Bridge Interactions​

This data provides information about bridges, describing the interactions with the networks below and over the bridge using a parent and child data relationship. This is similar to the data is OS NGD structures, only more detailed.​

​The data has been modelled and automatically created by OS using Topographic, Transport Network, Water Network, and Structures data.​

​There are 54 bridge interaction classification codes to give an overview of the type of networks that cross over and under the bridge e.g. Footbridge Over Canal.​​

Attribution
Definition
Indicative Values ​

PAO text​

Primary Addressable Object (PAO) name or description. Used to record the bridge name. Where the official name has not been captured by OS, then Bridge Unknown Name will be used.​

Abbey Bridge​

Abercamddwr Bridge​

Bridge Unknown Name​

SAO text​

Secondary Addressable Object (SAO) name or description. Used to record the names and numbers of intersecting network features or the type of network where no names apply.​

Duck Mill Walk Over River Great Ouse​

A483 Over Camddwr​

Railway between Glenfinnan and Locheilside Over A830​

Broughton​

Parent UPRN​

UPRN of the parent Record, if a parent- child relationship exists. This is used to relate individual intersections to the parent bridge feature where there are multiple intersections between different networks at the same bridge. This attribute is NULL for features where either there is no parent-child relationship or the BLPU itself is a parent bridge BLPU.​

996001447292​

NULL ​

Multi Occ Count​

Count of all of the child UPRNs for this record where a parent-child relationship exists; otherwise it will be set to 0.​

3​

5​

​

OS ESG Bridge Interactions user information​

Parent & Child UPRN Relationship​:

The Parent UPRN in this dataset is for the named bridge itself, in this case ‘Queen’s Bridge’ and lists all the interactions ‘Road Bridge over Multiple’. The Child UPRNs represent the individual interactions of the bridge over other networks, in this case the Norrie-Miller Riverside Walkway and the River Tay.​

Completeness​

The following bridges will be excluded:​

  • A subset of these features is already available in OS Addressing. To avoid duplicating features, these features will be excluded from the OS ESG product. ​

  • Unnamed bridges (including footbridges) with no networks crossing over them and unnamed watercourse passing beneath them​

  • Unnamed footbridges with unnamed paths crossing over them and either unnamed watercourse or no network passing beneath them.​

​OS ESG data can be used alongside OS NGD ​

Network over and under information is provided in OS ESG for bridges represented in OS NGD Compound Structure data. The main difference being that OS ESG is point data, not polygon data like OS NGD.​

​Rail Station Detail​

For a bridge that crosses a rail line the station information is provided, especially as a number of these are unnamed. With station information it is easier to pinpoint which section of track the bridge is on. ​

LPI: Area Name and Address​

In OS ESG as there is a hierarchy of assigning an LPI area name, it is derived from: ​

  1. The OS NGD Geographical Names Named Area Polygon if it is within one (this may have a different extent to the locality of the same name in Addressing data)​

  2. (NEAR) indicates either within 1 km of a settlement onshore, or within 500 m of a named island or 1 km from a Lower Tier Local Authority if the point is offshore​

  3. In non-urban areas the Lower Tier Local Authority is provided. ​

The OS ESG feature area name can include a combination of polygon descriptions based on hierarchy e.g. Suburban Area, Other Urban Area, City​

The address & street data in your 999 Control system that the OS ESG may sit alongside may have a locality field in some instances. This locality information may differ from the Area Name in OS ESG as they come from a different source

LPI: USRN Assigned to BLPU​

The USRN is supplied as part of the OS ESG is to allow compatibility with AddressBase Premium so it can be used with existing import tools​

When assigning the USRN to a junction, the USRN of the lowest classification Street within AddressBase intersecting a junction is assigned e.g. if you have a Designated Street Name and Officially Described Street then the Officially Described Street is selected, see StreetRecordTypeCode in the AddressBase Premium Technical Specification. ​

If there are multiple Streets with the same lowest classification, the USRN of the shortest Street intersecting a junction is assigned.​

Where roads intersecting a junction do not have an associated Street and hence a USRN, the USRN of the nearest non-motorway Street is assigned.​

The OS ESG will only reference USRNs that are in AddressBase Premium​.

OS ESG Junction compared with OS NGD Named Road Junction​

Geometry: Motorway Junctions and Roundabouts are a single point geometry in OS ESG and Multipoint geometry in OS NGD Named Junctions​

Schema: OS ESG is in an AddressBase Premium format and OS NGD Named Junctions have an OS NGD schema​

Attribution: OS ESG has an AREA_NAME. There is no AREA_NAME on the OS NGD Named Junction feature​

Classification: OS ESG has a classification scheme and OS NGD Named Junction has a description​

Looking at the OS NGD Geographical Names Lightning Talk may also be of benefit.


Links that may be useful:

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 PSGA members area of the OS website

PreviousAddressing LifecycleNextWhat are Vertical Streets?

Last updated 6 months ago

Was this helpful?

OS Emergency Services Gazetteer | OS Download Products' Documentation
Logo
OS Select+Build | Data Products | OSOrdnance Survey
Logo
Examples of road junctions (click to enlarge)
examples of USRNs being assigned to ESG records (click to enlarge)
Comparison of OS ESG and OS NGD data
Page cover image