Scotland AddressBase update Chris Chambers Address Portfolio Product Manager

Overview 1.2 years of progress 2.Benefits of AddressBase 3.What we’ve achieved to date 4.Still lots to do

Remember the start? WE DO!

In the beginning…. APALAL2 NLPG OSG

The challenge Synchronise data from five primary feeds each with a different specification, different quality protocols and different update cycles. England and WalesScotland NLPGAL2PAFVOAAL2OSG 30.76m BLPU’s 33.36m LPI’s 25.1m PAF 1.2m OWPA 25.1m DP’s 0.1m PO Box 24.3m CTax 1.8m NDR 2.6m PAF 0.18m OWPA 3.13m BLPU’s 3.21m LPI’s updates from 348 local authorities Six weekly full re-supply Monthly full re-supply, moving to daily updates Monthly updates with annual reconciliation Six weekly full re-supply updates from 32 local authorities Street BLPU’s Parent Shells Multi res OS/NLPG OWPA’s Organisations Successors Classification s

The benefits Single source of public sector owned national spatial address data Single national address data for public and private sector Facilitates data sharing Removes address matching costs More effective decision-making, supporting: Policy development Service delivery Monitoring Government efficiency – one database

Benefits of AddressBase

Product differentials AddressBaseAddressBase PlusAddressBase Premium UPRN Coordinates Classification (primary only)Classification Royal Mail Postal Address Royal Mail UDPRN Local Authority Geographic Address Local Authority meta data XREF to OSMM TOIDS Multiple occupancy addresses OWPAs Provisional properties (pre- build) Historic properties Alternative addresses Provisional addresses Historic Addresses Application cross references

AddressBase Numbers AddressBase™AddressBase™ PlusAddressBase™ Premium* PAF address 27,491,761 Geo address – LPI (Approved) + 6,575,799+ 8,047,474** Geo address – LPI (Alternative) + 972,663 Geo address – LPI (Provisional) + 422,539 Geo address – LPI (Historic) + 2,197,376 Total27,491,761 34,067,56039,131,887*** *stats based on LPIs not BLPUs. ** Different to AB Plus Geo address (Approved) because of historic BLPUs. E.g. single property that had single address that was demolished. ***LPI Addresses – includes ~1.2m Street Descriptor records

Compared to ADDRESS-POINT ADDRESS-POINTAddressBase™AddressBase™ Plus AddressBase™ Premium ∑ addresses 28,294,367* 27,491,761 34,067,56039,131,887*** Classification= Primary<= Quaternary MOWPAs 2,018,847**2,129,087** OWPAs 3,822,232**4,926,626** Provisional422,539** Alternative972,663** Historic2,197,376** USRN X-Ref *more records due to inclusion of deletions (~80k), out of product scope (~400k) and currently out to be matched, (~350k) **These numbers are included in the total count of addresses for this product ***LPI Addresses – includes ~1.2m Street Descriptor records

Compared to OSMM Address Layer Address LayerAddressBase™AddressBase™ Plus AddressBase™ Premium ∑ addresses 28,294,367* 27,491,761 34,067,56039,131,887*** Classification= Primary<= Quaternary MOWPAs 2,018,847**2,129,087** OWPAs 3,822,232**4,926,626** Provisional422,539** Alternative972,663** Historic2,197,376** USRN X-Ref *more records due to inclusion of deletions (~80k), out of product scope (~400k) and currently out to be matched, (~350k) **These numbers are included in the total count of addresses for this product ***LPI Addresses – includes ~1.2m Street Descriptor records

Compared to OSMM Address Layer 2 Address Layer 2AddressBase™AddressBase™ Plus AddressBase™ Premium ∑ addresses 30,485,241 27,491,761 34,067,56039,131,887*** Classification<= Quaternary= Primary<= Quaternary MOWPAs 667,385**2,018,847**2,129,087** OWPAs 1,407,909**3,822,232**4,926,626** Provisional422,539** Alternative972,663** Historic2,197,376** USRN X-Ref **These numbers are included in the total count of addresses for this product ***LPI Addresses – includes ~1.2m Street Descriptor records

Comparison of all products Postal**OWPAs**MOWPAs*LifecycleTotal AddressBase™ 27,491,761 AddressBase™ Plus 28,226,4813,822,2322,018,84734,067,560 AddressBase™ Premium 30,670,8933,822,232 2,018,847 2,619,91539,131,887* ADDRESS-POINT 28,294,367 OSMM Address Layer 28,294,367 OSMM Address Layer 2 28,409,9471,407,909667,38530,485,241 * LPI Addresses – includes 1.2m Street Descriptor records **Current Approved status or equivalent

What we’ve achieved to date: Key Milestones

AddressBase products – timeline and deliverables Epoch releaseKey Deliverables Epoch 1- Oct 11AddressBase products launched- England and Wales coverage only Epochs 2-5 Nov/Apr 11Managing data transfer system and assessing One Scotland Gazetteer data Epoch 6-May 12GB coverage release-One Scotland Gazetteer data imported Epochs 7-9 June/Sept12Continued system management and data content Change Request assessment Epoch 10 - Oct 12Data content Change Request improvements imported Epoch 11- Nov 12Production and delivery system improvements Epochs Jan 13Content additions and system developments applied Epoch 14- April 13Scottish Objects Without Postal Addresses added Epoch 15-May 13Phase 1- Change Only Update release Partners/ system suppliers / Priority customers Epoch 16-July 13Phase 2- COU release to all on a COU supply schedule

PAF matching SuppliedMatchedUnmatchedMatch rate (%) North West3,313,6403,270,15436, East Midlands2,091,3962,073,35513, West Midlands25,122,142,480,30624, East of England2,687,1852,659,94318, South East3,891,6763,851,98320, Greater London3,411,5423,318,04674, Yorkshire2,450,0492,430,6829, North East1,238,3541,226,2137, South West2,529,6182,491,11029, England24,125,67423,801,792234, Wales1,447,6881,437,9823, Scotland2,644,7272,538,73392, Great Britain28,218,08927,778,507330,

PAF matching 255 of the 380 Contributing Authorities have OVER 99% PAF match rate Some of the best: CARLISLENORTH WEST TORRIDGESOUTH WEST MALDONEAST OF ENGLAND NORTH LINCOLNSHIREYORKSHIRE STAFFORDSHIRE MOORLANDSWEST MIDLANDS FOREST HEATHEAST OF ENGLAND PEMBROKESHIREWALES MERTHYR TYDFIL UAWALES NEWPORTWALES TORFAENWALES CLACKMANNANSCOTLAND INVERCLYDESCOTLAND

VOA Matching – Council tax RegionData SuppliedMatchedOutcomedUnresolved Match Rate (%) North West3,170,7953,166, , E Midlands1,994,0621,991,983512, W Midlands2,391,2062,388,266592, E England2,561,7772,557,782793, South East3,728,7313,721,776816, London3,423,1053,411, , Wales1,391,4291,390, Yorkshire2,337,9432,335, , North East1,187,2211,185, , South West2,424,1432,418, , TOTAL24,610,41224,568,5901,31540,

VOA Matching - NDR RegionData SuppliedMatchedOutcomedUnresolved Match Rate (%) North West247,483222, , E Midlands140,071134, , W Midlands186,096163,8142,07020, E England187,077171,1881,23514, South East258,693245, , London288,322258,6731,09128, Wales106,652106, Yorkshire181,115173, , North East77,80272, , South West195,465179,6891,21214, TOTAL1,868,7761,727,8908,600132,

What we’ve achieved to date: Data Improvements

Total number of BLPUs

Total number of addresses (LPIs)

Increased PAF matching

Improved classifications

Still lots to do

Still lots to do – short term

PAF Inclusion ~700,000 records contained within PAF that are not within AddressBase. ~350,000 are out with Custodians for matching ~350,000 are not in product because of specification changes Reasons for non-inclusion: Multiple PAF records to a single BLPU PAF record without a matching BLPU

PAF Inclusion Why it’s needed: National Entitlement Card Citizens Account Police – National Firearms database Insurance – insuring properties / businesses Utilities – ensuring everyone is paying (reducing bills) Fraud – claims from bogus addresses ~42,000 PAF users ~900 Legacy OS Address Product customers Postcode

PAF Inclusion What we’re doing: Including one of the many PAF records matched to a single BLPU. ~80,000 in Epoch 20 / 21. Analysing the feasibility / impact of including: Many PAF records to a single BLPU ~160,000 PAF records not matched to an LPI record

Coordinates A difference in coordinates in approximately 6% of AddressBase and Topographic feature referenced. AL2 not always better Rules have been written and tested Now working out best method of implementation

Coordinates Centre of BLPU PAI

Coordinates Building Geometry Start of street

Coordinates Stacked (inside a building) Stacked (outside a building)

Coordinates

Coordinates – what it is

Coordinates – what it’s not…yet…

Postcode_Locator Currently spatially derived from Code-Point with Polygons (point in polygon) Issues around ‘Vertical Streets’ - Where two or more postcodes are associated with a single building seed, a single distinctive square polygon will represent all the postcodes attached to the seed. These polygons have a special series of identifiers, all commencing with the letter V.

Postcode_Locator Change based on feedback: 1.Royal Mail postcode where matched 2.LLPG postcode where unmatched 3.Spatially derived where unpopulated Planned implementation of Epoch 21, Feb 2014 SourceCOUNT(*)NUM_DIFFERENCES Royal Mail25,069,341732,231 NLPG4,726,5381,361,672 OSG436,17693,312 Code-Point5,719,6800

Still lots to do – longer term

Classification Scotland Count %England Count %Wales Count % Primary106, ,276, , Secondary2,061, ,285, ,034, Tertiary783, ,222, , Quaternary80, , , Unclassified391, , Total3,421, ,597, ,841,012100

Classification

Increased non-addressables (OWPAs) Demand from Emergency Services Demand from Central Government Due to inconsistent capture E.g: AddressBase Premium COUNTOS MasterMap AL2COUNT CLASSIFICATION_CODE = 'LW01' 1846 OS_CLASS = 'RESERVOIR' 12396

Building type

Level information

What I believe the priorities are… 1.Coordinates within building footprint 2.All PAF records within product 3.Improved Classification and Business names 4.More frequent supply of data – monthly, weekly, daily, live? 5.Different supply methods – API? 6.Candidate process – you tell us! 7.Level information. What do you actually want? 8.UK Coverage 9.Greater support to partners 10.More consistent capture of Provisional and Historic address data

Collaboration GREAT work so far… You’re not alone… What’s stopping you achieving your goals… What can WE do to help?

Questions