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
  • Overview
  • Introduction
  • Two Types of Address
  • Delivery Point Address
  • Geographic Address
  • Street Record Types
  • Constructing a single line address
  • What if the constructed single line address does not look right?
  • Type 2 Street descriptors
  • Possible solutions

Was this helpful?

  1. Tutorials
  2. GIS

Constructing a Single Line Address using a Geographic Address

PreviousCreating 3D Symbols for GIS ApplicationsNextCreating a Digital Terrain Model (DTM)

Last updated 10 months ago

Was this helpful?

Overview

This article is meant to provide users of AddressBase Plus and Premium with instruction concerning appropriate and suitable inclusion or suppression of the four StreetRecordTypeCode’s at the end-user point for mailing purposes and creation of postally addressable single line addresses. Code has already been relating to creating a single line address, this article is looking at how to handle the Street Record Types in that process.

Please note that the instructions given for AddressBase Premium are also applicable for AddressBase Premium Islands unless otherwise mentioned.

Introduction

Sometimes it is necessary to construct alternate versions of an address, therefore it is essential to distinguish between the types of addresses and how this may impact the function and applicability of the address string output.

First there is the distinction that should be made a between Postal Address or Delivery Point Address, Geographic Addresses and Addresses that lie somewhere between the two to fit particular use cases.

Two Types of Address

The AddressBase Premium products contain a variety of data fields which allow a user to construct, for a given addressable object, different forms of an address dependent on how the address is to be used.

There are two types of address contained in the AddressBase products:

Delivery Point Address

A Delivery Point Address contains information sourced from Royal Mail (PAF), a non-geocoded list of addresses . These addresses are defined as a property that receives deliveries and is used primarily for postal purposes.

Stringent rules are used to match the PAF address to the Geographic Address and assign a common UPRN to link addresses from the two addressing sources together in the data model. Not every BLPU will have a Delivery Point (postal) Address, only those that have been matched to the Royal Mail PAF database (Multiplicity [0..1]).

Geographic Address

Geographic Addresses are maintained by contributing Local Authorities. The structure of a Geographic Address is based on the British Standard BS7666. These addresses are used to provide an accurate geographic locator for an object to aid, for example, service delivery, asset management, or command and control operations. They also represent the legal form of addresses as created under street naming and numbering legislation.

Street Record Types

Value
Description

1

Official designated Street Name

allocated by a Street Naming and Numbering (SNN) Authority

2

Street Description

not allocated an official Street Name by the SNN Authority, therefore the Street may not have a Street nameplate

3

Numbered Street

4

Unofficial Street Description

9

Description 9 used for LLPG Access

When a new BLPU Record is created for an Addressable Object that is a Postal Address which has been through the SNN process, this BLPU can only be associated with a Street Name (type 1 Street).

BLPUs requiring a Postal Address must not be associated with a new Street Description (type 2 Street), the exception to this rule is applied when all of the following conditions are met:

  • A new BLPU is created on an existing Street Description (type 2 Street)

  • The Street Description is associated with existing Postal Addresses

  • The Addressable Object forms part of a Postal Address

  • The Addressable Object is approved by the SNN Authority

Constructing a single line address

Given that the AddressBase Premium products contain two different types of address, a decision needs to be made on whether to use the Geographic or Delivery Point Addresses, or a mixture. The following two options should be considered:

  • Use Delivery Point Addresses whenever they are available, and when they are not, use a Geographic Address.

  • Use Geographic Addresses in all cases.

Depending on user requirements, it may be worth considering displaying both forms of an address, since this will provide the maximum information available about a given UPRN.

‘Mixing and matching’ components from the two different forms of address into a single address label is not recommended as this is likely to cause confusion in some instances.

What if the constructed single line address does not look right?

If you opt to use geographic addresses when consolidating a mailing list then the following considerations may be applicable depending on the intended purpose and use case.

When using the Geographic address to construct a single line address, users may require for some attribution to be suppressed to meet their use case. Street records will impact the presentation of the address when concatenated along with other address string attributes.

Type 2 Street descriptors

Type 2 Street descriptors permit the use of generalised and descriptive language which may impact the deliverability or perceived validity of the mailing address created by the user.

For example, the identifier will either describe the end points or the general location and may include key words such as: from, to, adjacent to, next to, between, rear, alongside, passing across, joining, via, with branch to:

  • SIDE OF NOS WEST AVENUE

  • REAR 2 TO 12 NEWTON STREET

If properties are associated with a type 2 Street, you should consider excluding the STREET_DESCRIPTOR from any Address that is intended for mailing purposes for streets assigned a Type 2. However, if an address is generated for another reason, for example for a site visit, this information could be included to help locate the Addressable Object.

Possible solutions

Consider implementing one of the following interventions before constructing a single line address:

  • Exclude STREET_DESCRIPTOR where Type == 2

  • Exclude Type 2 Streets from inclusion

  • Only use DPA Addresses

  • Extract 'Postally Addressable' addresses using the 'Postal Flag'

  • Review the records subsequent to construction of the single line address and omit those that provide descriptive street information

published on GitHub