LogoLogo
OS Docs HomeOS NGDOS APIsOS Download ProductsMore than MapsProduct Refresh Dates
  • OS Download Products' Documentation
  • Addressing and Location
    • Addressing and Location Portfolio Information
    • AddressBase Fundamentals
      • Release Notes
        • AddressBase Products May 2025 – Epoch 118
        • AddressBase Islands May 2025 – Epoch 118
        • AddressBase Products March 2025 – Epoch 117
        • AddressBase Islands March 2025 – Epoch 117
        • AddressBase Products February 2025 – Epoch 116
        • AddressBase Islands February 2025 – Epoch 116
        • AddressBase Products December 2024 – Epoch 115
        • AddressBase Islands December 2024 – Epoch 115
        • AddressBase Products November 2024 – Epoch 114
        • AddressBase Islands November 2024 – Epoch 114
        • AddressBase Products September 2024 – Epoch 113
        • AddressBase Islands September 2024 – Epoch 113
        • AddressBase Products August 2024 – Epoch 112
        • AddressBase Islands August 2024 – Epoch 112
        • AddressBase Products June 2024 – Epoch 111
        • AddressBase Islands June 2024 – Epoch 111
        • AddressBase Products May 2024 – Epoch 110
        • AddressBase Islands May 2024 – Epoch 110
        • AddressBase Products April 2024 – Epoch 109
        • AddressBase Islands April 2024 – Epoch 109
      • AddressBase product family
      • Future and past publication dates
      • Unique Property Reference Number (UPRN)
      • Coordinate reference systems
      • Classification scheme
      • Data sources
      • Street names and numbering
      • Currency, completeness and precision
      • Product supply
      • Code lists and enumerations
        • AddressbasePostalCode
        • BLPUStateCode
        • ChangeTypeCode
        • CountryCode
        • Date
        • FileTypeCode
        • LanguageCode
        • LogicalStatusCode
        • OfficialFlagCode
        • PostcodeTypeCode
        • RPCCode
        • StateCode
        • StreetClassificationCode
        • StreetRecordTypeCode
        • StreetStateCode
        • StreetSurfaceCode
        • Time
        • USRNMatchIndicatorCode
      • AddressBase local custodian codes
      • AddressBase Islands local custodian codes
    • AddressBase
      • Release Notes
      • AddressBase Getting Started Guide
        • Prerequisites
        • Data supply
        • Working with CSV data
        • Working with GML data
        • Working with COU data
        • Creating a single-line or multi-line address
        • Searching for addresses
      • AddressBase Technical Specification
        • Data formats
        • Supply and update
        • AddressBase structure
        • Feature types
          • Address
          • AddressBase Supply Set
        • Code list and enumerations
        • CSV to GML mapping
        • Example records
          • CSV
          • GML
      • AddressBase Downloads
      • AddressBase Known Data Issues
    • AddressBase Core
      • Release Notes
        • 20 May 2025
        • 13 May 2025
        • 07 May 2025
        • 29 April 2025
        • 23 April 2025
        • 15 April 2025
        • 08 April 2025
        • 01 April 2025
        • 25 March 2025
        • 18 March 2025
      • AddressBase Core Overview
        • Data capture and sources
        • GeoPlace
        • Unique Property Reference Number (UPRN)
        • Coordinate reference systems
        • Classification
        • Currency, completeness and precision
        • Product supply
      • AddressBase Core Getting Started Guide
        • Downloading a dataset
        • Working with CSV data
        • Working with GPKG data
        • Working with COU data
        • Working with tiled data
      • AddressBase Core Technical Specification
        • Data formats
        • Supply and update
        • Attributes
        • Enumerations
        • Example records
      • AddressBase Core Downloads
      • AddressBase Core Known Data Issues
    • AddressBase Plus
      • Release Notes
      • AddressBase Plus Getting Started Guide
      • AddressBase Plus Technical Specification
        • Data formats
        • Supply and update
        • AddressBase Plus structure
        • Feature types
          • Address
          • AddressBase Supply Set
        • Code lists and enumerations
        • CSV to GML mapping
        • Example records
          • CSV
          • GML
      • AddressBase Plus Downloads
      • AddressBase Plus Known Data Issues
    • AddressBase Plus Islands
      • Release Notes
      • AddressBase Plus Islands Getting Started Guide
      • AddressBase Plus Islands Technical Specification
        • Data formats
        • Supply and update
        • AddressBase Plus Islands structure
        • Feature types
          • Address
          • AddressBase Supply Set
        • Code lists and enumerations
        • CSV to GML mapping
        • Example records
          • CSV
          • GML
      • AddressBase Plus Islands Downloads
      • AddressBase Plus Islands Known Data Issues
    • AddressBase Premium
      • Release Notes
      • AddressBase Premium Getting Started Guide
        • Prerequisites
        • Data supply
        • Working with CSV data
        • Working with GPKG data
        • Working with GML data
        • Working with COU data
        • Creating a single-line or multi-line address
        • Searching for addresses
      • AddressBase Premium Technical Specification
        • Data formats
        • Supply and update
        • AddressBase Premium structure
        • Feature types
          • Street – (Type 11 Record)
          • BLPU – (Type 21 Record)
          • AddressBase supply set
          • Feature with lifecycle
        • Structured data types
          • Street Descriptor – (Type 15 Record)
          • Application Cross Reference – (Type 23 Record)
          • LPI – (Type 24 Record)
          • Delivery Point Address – (Type 28 Record)
          • Successor Cross Reference – (Type 30 Record)
          • Organisation – (Type 31 Record)
          • Classification – (Type 32 Record)
          • Entity with lifecycle
        • Dataset metadata
          • Metadata – (Type 29 Record)
          • Header – (Type 10 Record)
          • Trailer – (Type 99 record)
        • Code lists and enumerations
        • Attribute format comparison
        • Example records
          • CSV
          • GML
      • AddressBase Premium Downloads
      • AddressBase Premium Known Data Issues
    • AddressBase Premium Islands
      • Release Notes
      • AddressBase Premium Islands Getting Started Guide
      • AddressBase Premium Islands Technical Specification
        • Release Notes
          • June 2024
        • Data formats
        • Supply and update
        • AddressBase Premium Islands structure
        • Feature types
          • Street – (Type 11 Record)
          • BLPU – (Type 21 Record)
          • AddressBase supply set
          • Feature with lifecycle
        • Structured data types
          • Street Descriptor – (Type 15 Record)
          • Application Cross Reference – (Type 23 Record)
          • LPI – (Type 24 Record)
          • Delivery Point Address – (Type 28 Record)
          • Successor Cross Reference – (Type 30 Record)
          • Organisation – (Type 31 Record)
          • Classification – (Type 32 Record)
          • Entity with lifecycle
        • Dataset metadata
          • Header – (Type 10 Record)
          • Metadata – (Type 29 Record)
          • Trailer – (Type 99 record)
        • Code lists and enumerations
        • Attribute format comparison
        • Example records
          • CSV
          • GML
      • AddressBase Premium Islands Downloads
      • AddressBase Premium Islands Known Data Issues
    • Boundary-Line
      • Release Notes
        • May 2025
        • October 2024
        • June 2024
      • Boundary-Line Overview
        • Data overview
        • Product supply
      • Boundary-Line Product Information
        • Relationships of administrative areas
        • Structure of Boundary-Line
        • Boundary-Line principles and features
        • Case studies
        • Metadata
        • Glossary
        • Exception areas
        • The coastline and associated items
      • Boundary-Line Technical Specification
        • Shapefile, TAB and GKPG
          • Features - Shapefile, TAB and GPKG
            • Area - GB
            • Area - English region
            • Area - Wales region
            • Link feature type
            • Area - Polling districts England
            • Historical and ceremonial boundaries features
          • Layers - Shapefile, TAB and GKPG
            • Shapefile
            • TAB
            • GKPG
          • Code lists - Shapefile, TAB and GKPG
            • AreaCode
            • TypeCode
        • GML
          • Features - GML
            • AdministrativeUnit
          • Code lists - GML
            • AdministrativeHierarchyValue
            • NationalClassificationValue
          • Example record - GML
        • Vector tiles
      • Guide to Ceremonial County Boundaries
      • Additional Product Details
      • Boundary-Line Downloads
      • Boundary-Line Known Data Issues
    • Code-Point
      • Code-Point Overview
        • Product details
        • Product supply
      • Code-Point Products Comparison
      • Code-Point Getting Started Guide
        • Product supply
        • Data structure
        • CSV file processing
        • Data measures
        • Metadata
        • Glossary
      • Code-Point Technical Specification
        • Product structure
        • Supply formats
      • Code-Point Downloads
      • Code-Point Known Data Issues
    • Code-Point Open
      • Code-Point Open Overview
        • Product details
        • Product supply
      • Code-Point Open Products Comparison
      • Code-Point Open Getting Started Guide
        • Requirements for using the data
        • CSV file processing
        • Data measures
        • Loading the data into a GIS
        • Glossary
      • Code-Point Open Technical Specification
        • Product structure
        • Supply formats overview
      • Code-Point Open Downloads
      • Code-Point Open Known Data Issues
    • Code-Point with Polygons
      • Release Notes
        • January 2025
      • Code-Point with Polygons Overview
        • Product details
        • Product supply
      • Code-Point with Polygons Products Comparison
      • Code-Point with Polygons Getting Started Guide
        • Using the vertical street lookup
        • Creating single-space postcodes
        • Data measures
      • Code-Point with Polygons Technical Specification
        • Data supply
        • Specification
      • Code-Point with Polygons Downloads
      • Code-Point with Polygons Known Data Issues
    • 🆕OS Emergency Services Gazetteer
      • 🆕OS ESG Overview
        • 🆕Product supply
        • 🆕Planned enhancements
      • OS ESG Getting Started Guide
      • OS ESG Technical Specification
        • Feature type
          • BLPU (Type 21 Record)
        • Structured data types
          • LPI (Type 24 Record)
          • Classification (Type 32 Record)
        • 🆕Code lists
          • AddressbasePostalCode
          • BLPUStateCode
          • ChangeTypeCode
          • 🆕ClassificationCode
          • CountryCode
          • FileTypeCode
          • LanguageCode
          • LogicalStatusCode
          • OfficialFlagCode
          • RPCCode
          • USRNMatchIndicatorCode
        • Dataset metadata
          • Header (Type 10 Record)
          • Metadata (Type 29 Record)
          • Trailer (Type 99 Record)
      • 🆕OS ESG FAQs
      • 🆕OS ESG Downloads
      • OS ESG Known Data Issues
    • OS Open Built Up Areas
      • Release notes
        • April 2024
      • OS Open Built Up Areas Overview
        • Product details
        • Product supply
      • OS Open Built Up Areas Technical Specification
        • Feature types
          • Built Up Areas
          • Built Up Extents
          • Non Built Up Extents
        • Structured data types
          • MultiSurfaceWithAreaType
          • NameType
        • Code list
          • LanguageValue
        • Supply formats
      • OS Open Built Up Areas Known Data Issues
    • OS Open Names
      • Release Notes
        • April 2025
        • January 2025
        • October 2024
        • July 2024
      • OS Open Names Overview
        • Product applications
        • Product details
        • Product supply
      • OS Open Names Getting Started Guide
        • Obtaining OS Open Names data
        • CSV file processing
        • Loading the data in a GIS
      • OS Open Names Technical Specification
        • Source of OS Open Names
        • Viewing resolution
        • Product structure
        • Feature type
          • NamedPlace
        • Code lists
          • LanguageValue
          • NamedPlaceTypeValue
          • LocalTypeValue
        • Structured data types
          • GeographicalName
          • Identifier
        • Local Type
        • Supply formats overview
        • Attribute naming format comparison
        • LocalType code list
      • OS Open Names Downloads
      • OS Open Names Known Data Issues
    • Points of Interest
      • Release Notes
        • March 2025
        • December 2024
        • September 2024
        • June 2024
      • Points of Interest Product Information
        • Using Points of Interest
        • Data measures and data sources
        • Classification scheme
        • Points of Interest Provenance
        • Glossary
        • Points of Interest symbology
      • Points of Interest Technical Specification
        • Using Points of Interest
        • Pipe delimited text (PDT) file format
          • Record structure
        • Code lists
          • Positional Accuracy
          • Match Indicator
        • Example records
        • Glossary
      • Points of Interest Classification Scheme
        • Accommodation, eating and drinking
        • Commercial services
        • Attractions
        • Sport and entertainment
        • Education and health
        • Public infrastructure
        • Manufacturing and production
        • Retail
        • Transport
      • Points of Interest Class Count
        • Accommodation, eating and drinking
        • Commercial services
        • Attractions
        • Sport and entertainment
        • Education and health
        • Public infrastructure
        • Manufacturing and production
        • Retail
        • Transport
      • Points of Interest Downloads
      • Points of Interest Known Data Issues
  • Contextual or derived mapping
    • Contextual or Derived Mapping Portfolio Information
    • Colour Raster Map Fundamentals
      • Colour Raster Map Overview
        • Metadata
        • Data compression
        • Data measures
        • Product supply
      • Colour Raster Map Technical Specification
        • Georeferencing
        • Image file directory (TIFF)
        • Abbreviations used on OS 1:25 000 and 1:50 000 scale mapping
        • Product glossary
    • 1:25 000 Scale Colour Raster
      • 1:25 000 Scale Colour Raster Overview
        • Product details
        • Features depicted in the product
        • Georeferencing
      • 1:25 000 Scale Colour Raster Technical Specification
      • 1:25 000 Scale Colour Raster Downloads
      • 1:25 000 Scale Colour Raster Known Data Issues
    • 1:50 000 Scale Colour Raster
      • 1:50 000 Scale Colour Raster Overview
        • Product details
        • Features depicted in the product
        • Georeferencing
      • 1:50 000 Scale Colour Raster Technical Specification
      • 1:50 000 Scale Colour Raster Downloads
      • 1:50 000 Scale Colour Raster Known Data Issues
    • 1:250 000 Scale Colour Raster
      • 1:250 000 Scale Colour Raster Overview
        • Product details
        • Georeferencing
        • Gazetteer
      • 1:250 000 Scale Colour Raster Technical Specification
      • 1:250 000 Scale Colour Raster Downloads
      • 1:250 000 Scale Colour Raster Known Data Issues
    • GB Overview Maps
      • GB Overview Maps Downloads
      • GB Overview Maps Known Data Issues
    • MiniScale
      • MiniScale Product Guide
        • Supply and formats
        • Georeferencing
        • Depiction of roads and towns
        • Data compression
        • Features, layers and styles
      • MiniScale Technical Specification
        • National Grid
        • MiniScale file management
      • MiniScale Downloads
      • Miniscale Known Data Issues
    • OS Open Zoomstack
      • OS Open Zoomstack Getting Started Guide
        • Zoomstack vector tiles
        • Zoomstack GeoPackage format
      • OS Open Zoomstack Technical Specification
        • List of Layers
        • Description of the cartographic styles
        • Sea Extent and Name Languages
        • Vector Tiles Schema
        • GeoPackage Schema
      • OS Open Zoomstack Known Data Issues
    • OS OpenMap – Local
      • Release Notes
        • April 2025
      • OS OpenMap – Local Overview
        • Product applications and uses
        • Product details
        • Product supply
      • OS OpenMap – Local Getting Started Guide
        • Loading raster data
        • Loading vector data
        • Loading and displaying GML Data
        • POSTGIS
        • Loading and displaying Shapefile supply
        • Viewing the data in QGIS
        • Using shapefiles in PostGIS
        • Using MapInfo Professional
      • OS OpenMap – Local Technical Specification
        • Data structure
        • Feature types
          • Building
          • ElectricityTransmissionLine
          • Glasshouse
          • RailwayStation
          • RailwayTrack
          • RailwayTunnel
          • Road
          • RoadTunnel
          • Roundabout
          • MotorwayJunction
          • CarChargingPoint
          • Foreshore
          • SurfaceWater_Area
          • SurfaceWater_Line
          • TidalBoundary
          • TidalWater
          • Woodland
          • FunctionalSite
          • ImportantBuilding
          • NamedPlace
        • Code lists
          • RailwayStationClassification
          • RailwayTrackClassification
          • DrawLevelValue
          • OverrideValue
          • RoadClassification
          • RoundaboutClassification
          • CarChargingType
          • RatedVoltage
          • ChargeMethod
          • TidalBoundaryClassification
          • BuildingTheme
          • BuildingClassification
          • SiteClassification
          • FontHeightClassification
          • NamedPlaceClassification
      • OS OpenMap – Local Downloads
      • OS OpenMap – Local Known Data Issues
    • OS VectorMap District
      • OS VectorMap District Overview
        • Generalisation
        • Feature types
        • Style definition
        • Product supply
      • OS VectorMap District Technical Specification
        • GML Overview
        • Raster Specification
        • Georeferencing
        • Feature types
          • Building
          • ElectricityTransmissionLine
          • Glasshouse
          • RailwayStation
          • RailwayTrack
          • RailwayTunnel
          • MotorwayJunction
          • Road
          • RoadTunnel
          • Roundabout
          • Foreshore
          • SurfaceWater_Area
          • SurfaceWater_Line
          • TidalBoundary
          • TidalWater
          • Ornament
          • Woodland
          • FunctionalSite
          • NamedPlace
          • SpotHeight
          • AdministrativeBoundary
        • Code lists
          • RailwayStationClassification
          • RailwayTrackClassification
          • RoadClassification
          • RoundaboutClassification
          • DrawLevelValue
          • OverrideValue
          • TidalBoundaryClassification
          • FunctionalSiteClassification
          • NamedPlaceClassification
          • FontHeightClassification
          • AdministrativeBoundaryClassification
        • Attributes
        • Feature Codes
        • Styling of Land and Sea
      • Vector Simple Guide
        • Downloading OS OpenData
        • Opening OS OpenData in QGIS
        • Styling vector data
        • Opening and saving maps in Composer
      • Raster Simple Guide
        • Downloading OS OpenData
        • Opening OS OpenData in QGIS
        • Opening and saving a map in composer
      • OS VectorMap District Downloads
      • OS VectorMap District Known Data Issues
    • OS VectorMap Local
      • Release Notes
        • January 2025
      • OS VectorMap Local Overview
        • Product details
        • Features represented in the product
        • Product style definition
        • Product supply
        • National Grid coverage for OS VectorMap Local
      • OS VectorMap Local Technical Specification
        • GeoPackage overview
        • GML overview
        • Raster data
        • Feature types
          • Area
          • Line
          • VectorMapPoint
          • RoadCLine
          • RailCLine
          • Text
        • Code lists
          • DrawLevelValue
          • AnchorPositionValue
          • TextFontValue
        • Structured data types
          • textRenderingType
        • Feature codes and descriptions
        • Vector tiles overview
        • Important Buildings classification
      • OS VectorMap Local Downloads
      • Supporting documents
        • OS VectorMap Local Cartographic Style Definitions
      • OS VectorMap Local Known Data Issues
  • Networks
    • Networks Portfolio Information
    • OS Detailed Path Network
      • OS Detailed Path Network Overview
        • Product details
        • Attribution
        • Product supply
        • Coordinate reference system
      • OS Detailed Path Network Getting Started Guide
        • Downloading the data
        • Loading GML data
      • OS Detailed Path Network Technical Specification
        • OS Detailed Path Network structure
        • Feature types
          • Route
          • RouteLink
          • RouteNode
        • Structured data types
          • VerticalGainType
        • Code lists
          • LevelCodeValue
          • PotentialHazardValue
          • RightOfWayValue
          • RouteDescriptiveGroupValue
          • RouteDescriptiveTermValue
          • RouteLinkDescriptiveTermValue
          • RouteNodeDescriptiveTermValue
          • SurfaceTypeValue
        • Data quality
        • GML overview
        • GeoPackage overview
          • Route
          • RouteLink
          • RouteNode
        • Vector Tiles overview
          • Route
          • RouteLink
        • GML examples
      • OS Detailed Path Network Downloads
      • OS Detailed Path Network Known Data Issues
    • OS MasterMap Highways Network Fundamentals
      • Release Notes
        • May 2025
        • April 2025
        • March 2025
        • February 2025
        • January 2025
        • December 2024
        • November 2024
        • October 2024
        • September 2024
        • August 2024
        • July 2024
        • June 2024
      • OS MasterMap Highways Network Product Family
      • OS MasterMap Highways Network Overview
        • Standards
        • Coordinate reference system
        • Feature types
          • Road Link (present in Roads & RAMI products)
          • Road Node (present in Roads & RAMI products)
          • Path Link (present in Paths product)
          • Path Node (present in Paths product)
          • Connecting Link (present in Paths product)
          • Connecting Node (Present in Paths product)
          • Road (present in Roads & RAMI products)
          • Path (present in Paths product)
          • Street (present in all OS MasterMap Highways Network products)
          • Road Junction (present in Roads & RAMI products)
          • Ferry Link (present in all OS MasterMap Highways Network products)
          • Ferry Node (present in all OS MasterMap Highways Network products)
          • Ferry Terminal (present in all OS MasterMap Highways Network products)
          • Access Restrictions (present in RAMI product)
          • Turn Restrictions (present in RAMI product)
          • Restrictions For Vehicles (present in RAMI product)
          • Hazards (present in RAMI product)
          • Structures (present in RAMI product)
          • Maintenance (present in RAMI & Paths products)
          • Reinstatement (present in RAMI & Paths products)
          • Highways Dedication (present in RAMI & Paths products)
          • Special Designations (present in RAMI & Paths products)
        • Product supply
        • Product packaging
        • File naming
        • Feature validation data set
        • Volume feature count
        • OS Open Roads Lookup Table
      • OS MasterMap Highways Network Getting Started Guide
        • What do I need to use this data?
        • Product supply
        • Coverage
        • Product packaging
        • File naming
        • Unzipping GML, GeoPackage, and vector tiles files
        • Loading OS MasterMap Highways Network products into a GIS
        • Relationships between Highways tables
      • OS MasterMap Highways Network Playbook
        • Connecting to Address Data
        • Identifying Change in the Network
        • Highlighting Roads Under Construction
        • Creating a Map of Winter Gritting Routes
        • Adding Road Names and Numbers to a Map
        • Merging Tables and Dropping Geometry
        • Creating a Routable Network
      • OS MasterMap Highways Network Downloads
      • OS MasterMap Highways Network Known Data Issues
    • OS MasterMap Highways Network – Roads
      • OS MasterMap Highways Network Overview
      • OS MasterMap Highways Network – Roads Technical Specification
        • Specification changes
        • Structure
        • How the product fits together
        • Change-Only Update (COU) supply
        • Feature types
          • RoadLink
          • RoadNode
          • Road
          • Street
          • RoadJunction
          • FerryLink
          • FerryNode
          • FerryTerminal
        • Structured data types
          • identifier
          • OperationalStateType
          • DesignatedNameType
          • ResponsibleAuthority
          • CycleFacilityType
          • ElevationGainType
          • RoadWidthType
        • Code lists and Enumerations
          • ChangeValue
          • RoadClassificationValue
          • RoadFunctionValue
          • MatchStatusValue
          • OperationalStateValue
          • ProvenanceSourceValue
          • RoadStructureValue
          • LinkDirectionValue
          • FormOfWayValue
          • CycleFacilityValue
          • RoadWidthConfidenceLevelValue
          • FormOfRoadNodeValue
          • RoadNodeClassificationValue
          • AccessPointValue
          • StreetTypeValue
          • JunctionTypeValue
          • ConnectionTypeValue
          • FormOfWaterwayNodeValue
        • GML overview
        • GeoPackage overview
          • ferry_link
          • ferry_node
          • ferry_terminal
          • road
          • road_junction
          • road_link
          • road_node
          • street
        • Vector tiles overview
          • ferry_link
          • ferry_node
          • ferry_node
          • road_link
          • road_node
          • street
        • GML examples
      • OS MasterMap Highways Network Getting Started Guide
      • OS MasterMap Highways Network Known Data Issues
    • OS MasterMap Highways Network – Routing and Asset Management Information
      • OS MasterMap Highways Network Overview
      • OS MasterMap Highways Network – Routing and Asset Management Information Technical Specification
        • Specification changes
        • How the product fits together
        • Routing and Asset Management feature information
          • Data types
            • NetworkReference
            • NodeReference
            • LinkReference
            • PointReference
            • Multiple Link Reference
            • Point Reference
        • Common attribution
        • Rights and Restrictions
          • Feature types
            • AccessRestriction
            • HighwayDedication
            • TurnRestriction
            • RestrictionForVehicles
        • Advisory information
          • Feature types
            • Hazard
            • Structure
        • Asset management
          • Feature types
            • Maintenance
            • Reinstatement
            • Special Designation
        • Change-Only Update (COU) supply
        • Code lists and enumerations
          • ChangeValue
          • UseTypeValue
          • VehicleTypeValue
          • LoadTypeValue
          • NamedDateValue
          • NamedDayValue
          • NamedPeriodValue
          • NamedTimeValue
          • AccessRestrictionValue
          • DedicationValue
          • TurnRestrictionValue
          • RestrictionTypeValue
          • HazardTypeValue
          • StructureTypeValue
          • ReinstatementTypeValue
          • SpecialDesignationTypeValue
          • LinkDirectionValue
          • MaintenanceValue
        • Data types
          • TemporalPropertyType
          • DateRangeType
          • DayPropertyType
          • TimePropertyType
          • TimeRangeType
          • TrafficRegulationOrderType
          • VehicleQualifier
          • ResponsibleAuthority
          • Identifier
        • GML overview
        • GeoPackage overview
          • Access Restriction
          • Highway Dedication
          • Turn Restriction
          • Restriction for Vehicles
          • Hazard Point
          • Hazard
          • Structure Point
          • Structure
          • Maintenance
          • Maintenance Point
          • Maintenance Line
          • Maintenance Area
          • Reinstatement
        • GML examples
      • OS MasterMap Highways Network Getting Started Guide
      • OS MasterMap Highways Network Known Data Issues
    • OS MasterMap Highways Network – Paths
      • OS MasterMap Highways Network Overview
      • OS MasterMap Highways Network – Paths Technical Specification
        • Specification changes
        • Structure
        • How does the product fit together?
        • Change-Only Update (COU) Supply
        • Feature types
          • PathLink
          • PathNode
          • ConnectingLink
          • ConnectingNode
          • Path
          • Street
          • FerryLink
          • FerryNode
          • FerryTerminal
          • Maintenance
          • Reinstatement
          • SpecialDesignation
          • HighwayDedication
        • Structured data types
          • Identifier
          • CycleFacilityType
          • ElevationGainType
          • OperationalStateType
          • DesignatedNameType
          • ResponsibleAuthority
          • TemporalPropertyType
          • DateRangeType
          • DayPropertyType
          • TimePropertyType
          • TimeRangeType
        • Data types
          • NetworkReferenceLocation
          • Temporal Properties
        • Code lists and Enumerations
          • ChangeValue
          • FormOfWayValue
          • SurfaceTypeValue
          • MatchStatusValue
          • ProvenanceSourceValue
          • CycleFacilityValue
          • FormOfRoadNodeValue
          • RoadNodeClassificationValue
          • OperationalStateValue
          • StreetTypeValue
          • ConnectionTypeValue
          • FormOfWaterwayNodeValue
          • DedicationValue
          • ReinstatementTypeValue
          • SpecialDesignationTypeValue
          • MaintenanceValue
        • GML Overview
        • GeoPackage overview
          • connecting_link
          • connecting_node
          • ferry_link
          • ferry_node
          • ferry_terminal
          • highway_dedication
          • maintenance
          • path
          • path_link
          • path_node
          • reinstatement
          • special_designation
          • street
        • Vector tiles overview
          • connecting_node
          • ferry_link
          • ferry_node
          • highway_dedication
          • path_link
          • path_node
          • street
        • GML examples
      • OS MasterMap Highways Network Getting Started Guide
      • OS MasterMap Highways Network Known Data Issues
    • OS MasterMap Water Network Layer
      • Release Notes
        • April 2025
        • January 2025
        • October 2024
        • April 2024
      • OS MasterMap Water Network Layer Overview
        • Feature types in the product
        • Standards and CRS
        • Product supply
      • OS MasterMap Water Network Layer Getting Started Guide
        • Requirements for using the data
        • Structure of the supplied data
        • Loading GML data into a GIS
        • Creating a water network using ESRI software
      • OS MasterMap Water Network Layer Technical Specification
        • Product notes
          • January 2022 product notes
        • Product structure
        • Feature types
          • WatercourseLink
          • HydroNode
        • Structured data types
          • LinearReference
          • PointReference
        • Code lists and enumerations
          • LinkDirectionValue
          • WatercourseFormValue
          • WatercourseProvenanceValue
          • LevelOfDetailValue
          • ReasonForChangeValue
          • VerticalPositionValue
          • HydroNodeCategoryValue
          • WatercourseTypeValue
        • Feature types for future release
          • WatercourseSeparatedCrossing
          • WatercourseLinkSet
          • WatercourseInteraction
        • GML overview
        • GeoPackage overview
          • WatercourseLink
          • HydroNode
        • Vector tiles overview
          • Attribute naming differences
          • HydroNode
        • Data provenance
        • Additional resources
      • OS MasterMap Water Network Layer Downloads
      • OS MasterMap Water Network Layer Known Data Issues
    • 🆕OS Multi-modal Routing Network
      • OS MRN Overview
        • Product supply
        • Coordinate reference system
        • Feature types overview
          • Transport Link overview
          • Transport Node overview
          • Turn Restriction overview
        • OpenStreetMap schema
        • Modal change
        • Grade separation
      • OS MRN Getting Started Guide
        • pgRouting
        • GraphHopper
        • OpenTripPlanner
        • Working with OpenStreetMap files
      • OS MRN Technical Specification
        • Feature types
          • Transport Link
          • Transport Node
          • Turn Restriction
        • Code lists
          • AccessValue
          • BridgeValue
          • FordValue
          • HighwayValue
          • JunctionValue
          • OneWayValue
          • RailServiceValue
          • RailwayValue
          • RestrictionLabelValue
          • RouteValue
          • TunnelValue
      • OS MRN Known Data Issues
    • OS Open Rivers
      • Release notes
        • April 2025
        • October 2024
      • OS Open Rivers Overview
        • OS Open Rivers Data
        • Product supply
        • Coverage and file sizes
      • OS Open Rivers Technical Specification
        • Product structure
        • Feature types
          • WatercourseLink
          • HydroNode
        • Code lists
          • LinkDirectionValue
          • WatercourseFormValue
          • HydroNodeCategoryValue
        • GML overview
        • Esri shapefile overview
          • WatercourseLink
          • HydroNode
        • GeoPackage overview
          • GeoPackage format changes April 2023
          • WatercourseLink
          • HydroNode
        • Vector tiles overview
          • Vector tiles schema
          • WatercourseLink
          • HydroNode
      • OS Open Rivers Downloads
      • OS Open Rivers Known Data Issues
    • OS Open Roads
      • Release notes
        • April 2025
        • October 2024
        • April 2024
      • OS Open Roads Overview
        • OS Open Roads Data
        • Feature types
        • Product supply
        • Coverage and file sizes
      • OS Open Roads Technical Specification
        • Product structure
        • Feature types
          • RoadLink
          • RoadNode
          • MotorwayJunction
        • Code lists and enumerations
          • RoadClassificationValue
          • RoadFunctionValue
          • FormOfWayValue
          • RoadStructureValue
          • FormOfRoadNodeValues
        • GML overview
        • Esri shapefile overview
          • RoadLink
          • RoadNode
        • GeoPackage overview
          • RoadLink
          • RoadNode
        • Vector Tiles overview
          • RoadLink
          • RoadNode
          • MotorwayJunction
      • OS Open Roads Downloads
      • OS Open Roads Known Data Issues
  • Topography
    • Topography Portfolio Information
    • OS MasterMap Topography Layer – Building Height Attribute
      • Release Notes
        • April 2025
        • October 2024
        • April 2024
      • OS MasterMap Topography Layer – Building Height Attribute Overview
        • Product details
        • Product attributes
        • Product supply information
        • Product data
      • OS MasterMap Topography Layer – Building Height Attribute Getting Started Guide
        • What do I need to use this data?
        • Product supply information
        • Managing .csv data
        • Loading data into a GIS
        • Joining Building Height Attribute data to a OS MasterMap Topography Layer
        • Importing data into a database
      • OS MasterMap Topography Layer – Building Height Attribute Technical Specification
        • Product supply
        • Product structure
        • Feature type
          • Building Height Attribute
        • Code list
          • BHA_ConfValue
        • Example record
      • OS MasterMap Topography Layer – Building Height Attribute Downloads
      • OS MasterMap Topography Layer – Building Height Attribute Known Data Issues
    • OS MasterMap Greenspace Layer
      • Release Notes
        • April 2025
        • October 2024
      • OS MasterMap Greenspace Layer Overview
        • Product details
        • Function and form
        • Data creation
        • Product supply
      • OS MasterMap Greenspace Layer Getting Started Guide
        • Using GeoPackage and Vector Tile formats
        • QGIS
        • ArcGIS ArcMap
        • PostGIS
        • MapInfo Professional
        • CadCorp Map Modeller
        • Loading the data
      • OS MasterMap Greenspace Layer Technical Specification
        • Product classification and structure
        • Feature types
          • Greenspace Area
        • Code lists and Enumerations
          • Function
          • Form
        • Function hierarchy
        • Form hierarchy
        • OS Open Greenspace lookup table
        • GML overview
        • ESRI Shapefile overview
        • GeoPackage overview
        • Vector Tiles overview
        • Attribute mapping
        • GML example record
      • OS MasterMap Greenspace Layer Downloads
      • OS MasterMap Greenspace Layer Known Data Issues
    • OS MasterMap Sites Layer
      • Release Notes
        • April 2025
        • October 2024
        • April 2024
      • OS MasterMap Sites Layer Overview
        • Product details
        • Product supply
        • Coordinate reference systems
        • Product glossary
      • OS MasterMap Sites Layer Getting Started Guide
        • QGIS
        • Cadcorp SIS Desktop
        • FME Desktop
        • ArcGIS and ArcMap
        • MapInfo Professional
        • Astun Technology GML/KML Loader
      • OS MasterMap Sites Layer Technical Specification
        • Data specification overview
        • Theme definitions
          • Air transport
          • Education
          • Medical care
          • Rail transport
          • Road transport
          • Water transport
          • Utility or industrial
        • Functional site extent overview
        • Access point overview
        • Routing point overview
        • Feature types
          • FunctionalSite
          • AccessPoint
          • RoutingPoint
        • Enumerations
          • FunctionStatusValue
          • StakeholderRoleValue
          • ExtentDefinitionValue
          • AccessTypeValue
          • NatureOfAccessValue
          • AccessUseRestrictionValue
          • AccessMechanismValue
          • AccessDirectionValue
          • ReasonForChangeValue
        • Code lists
          • FunctionValue
          • FunctionThemeValue
        • Geometry
        • GML
        • GeoPackage
          • Functional Site attributes
          • Access Point attributes
          • Routing Point
        • Vector tiles
      • OS MasterMap Sites Layer Downloads
      • OS MasterMap Sites Layer Known Data Issues
    • OS MasterMap Topography Layer
      • Release Notes
        • April 2025
        • March 2025
        • February 2025
        • December 2024
        • November 2024
        • September 2024
        • August 2024
        • June 2024
        • May 2024
        • April 2024
      • Product Refresh Dates
      • OS MasterMap Topography Layer Overview
        • Product purpose
        • Product applications
        • Product details
        • Styling
        • Product themes
        • Coordinate reference systems
        • Product supply
          • Product supply mechanism and options
          • GML supply options
          • Updating data holdings
        • Change management and data association
      • OS MasterMap Topography Layer Getting Started Guide
        • QGIS
        • ArcGIS Pro
        • ArcMap
        • Cadcorp SIS Desktop Express
        • MapInfo Professional
        • FME Desktop
        • Astun Technology GML/KML Loader
      • OS MasterMap Topography Layer Getting Started with Styling Guide
        • Styling method overview
        • How to use the SQL scripts
        • How to use the stylesheets
        • Attribute tables
      • OS MasterMap Topography Layer Standard Styling Specification
        • Cartographic styling
        • Cartographic style definitions
        • Cartographic styling for new descriptive terms
          • TopographicArea
          • TopographicLine
          • TopographicPoint
        • Shared symbol geometry
        • Point symbols
        • Fill symbols
        • Compound symbols
        • Pattern definitions
        • Line styles
        • Cartographic descriptive term style definitions
      • OS MasterMap Topography Layer Technical Specification
        • File naming
        • Supply mechanisms
        • Product themes
          • Administrative Boundaries
          • Buildings
          • Heritage and Antiquities
          • Land
          • Rail
          • Roads, Tracks, and Paths
          • Structures
          • Terrain and Height
          • Water
        • Feature types
          • TopographicPoint
          • TopographicLine
          • TopographicArea
          • BoundaryLine
          • CartographicSymbol
          • CartographicText
        • Complex attributes
          • ChangeHistoryType
          • HeightAboveDatumType
          • HeightAboveGroundLevelType
          • TextRenderingType
        • Enumerations
          • ThemeValue
          • DescriptiveGroupValue
          • AccuracyOfPositionValue
          • ReasonForChangeValue
          • PhysicalPresenceValue
          • MakeValue
          • DescriptiveTermValue
        • Geometric data types
        • Topology
        • Seamless data supply
        • Feature lifecycles and tracking change
          • Polygon feature lifecycle rules
          • Line feature lifecycle rules
          • General point feature lifecycle rules
        • GML overview
          • GML examples
        • GeoPackage overview
        • Vector tiles overview
        • Attribute mapping
        • Geometry mapping
        • COU overview
        • Feature code lookup table
        • Change value descriptions
        • Administrative boundary alignments
      • OS MasterMap Topography Layer Downloads
      • OS MasterMap Topography Layer Known Data Issues
    • OS Open Greenspace
      • Release Notes
        • April 2025
        • October 2024
      • OS Open Greenspace Overview
        • Product details
        • Data creation
        • Product supply
      • OS Open Greenspace Getting Started Guide
        • QGIS
        • ESRI ArcGIS
        • PostGIS
        • MapInfo Professional
        • Cadcorp Map Modeller
      • OS Open Greenspace Technical Specification
        • Data structure
        • Feature types
          • GreenspaceSite
          • AccessPoint
        • Code lists
          • AccessTypeValue
          • FunctionValue
        • GML overview
        • GeoPackage overview
        • Vector tiles overview
        • Attribute mapping
      • OS Open Greenspace Downloads
      • OS Open Greenspace Known Data Issues
  • Identifiers
    • Identifiers Portfolio Information
    • OS Open Identifiers Family Information
    • OS Open Linked Identifiers
      • Release Notes
        • May 2025 – Epoch 43
        • March 2025 – Epoch 42
        • February 2025 – Epoch 41
        • January 2025 – Epoch 40
        • November 2024 – Epoch 39
        • October 2024 – Epoch 38
        • August 2024 – Epoch 37
        • July 2024 – Epoch 36
      • OS Open Linked Identifiers Overview
        • Uses of OS Open Linked Identifiers
        • Product details
      • OS Open Linked Identifiers Getting Started Guide
        • Linked identifiers
        • Instructions to install/load into a database application
      • OS Open Linked Identifiers Technical Specification
        • Product structure
        • Linked Identifier data (CSV) attributes
        • Product Version Information file (JSON)
        • RoadLink_TOID_TopographicArea_TOID_2
        • Road_TOID_TopographicArea_TOID_3
        • Street_USRN_TopographicArea_TOID_4
        • BLPU_UPRN_TopographicArea_TOID_5
        • RoadLink_TOID_Road_TOID_7
        • RoadLink_TOID_Street_USRN_8
        • BLPU_UPRN_RoadLink_TOID_9
        • Road_TOID_Street_USRN_10
        • BLPU_UPRN_Street_USRN_11
        • ORRoadLink_GUID_RoadLink_TOID_12
        • ORRoadNode_GUID_RoadLink_TOID_13
      • OS Open Linked Identifiers Known Data Issues
    • OS Open TOID
      • Release Notes
        • May 2025 – Epoch 43
        • March 2025 – Epoch 42
        • February 2025 – Epoch 41
        • January 2025 – Epoch 40
        • November 2024 – Epoch 39
        • September 2024 – Epoch 38
        • August 2024 – Epoch 37
        • July 2024 – Epoch 36
      • OS Open TOID Overview
        • Product supply
        • Coordinate reference system
      • OS Open TOID Technical Specification
        • Product Details
        • Data structure
        • Product Supply
      • OS Open TOID Known Data Issues
    • OS Open UPRN
      • Release Notes
        • May 2025
        • March 2025
        • February 2025
        • December 2024
        • November 2024
        • September 2024
      • OS Open UPRN Overview
        • Product supply
        • Coordinate reference systems
      • OS Open UPRN Technical Specification
        • Feature type
          • OS Open UPRN
      • OS Open UPRN Known Data Issues
    • OS Open USRN
      • Release Notes
        • May 2025
        • April 2025
        • March 2025
        • February 2025
        • January 2025
        • December 2024
        • November 2024
        • October 2024
        • September 2024
        • August 2024
        • July 2024
      • OS Open USRN Overview
        • Product supply
        • Coordinate reference system
      • OS Open USRN Technical Specification
        • Street Type
        • Feature type
          • OS Open USRN
        • Geometry
        • Metadata
      • OS Open USRN Known Data Issues
  • Height and imagery
    • Height and Imagery Portfolio Information
    • 🆕OS 3D Mesh (Beta Product)
      • 🆕OS 3D Mesh Overview
        • 🆕Product data
        • 🆕Feature modelling
      • 🆕OS 3D Mesh Getting Started Guide
        • 🆕Importing an OS integrated mesh model into ArcGIS Pro
          • 🆕Navigation
          • 🆕Scene lighting
          • 🆕Adding additional vector data
          • 🆕Adding 2D polygon layers
          • 🆕Adding 3D line feature layers
          • 🆕Adding point datasets
          • 🆕Adding miscellaneous 3D models
          • 🆕'Line of sight' analysis
          • 🆕Animation
        • 🆕Importing an OS integrated mesh model into ArcGIS Online
          • 🆕Adding data to AGOL
          • 🆕Creating a 3D scene
          • 🆕Adding an OS mesh
          • 🆕Spatial reference systems
          • 🆕Defining 'Layer Style' options
          • 🆕Polygon layers
          • 🆕Line layers
          • 🆕Point layers
          • 🆕Text labels
          • 🆕Custom 3D models
          • 🆕Spatial analysis and reporting
    • OS Terrain 5
      • OS Terrain 5 Overview
        • Product supply
        • Pre-requisites
        • Data structure
        • Source data
        • The National Grid
      • OS Terrain 5 Technical Specification
        • Grid data
        • Contour data
        • GML Feature types
        • Esri shapefile
        • Metadata
        • Product glossary
      • OS Terrain 5 Downloads
      • OS Terrain 5 Known Data Issues
    • OS Terrain 50
      • OS Terrain 50 Overview
        • Product supply
        • Pre-requisites
        • Data structure
        • Source data
      • OS Terrain 50 Technical Specification
        • Grid data
        • Contour data
        • GML Feature Types
        • Esri Shapefile
        • GeoPackage
        • Vector tiles
        • Metadata
        • Product glossary
      • OS Terrain 50 Downloads
      • OS Terrain 50 Known Data Issues
    • OS MasterMap Imagery Layer
      • OS MasterMap Imagery Layer Technical Specification
        • Image appearance
        • Ancillary files
      • OS MasterMap Imagery Layer Downloads
      • OS MasterMap Imagery Layer Known Data Issues
  • Getting Started
    • Getting Started with GeoPackage
      • Accessing GeoPackage data via GIS software
      • Loading GeoPackage into a database
      • Reading GeoPackage data via FME
    • Getting Started with Vector Tiles
      • Installing vector tiles in GIS software
      • Using OS styles to get started in Mapbox Studio
      • Hosting and serving your own vector tiles
      • Using OS styles on vector tiles you have created
      • Product downloads
  • Resources
    • 📅Product Refresh Dates
    • 📣Product Announcements
    • 🗺️PSGA Product Summary
    • 🔍OS MasterMap Product Viewer Tool
    • OS Product Roadmap
    • End of Life Product Notices
      • End of Life Notice – OS MasterMap Water Network Layer
    • Accessibility
    • Contact Us
    • 📃Terms and Conditions
    • 📔Open Identifiers Policy
    • Use of NSG and OS Data
Powered by GitBook
On this page
  • Delivery Point Address vs Geographic Address
  • High-level data model
  • Background to single-line and multi-line address labels
  • Delivery Point Address
  • Building a single-line Delivery Point Address
  • Building a multi-line Delivery Point Address
  • Geographic Address (Local Authority Address)
  • Constructing a single address label from the Geographic Address fields
  • Linking address components
  • Rendering SAOs and PAOs
  • Street description, town, locality and administrative area names
  • Building a single-line Geographic Address
  • Building a multi-line Geographic Address
  • Advice on creating mailing lists using AddressBase Premium products
  • Address status
  • Other filters available in AddressBase Premium products for use in addressing labels

Was this helpful?

Export as PDF
  1. Addressing and Location
  2. AddressBase Premium
  3. AddressBase Premium Getting Started Guide

Creating a single-line or multi-line address

PreviousWorking with COU dataNextSearching for addresses

Last updated 8 months ago

Was this helpful?

Delivery Point Address vs Geographic 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

  • Geographic Address

These two address types come from different sources and are matched together by GeoPlace.

The Delivery Point Address is sourced from Royal Mail’s Postcode Address File (PAF), which is a non- geocoded list of addresses. These addresses are used primarily as a ‘mailing list’ for postal purposes.

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.

High-level data model

The AddressBase Premium data model accommodates both the Delivery Point Address and the Geographic Address by linking them using the unique property reference number (UPRN) as the key.

It is important to note the cardinality differences that the Geographic and Delivery Point Address components have with the Basic Land and Property Unit (BLPU):

  • The relationship between the Delivery Point Address and the BLPU is 0..1 – 1.

  • This means that the Delivery Point Address is an optional component, so a Delivery Point Address will only be created when it has been matched to the Geographic Address. Moreover, only one Delivery Point Address can be matched to a BLPU.

  • The relationship between the Land and Property Identifier (LPI) and the BLPU is 1..* – 1.

  • This means that the LPI component is mandatory; therefore, at least one LPI must exist for each BLPU. Moreover, there can be more than one LPI linked to a single BLPU.

Together, these differences mean that there are more Geographic Addresses in the product than there are Delivery Point Addresses, because:

  • Not every BLPU has a Delivery Point (postal) Address, only those that have been matched to the Royal Mail PAF database.

  • A single BLPU can have only one Delivery Point Address.

  • A single BLPU can have more than one Geographic Address (because alternative and historical addresses are available in AddressBase Premium).

Background to single-line and multi-line address labels

A common requirement for customers using the AddressBase products is to build a single address label from core address elements.

There are two types of address label: single line and multi-line. The simplest label is a full address on a single line, with different elements separated by commas and spaces. This type of label is suited for displaying a full address within a tabular display, such as within an on-screen data grid or spreadsheet, or where a single-line printed address is most appropriate (such as within the text, header or footer of a letter), for example:

ROSE COTTAGE, 5 MAIN STREET, ADDRESSVILLE, LONDON, SE99 9EX

The second type of formatted address is a multi-line address label. These labels are most often used on envelopes or at the tops of letters, where different parts of an address are separated onto different lines, for example:

ROSE COTTAGE 5 MAIN STREET ADDRESSVILLE LONDON SE99 9EX

The following sections outline a methodology for structuring and layering a single address label using AddressBase Premium. The rules outlined are suggestions only and can be used for visual display of full addresses. It is strongly recommended that address components are stored in the format in which they are provided in order to allow maximum flexibility of use and derived value.

Delivery Point Address

A Delivery Point Address contains information sourced from Royal Mail (PAF). Stringent rules are used to match these addresses to the Geographic Address and assign a common UPRN to link addresses from the two addressing sources together in the data model.

To construct a single address label based purely on the Royal Mail PAF address fields, the following attributes listed in Table 7 can be used to build a Delivery Point Address label.

The following table details the Delivery Point Address components.

Delivery Point Address component
Type

DEPARTMENT_NAME

Character

ORGANISATION_NAME

Character

SUB_BUILDING_NAME

Character

BUILDING_NAME

Character

BUILDING_NUMBER

Integer

PO_BOX_NUMBER

Integer

DEPENDENT_THOROUGHFARE (or WELSH_DEPENDENT_THOROUGHFARE)

Character

THOROUGHFARE (or WELSH_THOROUGHFARE)

Character

DOUBLE_DEPENDENT_LOCALITY (or WELSH_DOUBLE_DEPENDENT_LOCALITY)

Character

DEPENDENT_LOCALITY (or WELSH_DEPENDENT_LOCALITY)

Character

POST_TOWN (or WELSH_POST_TOWN)

Character

POSTCODE

Character

These address components are listed in the correct order in which they should appear on an address label. There may be a business need to replace the thoroughfare, locality and post_town attributes with the Welsh equivalent (listed in Table 7). The following examples will use the English version of these attributes.

It should be noted that most of the PAF fields are optional and may contain null values (or zero, in the cases of BUILDING NUMBER and PO BOX NUMBER). In these cases, those fields should be omitted.

The following (entirely fictional) example shows all of the PAF fields filled in (apart from the PO BOX NUMBER) and illustrates how these fields should be ordered in a single address label:

Delivery Point Address component
Example

DEPARTMENT_NAME

CUSTOMER SERVICE DEPARTMENT

ORGANISATION_NAME

JW SIMPSON LTD.

SUB_BUILDING_NAME

UNIT 3

BUILDING_NAME

THE OLD FORGE

BUILDING_NUMBER

7

PO_BOX_NUMBER

DEPENDENT_THOROUGHFARE

RICHMOND TERRACE

THOROUGHFARE

MAIN STREET

DOUBLE_DEPENDENT_LOCALITY

HOOK

DEPENDENT_LOCALITY

WARSASH

POST_TOWN

SOUTHAMPTON

POSTCODE

SO99 9ZZ

In cases where a PO BOX NUMBER is present, it will only be described in the data as an integer. In order to properly format these addresses when generating an address label, these integers should be prefixed with the text ‘PO BOX’, as shown in the following example:

Delivery Point Address component

Data content

Formatted output

ORGANISATION_NAME

‘JWS CONSULTING’

JWS CONSULTING

PO_BOX_NUMBER

5422

PO BOX 5422

THOROUGHFARE

‘HIGH STREET’

HIGH STREET

POST_TOWN

‘SPRINGFIELD’

SPRINGFIELD

POSTCODE

‘SP77 0SF’

SP77 0SF

Where null or empty string values exist (for character fields) or zeros or nulls (for integer fields), those fields should be entirely omitted from the output. However, the order in which the fields should be concatenated always remains the same, as shown in the following example:

Delivery Point Address component

Data content

Formatted output

DEPARTMENT_NAME

null

ORGANISATION_NAME

‘TM MOTORS’

TM MOTORS

SUB_BUILDING_NAME

null

BUILDING_NAME

‘THE OLD BARN’

THE OLD BARN

BUILDING_NUMBER

0 (or null)

PO_BOX_NUMBER

0 (or null)

DEPENDENT_THOROUGHFARE

null

THOROUGHFARE

‘HORSHAM LANE’

HORSHAM LANE

DOUBLE_DEPENDENT_LOCALITY

null

DEPENDENT_LOCALITY

null

POST_TOWN

‘HORSHAM’

HORSHAM

POSTCODE

‘RH12 1EQ’

RH12 1EQ

Building a single-line Delivery Point Address

Building a single-line, formatted address for a Delivery Point is relatively straightforward. All the fields should be checked in the order shown previously in the tables above, and those that have values should be concatenated together into a single line. Generally, address components should be separated by a comma followed by a single space (‘, ’), although sometimes only a space is used between a building number and a thoroughfare name. You can use your preference.

  • The SQL operator for concatenating text is a double pipe (‘||’).

  • CASE blocks have been used to test each of the fields for null values before concatenating its contents (along with a suitable separator: either ‘, ‘ or ‘ ‘).

  • The field names and table names used are illustrative and may vary between databases.

  • Depending on the database schema and data loading method used, it may be necessary to test some fields for empty strings (‘’) or zero values (for integer fields) instead of, or as well as, testing for NULLs.

  • If you are using PostGres (PostGIS), it might be beneficial to substitute the ‘IS NOT NULL’ with != ‘’. This should improve the overall appearance of the output.

Building a multi-line Delivery Point Address

Splitting a Delivery Point Address into multiple lines is more complicated. There are several rules to consider in order to avoid having very short lines (for example, just a building number) or very long lines within the formatted address. A summary of these rules is as follows:

  • Generally, if there is a building number, it should appear on the same line as the thoroughfare (or dependent thoroughfare). If there is no thoroughfare information, the building number should appear on the same line as the first locality line.

  • In cases where building numbers have been placed in the building name field due to the presence of a letter suffix (for example, ‘11A’) or a number range separator (for example, ‘3-5’), these should be detected and placed on the same line as the thoroughfare (or on the first locality line if no thoroughfare is present).

  • In most other cases, the building name, if present, should appear on a separate line above the thoroughfare name or dependent thoroughfare or locality line if no thoroughfare is present.

  • Similar tests should be applied to the SUB_BUILDING_NAME field: if this field contains a number, a number with a suffix or a numeric range, it should precede the building name on the same line. In most other cases, it should appear on a separate line above the building name.

Geographic Address (Local Authority Address)

The structure of a Geographic Address is based on the British Standard BS7666 and is split into a number of components. This means that in order to construct a complete address label, for example, on an envelope, database form or GIS display, the components need to be constructed according to a set of rules.

Within the AddressBase products, the core property-level address information is stored within the Primary Addressable Object (PAO) and Secondary Addressable Object (SAO) fields of the LPI table. The additional attribution required to build a full address label is maintained in the BLPU (postcode_locator), ORGANISATION (organisation) and STREET_DESCRIPTOR (street_description, locality_name, town_name, administrative_area) tables.

Constructing a single address label from the Geographic Address fields

To construct a single address label based purely on the BS7666 address fields, the following attributes listed in the table below should be used to build a Geographic Address label.

The following table details the Geographic Address components.

Table
Geographic Address Component

Organisation

ORGANISATION

LPI

SAO_TEXT

LPI

SAO_START_NUMBER

LPI

SAO_START_SUFFIX

LPI

SAO_END_NUMBER

LPI

SAO_END_SUFFIX

LPI

PAO_TEXT

LPI

PAO_START_NUMBER

LPI

PAO_START_SUFFIX

LPI

PAO_END_NUMBER

LPI

PAO_END_SUFFIX

Street Descriptor

STREET_DESCRIPTION

Street Descriptor

LOCALITY

Street Descriptor

TOWN_NAME

Street Descriptor

ADMINISTRATIVE_AREA*

BLPU

POSTCODE_LOCATOR

*ADMINISTRATIVE_AREA is optional because it is common for this field to be the same as the TOWN_NAME. Sometimes, however, this field will help users construct a more complete address.

These address components are listed in the correct order in which they should appear on an address label. There may be a business need to build the address using the alternate language for SAO_TEXT, PAO_TEXT and Street Descriptor entries. This can be achieved by filtering on the language field of the LPI and Street Descriptor tables. The same order as above would be applicable.

Linking address components

The LPI table includes the PAO and SAO fields. However, in order to obtain the rest of the address, it is necessary to join the LPI table to the Street Descriptor table to pick up the street name, locality and town information (using the USRN as the key), and also to the Organisation and BLPU tables (using the UPRN as the key) to pick up the organisation names and postcodes, respectively.

The diagram below shows the links that need to be made in order to build a full Geographic Address from the different BS7666 components in AddressBase Premium.

Using the LPI table as a starting point, the remaining address components can be picked up using table joins to the other tables on UPRNs and USRNs. Note that there can be more than one LPI for each UPRN, so if only one address is required per BLPU, the LPI with logical_status = 1 (approved) should be selected (there can be only one approved LPI per BLPU).

Rendering SAOs and PAOs

When building a single address label, it may be necessary to concatenate the various SAO fields and PAO fields together respectively. These fields contain any property names, numbers, number ranges or suffixes that apply to an address.

A PAO number / range string should be constructed from the PAO_START_NUMBER, PAO_START_SUFFIX, PAO_ END_NUMBER and PAO_END_SUFFIX fields, as illustrated in the following table:

Attribute
Example 1
Example 2
Example 3
Example 4

PAO_START_NUMBER

1

1

1

1

PAO_START_SUFFIX

A

A

PAO_END_NUMBER

5

5

PAO_END_SUFFIX

C

Rendered PAO range

1

1A

1-5

1A-5C

Similarly, a SAO number / range string should be constructed from the SAO_START_NUMBER, SAO_START_ SUFFIX, SAO_END_NUMBER and SAO_END_SUFFIX fields.

In addition to the numeric range fields described above, there are also PAO_text and SAO_text fields. These fields may be populated instead of, or as well as, the numeric range fields. In both cases, if both text and a numeric range string are present, the text should appear before the numeric range in any formatted address, as shown in the following table:

Attribute
Example 1
Example 2
Example 3
Example 4

PAO (number string)

1

1A

1A

PAO (text)

Rose Cottage

Rose Cottage

Rendered PAO (showing street name location)

1 <street>

1A <street>

Rose Cottage, 1A

<street>

Rose Cottage,

<street>

For primary addressable objects (PAOs), there will always be either a text entry or a numeric/range entry or both. This is not the case for SAOs, which may be entirely absent for a given address.

Street description, town, locality and administrative area names

The street description and administrative area names are always present, while the locality name and town name may be empty.

The ADMINISTRATIVE_AREA field always contains a value; however, this value will not always enhance an address, but in some cases it will. In particular, check that it is not the same as the value in the TOWN_NAME field, as is often the case. The following table shows an example where the administrative area name (in this case, BURY) has been included and excluded from a single-line address:

Administrative area not included

34, CROW LANE, RAMSBOTTOM, BL0 9BR

Administrative area included (BURY)

34, CROW LANE, RAMSBOTTOM, BURY, BL0 9BR

In other cases, the administrative area name will simply contain the local authority name, which would not traditionally form part of a single or multi-line address but can be included to add additional information to an address label. Its inclusion is largely down to business requirements or personal preference; however, it may also be useful to 'de-duplicate' some Geographic Addresses.

The following (entirely fictional) example shows all of the BS7666 Geographic Address fields filled in and illustrates how they should be ordered in a single address label.

The table below details the Geographic Address formatting:

Geographic Address Component
Example

ORGANISATION

JW SIMPSON LTD

SAO_TEXT

THE ANNEXE

SAO (number / range string)*

1A

PAO_TEXT

THE OLD MILL

PAO (number / range string)*

7–9

STREET_DESCRIPTION

MAIN STREET

LOCALITY

HOOK

TOWN_NAME

WARSASH

ADMINISTRATIVE_AREA

SOUTHAMPTON

POSTCODE_LOCATOR

SO99 9ZZ

*The number/range strings are built from the relevant PAO / SAO start_number, start_suffix, end_number and end_suffix fields, as described above, and formatted as character strings.

Where an administrative area matches the town name, it should always be omitted.

Delivery Point Address Component
Data content
Formatted output

PAO_TEXT

‘HIGHBURY HOUSE’

HIGHBURY HOUSE

STREET_DESCRIPTION

‘HIGH STREET’

HIGH STREET

TOWN_NAME

‘SOUTHAMPTON’

SOUTHAMPTON

ADMINISTRATIVE_AREA

‘SOUTHAMPTON’

POSTCODE_LOCATOR

‘SO77 0SF’

SO77 0SF

Where null or empty string values exist (for character fields) or zeros or nulls (for integer fields), those fields should be entirely omitted from the output; however, the order in which the fields should be concatenated always remains the same.

Delivery Point Address Component
Data content
Formatted output

ORGANISATION

‘TM MOTORS’

TM MOTORS

SAO_TEXT

null

SAO (number / range string)*

null

PAO_TEXT

‘THE OLD BARN’

THE OLD BARN

PAO (number / range string)*

‘1’

1

STREET_DESCRIPTION

‘HORSHAM LANE’

HORSHAM LANE

LOCALITY_NAME

null

TOWN_NAME

‘HORSHAM’

HORSHAM

ADMINISTRATIVE_AREA

‘HORSHAM’

* Duplicate name omitted

POSTCODE_LOCATOR

‘RH12 1EQ’

‘RH12 1EQ’

Building a single-line Geographic Address

Building a single-line, formatted address for a Geographic Address is slightly more complicated than for a Delivery Point Address due to the need to pre-format the SAO and PAO number/range strings and join tables together. However, once this is done, the process is largely the same as before: the calculated fields should be checked in the order shown previously in the table above, and those that have values should be concatenated together into a single line. Generally, address components should be separated by a comma followed by a single space (‘, ’), although sometimes only a space is used between a PAO number/range string and a street description. This is down to personal preference.

  • The SQL operator for concatenating text is a double pipe (‘||’).

  • CASE blocks have been used to test each of the fields for null values before concatenating its contents (along with a suitable separator – either ‘, ‘ or ‘ ‘).

  • The field names and table names used are illustrative and may vary between databases.

  • Depending on the database schema and data loading method used, it may be necessary to test some fields for empty strings (‘’) or zero values (for integer fields) instead of, or as well as, testing for NULLs.

  • If you want no duplicate UPRNs to be returned an additional DISTINCT line needs to read DISTINCT(l.UPRN).

Building a multi-line Geographic Address

Splitting a Geographic Address into multiple lines is more complex. As with Delivery Point Addresses, there are several rules to consider in order to avoid having very short lines (for example, just a building number) or very long lines within the formatted address.

A summary of these rules is as follows:

  • Generally, if there is a PAO number/range string, it should appear on the same line as the Street Description. 11A MAIN STREET

  • If there is a PAO_text value, it should always appear on the line above the Street Name (or on the line above the <PAO number string> + <Street Name> where there is a PAO number/range). PAO_text only ROSE COTTAGE, MAIN STREET PAO_text and PAO number or range ROSE COTTAGE, 11A MAIN STREET

  • If there is a SAO_text value, it should appear on a separate line above the PAO_text line (or the PAO number/range + street line where there is no PAO_text value). SAO_text value only, with PAO_text value only THE ANNEXE, ROSE COURT,

    MAIN STREET SAO_text value only, with PAO number/range only THE ANNEXE, 11A MAIN STREET

  • If there is a SAO number/range value, it should be inserted either on the same line as the PAO_text (if there is a PAO_text value), or on the same line as the PAO number/range + Street Name (if there is only a PAO number/range value and no PAO_text value). If there are both PAO_text and a PAO number/range, then the SAO number/range should appear on the same line as the PAO_text, and the PAO number/range should appear on the street line. SAO number/range value only, and PAO_text value only 1A ROSE COURT, MAIN STREET SAO number/range value only, and PAO number/range value only 1-3, 11A MAIN STREET SAO number/range value only, and both PAO_text and PAO number/range values 1A ROSE COURT,

    11A MAIN STREET

  • If there is a SAO_text value, it should always appear on its own line. SAO_text value only with PAO_text only THE ANNEXE, ROSE COTTAGE, MAIN STREET SAO_text and SAO number/range and PAO_text and PAO number/range WARDEN’S FLAT, 1A ROSE COURT,

    11A MAIN STREET

  • If there is an Organisation Name, it should always appear alone as the top line of the address. Organisation Name along with all PAO + SAO fields COTTAGE INDUSTRY LTD, THE ANNEXE, 1A ROSE COURT, 11A MAIN STREET

  • The Locality (if present) should appear on a separate line beneath the Street Description, followed by the Town Name on the line below it. If there is no Locality, the Town Name should appear alone on the line beneath the Street Description. Locality and Town Name present [first part of address, formatted as described above] MAIN STREET,

    HIGHFIELD,

    SOUTHAMPTON Town Name only [first part of address, formatted as described above] HIGH STREET,

    SOUTHAMPTON

  • If the Administrative Area name is required and it is not a duplicate of the Town Name, it can optionally be included on a separate line beneath the Town Name. Administrative Area name included [first part of address, formatted as described above] MAIN STREET, WINDSOR, ROYAL BOROUGH OF WINDSOR AND MAIDENHEAD

  • Finally, the Postcode Locator should be inserted on the final line of the address. With Postcode_Locator on final line [first part of address, formatted as described above] HIGH STREET, MILTON, ML99 0WW

Advice on creating mailing lists using AddressBase Premium products

It's possible to create mailing lists using the AddressBase Premium and AddressBase Premium Islands products (you can also create them using AddressBase Plus and AddressBase Plus Islands). 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 business requirements, in some user interfaces, 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.

Address status

When building your query to extract a mailing list, it is important that you consider filtering your results based on the address status and type. The status of an address is often something that needs to be considered when working with address data. Questions need to be answered before AddressBase Premium can be used effectively, such as “Is the addressable object in planning, being constructed, current, demolished or accurately positioned?”.

Status attributes
Table
Use
Values

LOGICAL_STATUS

BLPU

Describes where a land or property unit is in its lifecycle.

1 = Approved

6 = Provisional

8 = Historical

LOGICAL_STATUS

LPI

Describes where an address is in its lifecycle.

1 = Approved

3 = Alternative

6 = Provisional

8 = Historical

BLPU_STATE_CO DE

(optional)

BLPU

Informs the user what physical state the land or property is in (for example, ‘under construction’, ‘in use’, ‘demolished’).

1 = Under construction

2 = In use

2 = Unoccupied

4 = No longer existing

6 = Planning permission granted Null= Unknown or N/A

RPC_CODE

BLPU

To ascertain how accurate the coordinate is. Use in conjunction with the postcode_locator field to understand the accuracy of the address’ position.

1 = Visual centre

2 = General internal point

3 = SW corner of 100m grid ref

4 = Start of referenced street

5 = Postcode unit point

9 = Centre of Local Authority area

ADDRESSBASE_ POSTAL

BLPU

This field can be used to limit your records based on whether they are capable of receiving mail or not.

D = A record which is linked to PAF

C = A record which is postal and has a parent linked to PAF

L = A record identified as postal via Local Authority information

N = Not a postal address

LANGUAGE

LPI STREET_DESCRIPTOR

This information can be used to limit your records based on the language.

ENG = English CYM = Welsh GAE = Gaelic

Other filters available in AddressBase Premium products for use in addressing labels

AddressBase Premium is a rich addressing dataset that contains a wealth of other attributes that could be used in conjunction with address labels. For example:

  • Classification can be used to target certain types of property.

  • OS MasterMap Topography TOID cross references can be used to link address labels to Topographic objects and viewed in a GIS for Great Britain (AddressBase Premium Islands does not has OS MasterMap Topography TOID cross references).

Examples of SQL logic to create a single-line Delivery Point Address are on our , which incorporates the following elements:

For a full description of PAOs and SAOs, and the complete set of AddressBase fields, please refer to the relevant

Example SQL logic to create a single-line Geographic Address can be found on our , which incorporates the following elements:

The table below offers guidance on what status filters should be considered. Please see the on our website for more information about each of these attributes.

GitHub repository
AddressBase Premium Technical Specification.
GitHub repository
AddressBase Premium technical specification
AddressBase Premium high-level data model diagram with address ‘types’ highlighted.
Table join logic diagram for Geographic Address label
AddressBase Premium high-level data model diagram with address ‘types’ highlighted.
Table join logic diagram for Geographic Address label