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
  • Introduction to COU
  • Types of change within a COU
  • High-level COU implementation model
  • High-level COU implementation model – with archiving
  • Applying COU to tables
  • Changes to the BLPU table
  • Changes to the Classification table
  • Changes to the Organisation table
  • Changes to the Delivery Point Address table
  • Changes to the Land and Property Identifier table
  • Changes to the Street table
  • Changes to the Street Descriptor table
  • Changes to the Cross Reference table

Was this helpful?

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

Working with COU data

PreviousWorking with GML dataNextCreating a single-line or multi-line address

Last updated 8 months ago

Was this helpful?

Introduction to COU

AddressBase Premium and AddressBase Premium Islands are complex relational datasets that are used by a variety of customers who use a variety of methods and software to manage the data. Some of the software solutions take a considerable length of time to load and manage the data. A change-only update (COU) is a simple and effective way to keep data holdings up to date without spending considerable time loading and managing a full supply every time the data is refreshed.

A COU means you will only be supplied with the features which have changed since your last supply. The following sub-sections provide guidance on how to manage a COU supply of AddressBase Premium data.

Note - If you receive a tile supply, you will receive Change Chunks. This means if a record within your tile has changed, then all of the records in that tile will be provided to you as inserts, and no updates or deletes will be issued. This is not applicable for AddressBase Premium Islands as a tile supply is not available for that product.

Types of change within a COU

At a high-level, there are three types of change found within a COU:

  1. Deletes (CHANGE_TYPE ‘D’) are objects that have ceased to exist in your area of interest (AOI) since the last product refresh.

  2. Inserts (CHANGE_TYPE ‘I’) are objects that have been newly inserted into your AOI since the last product refresh.

  3. Updates (CHANGE_TYPE ‘U’) are objects that have been updated in your AOI since the last product refresh.

High-level COU implementation model

The diagram below outlines how to implement the AddressBase Premium COU within a database. It also shows the necessary primary keys needed to implement the COU for each relational table.

High-level COU implementation model – with archiving

Before a COU is applied, there may be a business requirement to archive existing address records. The diagram below outlines how to implement the AddressBase Premium COU within a database, shows the necessary primary keys needed to implement the COU for each relational table, and how to archive existing records.

Applying COU to tables

Changes to the BLPU table

Within the Basic Land and Property Unit (BLPU) table, there will not be any records with the same UPRN. This can be tested by checking the number of records that have the same UPRN. The following SQL code would notify you of any duplicates:

SELECT uprn, COUNT(uprn) AS NumOccurrences FROM abp_blpu
GROUP BY uprn
HAVING ( COUNT(uprn) > 1 );

This query should return 0 rows, and this confirms there are no duplicates. As there are no duplicate records, the UPRN can be used to apply the COU. Once confirmed, the following steps can be taken to apply the COU (without archiving):

Initially delete the existing records that will be updated and delete

DELETE FROM abp_blpu WHERE uprn IN (SELECT distinct uprn FROM abp_blpu_cou WHERE change_type!= ‘I’);

Insert the new updated records and the newly inserted records

INSERT INTO abp_blpu SELECT * FROM abp_blpu_cou WHERE change_type != ‘D’;

Some of the COU records that are change type ‘U’ (updates) may change the Logical Status Code from ‘1’ to ‘8’, meaning that this address has become ‘Historical’. This means that the BLPU table intrinsically archives historical records.

Where there is a business requirement to keep the records that are being updated and deleted in a separate archive table, the following SQL will create an Archive Table and populate it with records that are being Updated and Deleted from the live BLPU table.

The following command creates an archive table of the records that are being updated and deleted from the existing BLPU table: If this table already exists, you can simply use INSERT INTO rather than CREATE TABLE

CREATE TABLE abp_blpu_archive AS SELECT * FROM abp_blpu WHERE uprn IN (SELECT distinct uprn FROM abp_blpu_cou WHERE change_type != ‘I’);

The following command then deletes the records from the existing table which are either updates or deletions:

DELETE FROM abp_blpu WHERE uprn IN (SELECT distinct uprn FROM abp_blpu_cou WHERE change_type!= ‘I’);

The following command then inserts the new insert records and the new updated records into the live BLPU table:

INSERT INTO abp_blpu SELECT * FROM abp_blpu_cou WHERE change_type != ‘D’;

Changes to the Classification table

Because there is a one-to-many relationship between the BLPU table and the Classification table, there can be records in the Classification table that share a UPRN. To apply COU to the correct record, users should use the Class_Key to ensure that the correct classification record is updated.

The table below provides examples of using the Class_Key to apply a COU to one of two classification records that share a UPRN in a Classification table.

Classification
Record 1
Record 2
Classification
Updated record
Record 2
Classification
COU record

Record identifier

32

32

Record identifier

32

32

Record identifier

32

Change type

I

I

Change type

U

I

Change type

U

Pro order

922371

922372

Pro order

922500

922372

Pro order

922500

UPRN

100062645004

100062645004

UPRN

100062645004

100062645004

UPRN

100062645004

Class key

1715C000002050

1715C802457028

Class key

1715C000002881

1715C802457028

Class key

1715C000002881

Classification code

U

CS

Classification code

CR08

CS

Classification code

CR08

Class scheme

AddressBase Premium classification scheme

VOA Primary Description

Class scheme

AddressBase Premium classification scheme

VOA Primary Description

Class scheme

AddressBase Premium classification scheme

Scheme version

1.0.0

1.0.0

Scheme version

1.0.0

1.0.0

Scheme version

1.0.0

Start date

2011-12-01

2010-03-16

Start date

2011-12-01

2010-01-16

Start date

2011-12-01

End date

N/A

N/A

End date

N/A

N/A

End date

N/A

Last update

2011-12-01

2010-08-12

Last update date

2013-05-04

2010-08-12

Last update

2013-05-04

Entry date

2011-12-01

2010-03-16

Entry date

2011-12-01

2010-03-16

Entry date

2011-12-01

The example in classification code table above illustrates a scenario when a user would need to choose between two classification records that have the same UPRN. In this case, the Class_Key has been used to apply the COU to Record 2.

To achieve this outcome (without archiving the ‘old’ Record 2), we can use the following SQL commands to apply the COU:

Initially delete the existing records that are being updated and deleted:

DELETE FROM abp_classification WHERE class_key IN (SELECT distinct class_key FROM abp_ classification_cou WHERE change_type != ‘I’);

Insert the new update records and the new insert records:

INSERT INTO abp_classification SELECT * FROM abp_classification_cou WHERE change_type != ‘D’;

One thing you may want to consider is keeping an archive of the updated and deleted classification records. For example, this might be useful to understand when an address has changed use from residential to commercial.

To achieve this outcome for change types ‘U’ (updates) or ‘D’ (deletes) (with archiving), we can use the following SQL commands to apply the COU:

The following command creates an archive table of the records that are being updated and deleted from the existing Classification table. If this table already exists, you can simply use INSERT INTO rather than CREATE TABLE:

CREATE TABLE abp_classification_archive AS SELECT * FROM abp_classification WHERE class_key IN (SELECT distinct class_key FROM abp_classification_cou WHERE change_type != ‘I’);

The following command then deletes the records from the existing table that are either updates or deletions:

DELETE FROM abp_classification WHERE class_key IN (SELECT distinct class_key FROM aabp_ classification_cou WHERE change_type != ‘I’);

The following command then inserts the new insert records and the new updated records into the Classification table:

INSERT INTO abp_classification SELECT * FROM abp_classification_cou WHERE change_type != ‘D’;

The following table shows classification and archive record details:

Classification
Archive record

Record identifier

32

Change type

I

Pro order

706838

UPRN

116000665

Class key

9055C000081107

Classification code

CL10RE

Class scheme

AddressBase Premium classification scheme

Scheme version

1.0.0

Start date

2011-12-01

End date

N/A

Last update date

2011-12-01

Entry date

2011-12-01

When the updated or deleted records are moved into an archive table, the end date may not always be populated, as seen in Table 4. If this is the case, users may wish to consider adding an end_date (which could be based on the epoch date that it was archived) as shown in Table 5. Adding an end date to an updated or deleted record will enable querying for a particular timeframe.

The following table shows classification and archive record with an end date details:

Classification
Archive record

Record identifier

32

Change type

I

Pro order

706838

UPRN

116000665

Class key

9055C000081107

Classification code

CL10RE

Class scheme

AddressBase Premium classification scheme

Scheme version

1.0.0

Start date

2011-12-01

End date

2013-05-04

Last update date

2011-12-01

Entry date

2011-12-01

Changes to the Organisation table

The numerous one-to-many relationships between the BLPU table and the Organisation table mean there can be records in the Organisation table that share a UPRN. To apply COU to the correct record, we should use the Org_Key to ensure that the correct classification record is updated.

To apply the COU to the Organisation table (without archiving), the following code can be used:

Initially delete the existing records that will be updated and deleted:

DELETE FROM abp_organisation WHERE org_key IN (SELECT distinct org_key FROM abp_organisation_ cou WHERE change_type != ‘I’);

Insert the new updated records and the newly inserted records:

INSERT INTO abp_organisation SELECT * FROM abp_organisation_cou WHERE change_type != ‘D’;

As with the Classification table, the changes in Organisation name may be useful to keep as archives as doing so will allow a business to find previous organisations and understand when name changes were made.

To apply the COU to the Organisation table (with archiving), the following code can be used:

The following command creates an archive table of the records that are being updated and deleted from the existing Organisation table. If this table already exists, you can simply use INSERT INTO rather than CREATE TABLE:

CREATE TABLE abp_organisation_archive AS SELECT * FROM abp_organisation WHERE org_key IN (SELECT distinct org_key FROM abp_organisation_cou WHERE change_type != ‘I’);

The following command then deletes the records from the existing table that are either updates or deletions:

DELETE FROM abp_organisation WHERE org_key IN (SELECT distinct org_key FROM aabp_organisation_ cou WHERE change_type != ‘I’);

The following command then inserts the new insert records and the new updated records into the Organisation table:

INSERT INTO abp_organisation SELECT * FROM abp_organisation_cou WHERE change_type != ‘D’;

Changes to the Delivery Point Address table

Within the Delivery Point Address table, there will not be any records with the same Unique Delivery Point Reference Number (UDPRN). This can be tested by checking the number of records that have the same UDPRN. The following SQL code would notify you of any duplicates:

SELECT udprn, COUNT(udprn) AS NumOccurrences FROM abp_delivery_point GROUP BY udprn
HAVING (COUNT(udprn) > 1 );

This query should return 0 rows, and this confirms that there are no duplicates. As there are no duplicate records, we can therefore use the UDPRN to apply the COU.

To apply the COU to the Delivery Point Address table (without archiving), the following code can be used:

Initially delete the existing records that will be updated and deleted:

DELETE FROM abp_delivery_point WHERE udprn IN (SELECT distinct udprn FROM abp_delivery_point_cou WHERE change_type != ‘I’);

Insert the new updated records and the new inserted records:

INSERT INTO abp_delivery_point SELECT * FROM abp_delivery_point_cou WHERE change_type != ‘D’;

The Delivery Point Address table does not have the ability to hold historical records as it is the current view of the Royal Mail Delivery Point Address File (PAF). Therefore, in order to capture the historical records, you will need to create an archive table that is populated when records are either deleted or updated. The following code will create the archive records:

To apply the COU to the Delivery Point Address table (with archiving), the following code can be used:

The following command creates an archive table of the records that are being updated and deleted from the existing Delivery Point Address table. If this table already exists, you can simply use INSERT INTO rather than CREATE TABLE:

CREATE TABLE abp_delivery_point_archive AS SELECT * FROM abp_delivery_point WHERE udprn IN (SELECT distinct udprn FROM abp_delivery_point_cou
WHERE change_type != ‘I’);

The following command then deletes the records from the existing table that are either updates or deletions:

DELETE FROM abp_delivery_point WHERE udprn IN (SELECT distinct udprn FROM abp_delivery_point_cou WHERE change_type != ‘I’);

The following command then inserts the new insert records and the new updated records into the Delivery Point Address table:

INSERT INTO abp_delivery_point SELECT * FROM abp_delivery_point_cou WHERE change_type != ‘D’;

Changes to the Land and Property Identifier table

The numerous one-to-many relationships between the BLPU table and the Land and Property Identifier (LPI) table mean there can be records in the LPI table that share a UPRN. To apply the COU to the correct record, we should use the LPI_Key to ensure that the correct classification record is updated.

To apply the COU to the LPI table (without archiving), the following code can be used:

Initially delete the existing records that will be updated and deleted:

DELETE FROM abp_lpi WHERE lpi_key IN (SELECT distinct lpi_key FROM abp_lpi_cou WHERE change_type != ‘I’);

Insert the new updated records and the new inserted records:

INSERT INTO abp_lpi SELECT * FROM abp_lpi_cou WHERE change_type != ‘D’;

As with the BLPU table, some of the COU records that are change type ‘U’ (updates) may change the Logical Status Code from ‘1’ to ‘8’, meaning that this address has become ‘historical’. This means that the LPI table intrinsically archives the historical record.

Where there is a business requirement to keep the records that are being updated and deleted in a separate archive table, the following SQL will create an archive table and populate it with records that are being updated and deleted from the live LPI table.

To apply the COU to the LPI table (with archiving), the following code can be used:

The following command creates an archive table of the records that are being updated and deleted from the existing LPI table. If this table already exists, you can simply use INSERT INTO rather than CREATE TABLE:

CREATE TABLE abp_lpi_archive AS SELECT * FROM abp_lpi WHERE lpi_key IN (SELECT distinct lpi_key FROM abp_ lpi_cou WHERE change_type != ‘I’);

The following command then deletes the records from the existing table which are either updates or deletions:

DELETE FROM abp_lpi WHERE lpi_key IN (SELECT distinct lpi_key FROM abp_lpi_cou WHERE change_type != ‘I’);

The following command then inserts the new insert records and the new updated records into the LPI table:

INSERT INTO abp_lpi SELECT * FROM abp_lpi_cou WHERE change_type != ‘D’;

The following table shows an original LPI record next to a COU record. In this example, the record is being made historical (logical status code: 8) and therefore has a populated end date attribute.

LPI
Record
COU Record

Record identifier

24

24

Change type

I

U

Pro order

478857

478857

UPRN

100000527208

100000527208

LPI key

4520L000005174

4520L000005174

Language

ENG

ENG

Logical status

1

8

Start date

‘2001-03-23’

‘2001-03-23’

End date

‘2013-04-24’

Last update date

‘2010-05-21’

‘2013-04-24’

Entry date

‘2001-03-23’

‘2001-03-23’

SAO start number

SAO start suffix

SAO end number

SAO end suffix

SAO text

PAO start number

PAO start suffix

PAO end number

PAO end suffix

PAO text

‘SITE OF FORMER MISER NETHAULERS’

‘FORMER SITE OF MISER NETHAULERS’

USRN

36815950

36815950

USRN match indicator

1

1

Area name

Level

Official flag

Changes to the Street table

Within the Street table, there will not be any records with the same Unique Street Reference Number (USRN). This can be tested by checking the number of records that have the same USRN. The following SQL code would notify you of any duplicates:

SELECT usrn, COUNT(usrn) AS NumOccurrences FROM abp_street
GROUP BY usrn
HAVING ( COUNT(usrn) > 1 );

This query should return 0 rows, and this confirms there are no duplicates. As there are no duplicate records, we can use the USRN to apply the COU.

To apply the COU to the Street table (without archiving), the following code can be used:

Initially delete the existing records that will be updated and deleted:

DELETE FROM abp_street WHERE usrn IN (SELECT distinct usrn FROM abp_street_cou WHERE change_type != ‘I’);

Insert the new updated records and the new inserted records:

INSERT INTO abp_street SELECT * FROM abp_street_cou WHERE change_type != ‘D’;

The Street table does not have the ability to hold historical records as it does not have a Logical Status Code attribute. Therefore, to capture the historical records, you will need to create an archive table that is populated when records are either deleted or updated.

To apply the COU to the Street table (with archiving), the following code can be used:

The following command creates an archive table of the records that are being updated and deleted from the existing Street table. If this table already exists, you can simply use INSERT INTO rather than CREATE TABLE:

CREATE TABLE abp_street_archive AS SELECT * FROM abp_street WHERE usrn IN (SELECT distinct usrn FROM abp_ street_cou WHERE change_type != ‘I’);

The following command then deletes the records from the existing table that are either updates or deletions:

DELETE FROM abp_street WHERE usrn IN (SELECT distinct usrn FROM abp_street_cou WHERE change_type != ‘I’);

#The following command then inserts the new insert records and the new updated records into the Street table:

INSERT INTO abp_street SELECT * FROM abp_street_cou WHERE change_type != ‘D’;

Changes to the Street Descriptor table

Within the Street Descriptor table, there will not be any records with the same USRN and the same language. This is called a compound key, rather than having a single column as a Primary Key. This can be tested by checking the number of records that have the same USRN. The following SQL code will notify you of any duplicates:

SELECT usrn, language, COUNT(usrn) AS NumOccurrences FROM abp_street_descriptor
GROUP BY usrn, language HAVING ( COUNT(usrn) > 1 );

This query should return 0 rows, and this confirms there are no duplicates using the compound key. As there are no duplicate records, we can therefore use the USRN and LANGUAGE to apply the COU.

To apply the COU to the LPI table (without archiving), the following code can be used:

Initially delete the existing records that will be updated and deleted:

DELETE FROM abp_street_descriptor WHERE EXISTS (SELECT 1 FROM abp_street_descriptor_cou WHERE abp_street_descriptor_cou.usrn = abp_street_descriptor.usrn AND abp_street_descriptor_cou.language = abp_street_descriptor.language
AND abp_street_descriptor_cou.change_type != ‘I’ ) 

Insert the new updated records and the new inserted records:

INSERT INTO abp_street_descriptor SELECT * FROM abp_street_descriptor_cou WHERE change_type != ‘D’;

The Street Descriptor table does not have the ability to hold historical records as it does not have a Logical Status Code attribute. Therefore, to capture the historical records, you will need to create an archive table that is populated when records are either deleted or updated.

To apply the COU to the Street Descriptor table (with archiving), the following code can be used:

The following command creates an archive table of the records that are being updated and deleted from the existing Street table. If this table already exists, you can simply use INSERT INTO rather than CREATE TABLE:

CREATE TABLE abp_street_descriptor_archive AS SELECT * FROM abp_street_descriptor WHERE EXISTS (SELECT 1 FROM abp_street_descriptor_cou
WHERE abp_street_descriptor_cou.usrn = abp_street_descriptor.usrn AND abp_street_descriptor_cou.language = abp_street_descriptor.language AND abp_street_descriptor_cou.change_type != ‘I’ )

The following command then deletes the records from the existing table that are either updates or deletions:

DELETE FROM abp_street_descriptor WHERE usrn IN (SELECT distinct usrn FROM abp_street_descriptor_cou WHERE change_type != ‘I’);

The following command then inserts the new insert records and the new updated records into the Street table:

INSERT INTO abp_street_descriptor SELECT * FROM abp_street_descriptor_cou WHERE change_type != ‘D’;

Changes to the Cross Reference table

Within the Cross Reference table, there will not be any records with the same XREF_KEY. This can be tested by checking the number of records that have the same XREF_KEY. The following SQL code will notify you of any duplicates:

SELECT XREF_KEY, COUNT(XREF_KEY) AS NumOccurences FROM ABP_XREF
GROUP BY XREF_KEY
HAVING (COUNT(XREF_KEY) > 1);

The query above should return 0 rows and therefore confirms that there are no duplicates. As there are no duplicates, we can therefore use the XREF_KEY to apply the COU.

To apply the COU to the Cross Reference Table (without archiving), the following code can be used:

Initially delete the existing records that will be updated and deleted:

DELETE FROM ABP_XREF WHERE XREF_KEY IN (SELECT distinct XREF_KEY FROM ABP_XREF_COU WHERE CHANGE_TYPE != ‘I’);

Insert the new records and the updated records:

INSERT INTO ABP_XREF SELECT * FROM ABP_XREF_COU WHERE CHANGE_TYPE != ‘D’;

The Cross Reference table does not have the ability to hold historical records as it does not have a logical status code attribute. Therefore, to capture the historical records, you will need to create an archive table which is populated when records are either deleted or updated.

To apply the COU to the Cross Reference table (with archiving), the following code can be used:

The following command creates an archive table of records which are being updated and deleted from the existing Cross Reference table. If this table already exists, you can simply use INSERT INTO rather than CREATE TABLE:

CREATE TABLE ABP_XREF_ARCHIVE AS SELECT * FROM ABP_REF WHERE XREF_KEY IN (SELECT DISTINCT XREF_KEY FROM ABP_XREF_COU WHERE CHANGE_TYPE != ‘I’);

The following command then deletes the records from the existing table that are either updates or deletes:

DELETE FROM ABP_XREF WHERE XREF_KEY IN (SELECT DISTINCT XREF_KEY FROM ABP_XREF_COU WHERE CHANGE_TYPE != ‘I’);

The following command then inserts the new insert records and the updated records:

INSERT INTO ABP_XREF SELECT * FROM ABP_XREF_COU WHERE CHANGE_TYPE != ‘D’;
High-level COU implementation model diagram
High-level COU implementation model diagram showing how to create archive tables and apply a COU
High-level COU implementation model diagram
High-level COU implementation model diagram showing how to create archive tables and apply a COU