AddressBase Premium Islands - June 2024 release note

This release note provides information about the June 2024 release of AddressBase Islands Products

This section describes the features (one for CSV and GeoPackage, and two for GML) which make up the AddressBase Premium Islands product, giving the following information about each attribute:

AddressBase Premium Islands feature type attributes

Name and Definition

The name of the attribute and what it is describing.

Condition

A condition associated with this attribute (optional).

Attribute Type

The nature of the attribute, for example a numeric value or a code list value.

Multiplicity

Describes how many times this element is expected to be populated in the data. An attribute may be optional or mandatory within the product. These are denoted by:

• ‘1’ – there must be a value.

• ‘0..1’ – population is optional but a maximum of one attribute will be returned These values may be used in combination.

AddressBase Premium Islands feature types

• Street – (Type 11 Record)

• BLPU – (Type 21 Record)

• AddressBase supply set

• Feature with lifecycle

A way or thoroughfare providing a right of way on foot, by cycle or by motor vehicle, or access to more than one property. This record assigns a Unique Street Reference Number (USRN) to each street and holds the start and end coordinates of the street feature with information about surface type and classification.

Feature type attributes

The following page provides details about the attributes included with this feature, their data types in the different output formats, and other important metadata about them.

fid

A non-persistent integer which is autogenerated and is required within the OGC GPKG format.

• Attribute Name: Not provided (GML), Not provided (CSV), fid (GKPG)

• Data Type: Integer

• Multiplicity: [1]

Record identifier

Identifies this record as a Street Record (type 11).

• Attribute Name: Not provided (GML), RECORD_IDENTIFIER (CSV), Not provided (GKPG)

• Data Type: Integer (CSV)

• Size: 2

• Multiplicity: [1]

Change type

Type of record change – please see COU supply for more information.

• Attribute Name: Provided in FeatureWithLifeCycle (GML), CHANGE_TYPE (CSV), change_type (GKPG)

• Code List Name: ChangeTypeCode

• Size: 1

• Multiplicity: [1]

Pro order

The order in which the records were processed in to create the data supply.

• Attribute Name: Not provided (GML), PRO_ORDER (CSV), Not provided (GKPG)

• Data Type: Integer

• Size: 16

• Multiplicity: [1]

USRN

Unique Street Reference Number (USRN) - the unique key for the record and primary key for the Street table.

• Attribute Name: usrn (GML), USRN (CSV), usrn (GKPG)

• Data Type: Integer

• Size: 8

• Multiplicity: [1]

Record type

Description of the street record type, for example whether it is a named or numbered street.

• Attribute Name: recordType (GML), RECORD_TYPE (CSV), record_type (GKPG)

• Code List Name: StreetRecordTypeCode

• Size: 1

• Multiplicity: [1]

SWA org ref

The code which identifies the Street Naming and Numbering Authority or the Local Highway Authority.

• Attribute Name: swaOrgRefNaming (GML), SWA_ORG_REF_NAMING (CSV), swa_org_ref_naming (GKPG)

• Data Type: Integer

• Size: 4

• Multiplicity: [1]

State

A code identifying the current state of the Street, ‘Open’ for example.

• Attribute Name: state (GML), STATE (CSV), state (GKPG)

• Code List Name: StreetStateCode

• Size: 1

• Multiplicity: [0..1]

State date

Date at which the street achieved its current state as referenced in the ‘State’ column.

• Attribute Name: stateDate (GML), STATE_DATE (CSV), state_date (GKPG)

• Condition: If State Date is present, State must also be present.

• Data Type: Date

• Multiplicity: [0..1]

Street surface

A code to indicate the surface finish of the street.

• Attribute Name: streetSurface (GML), STREET_SURFACE (CSV), street_surface (GKPG)

• Code List Name: StreetSurfaceCode

• Size: 1

• Multiplicity: [0..1]

Street classification

A code for the primary street classification, for example denoting it to be ‘open to all vehicles’.

• Attribute Name: streetClassification (GML), STREET_CLASSIFICATION (CSV), street_classification (GKPG)

• Code List Name: StreetClassificationCode

• Size: 2

• Multiplicity: [0..1]

Version

Version number of the street record.

• Attribute Name: version (GML), VERSION (CSV), version (GKPG)

• Data Type: Integer

• Size: 3

• Multiplicity: [1]

Street start date

Date this record or version was inserted into the database.

• Attribute Name: Provided in FeatureWithLifeCycle (GML), STREET_START_DATE (CSV), street_start_date (GKPG)

• Data Type: Date

• Multiplicity: [1]

Street end date

Date on which the street was closed in the product database. This can occur due to the street being permanently closed in the real world.

• Attribute Name: Provided in FeatureWithLifeCycle (GML), STREET_END_DATE (CSV), street_end_date (GKPG)

• Condition: If State is equal to 4, Street End Date must be populated.

• Data Type: Date

• Multiplicity: [0..1]

Last update date

The date on which any attribute of the Record was last changed.

• Attribute Name: Provided in FeatureWithLifeCycle (GML), LAST_UPDATE_DATE (CSV), last_update_date (GKPG)

• Data Type: Date

• Multiplicity: [1]

Record entry date

The date that the record was entered into the Local Authority database.

• Attribute Name: Provided in FeatureWithLifeCycle (GML), RECORD_ENTRY_DATE (CSV), record_entry_date (GKPG)

• Data Type: Date

• Multiplicity: [1]

Street start

A value in metres defining the x and y location in accordance with the British National Grid for the start point of the street.

• Attribute Name: streetStart (GML) <<VOIDABLE>>, STREET_START_X, STREET_START_Y (CSV), street_start_x, street_start_y (GKPG)

• Condition: Must be populated if COUNTRY = ‘M’

• Data Type: GM_POINT (GML), Float (CSV), Double (GPKG)

• Size: STREET_START_X (precision, scale) – (8, 2), STREET_START_Y (precision, scale) – (9, 2)

• Multiplicity: [1] (GML), [0..1] (CSV), [0..1] (GPKG)

Street start lat long

A value defining the Latitude and Longitude start point of the street in accordance with the ETRS89 coordinate reference system.

• Attribute Name: streetStartLatLong (GML), STREET_START_LAT, STREET_START_LONG (CSV), street_start_lat, street_start_long (GKPG)

• Data Type: GM_POINT (GML), Float (CSV), Double (GPKG)

• Size: LATITUDE (precision, scale) – (9, 7), LONGITUDE (precision, scale) – (8, 7)

• Multiplicity: [1]

Street end

A value in metres defining the x and y location in accordance with the British National Grid for the end point of the street.

• Attribute Name: streetEnd (GML) <<VOIDABLE>>, STREET_END_X, STREET_END_Y (CSV), street_start_lat, street_end_x, street_end_y (GKPG)

• Condition: Must be populated if COUNTRY = ‘M’

• Data Type: GM_POINT (GML), Float (CSV), Double (GPKG)

• Size: STREET_END_X (precision, scale) – (8, 2), STREET_END_Y (precision, scale) – (9, 2)

• Multiplicity: [1] (GML), [0..1] (CSV), [0..1] (GPKG)

Street end lat long

A value defining the Latitude and Longitude end point of the street in accordance with the ETRS89 coordinate reference system.

• Attribute Name: streetEndLatLong (GML), STREET_END_LAT, STREET_END_LONG (CSV), street_end_lat, street_end_long (GKPG)

• Data Type: GM_POINT (GML), Float (CSV), Double (GPKG)

• Size: LATITUDE (precision, scale) – (9, 7), LONGITUDE (precision, scale) – (8, 7)

• Multiplicity: [1]

Street tolerance

The accuracy of data capture (in metres) to which the Street Start and End coordinates have been captured.

• Attribute Name: streetTolerance (GML), STREET_TOLERANCE (CSV), street_tolerance (GKPG)

• Data Type: Integer

• Size: 3

• Multiplicity: [1]

This feature is formally known as the GML feature collection and is used to define a collection of features.

Feature type attributes

The following page provides details about the attributes included with this feature, their data types in the different output formats, and other important metadata about them.

Query time

Time the data was extracted from the database.

• Attribute Name: queryTime (GML), Not provided (CSV), Not provided (GKPG)

• Data Type: DateTime

• Multiplicity: [1]

Query change since date

The date given as part of a change-only query.

• Attribute Name: queryChangeSinceDate (GML), Not provided (CSV), Not provided (GKPG)

• Data Type: Date

• Multiplicity: [0..1]

This feature holds the lifecycle information about the whole feature.

Feature type attributes

The following page provides details about the attributes included with this feature, their data types in the different output formats, and other important metadata about them.

Change time

Type of record change – please see COU supply for more information.

• Attribute Name: changeType (GML), Not provided (CSV), Not provided (GKPG)

• Code List Name: ChangeTypeCode

• Multiplicity: [1]

Start date

Date on which the record was first loaded into the database.

• Attribute Name: startDate (GML), Not provided (CSV), Not provided (GKPG)

• Data Type: Date

• Multiplicity: [1]

End date

The date on which the record ceased to exist in the product database.

• Attribute Name: endDate (GML), Not provided (CSV), Not provided (GKPG)

• Data Type: Date

• Multiplicity: [0..1]

Last update date

The date on which any attribute on this record was last changed in the product database.

• Attribute Name: endDate (GML), Not provided (CSV), Not provided (GKPG)

• Data Type: Date

• Multiplicity: [0..1]

Entry date

The date on which the record was entered into the Local Authority database.

• Attribute Name: entryDate (GML), Not provided (CSV), Not provided (GKPG)

• Data Type: Date

• Multiplicity: [1]

A descriptive identifier providing additional information about the street feature. This record holds information about locality, town name and street name.

Data type attributes

The following page provides details about the attributes included with this data type, their types in the different output formats, and other important metadata about them.

fid

A non-persistent integer which is autogenerated and is required within the OGC GPKG format.

• Attribute Name: Not provided (GML), Not provided (CSV), fid (GKPG)

• Data Type: Integer

• Multiplicity: [1]

Record identifier

Identifies this record as a Street Descriptor record (type 15).

• Attribute Name: Not provided (GML), RECORD_IDENTIFIER (CSV), Not provided (GKPG)

• Data Type: Integer

• Size: 2

• Multiplicity: [1]

Change type

Type of record change – please see COU supply for more information.

• Attribute Name: Not provided (GML), CHANGE_TYPE (CSV), change_type (GKPG)

• Code List Name: ChangeTypeCode

• Size: 1

• Multiplicity: [1]

Pro order

The order in which the records were processed in to create the data supply.

• Attribute Name: Not provided (GML), PRO_ORDER (CSV), Not provided (GKPG)

• Data Type: Integer

• Size: 16

• Multiplicity: [1]

USRN

Unique Street Reference Number (USRN): used as foreign key to reference the corresponding street record.

• Attribute Name: usrn (GML), USRN (CSV), usrn (GKPG)

• Data Type: Integer

• Size: 8

• Multiplicity: [1]

Street description

Name, description or Street number for this record.

• Attribute Name: streetDescription (GML), STREET_DESCRIPTION (CSV), street_description (GKPG)

• Data Type: LocalisedCharacterString (GML), char (CSV), String (GKPG)

• Size: 100

• Multiplicity: [1]

Locality

A locality defines an area or geographical identifier within a town, village or hamlet.

Locality represents the lower-level geographical area. The locality field should be used in conjunction with the town name and street description fields to uniquely identify geographic area where there may be more than one within an administrative area.

• Attribute Name: locality (GML), LOCALITY (CSV), locality (GKPG)

• Data Type: LocalisedCharacterString (GML), char (CSV), String (GKPG)

• Size: 35

• Multiplicity: [0..1]

Town name

The name of the town the address is within.

• Attribute Name: townName (GML), TOWN_NAME (CSV), town_name (GKPG)

• Condition: Town name must be present if the Street Record Type is 1 or 2 and may be entered for type 3, 4 and 9 Streets.

• Data Type: LocalisedCharacterString (GML), char (CSV), String (GKPG)

• Size: 30

• Multiplicity: [0..1]

Administrative area

Local Highway Authority name for the area this record exists within.

• Attribute Name: administrativeArea (GML), ADMINSTRATIVE_AREA (CSV), administrative_area (GKPG)

• Data Type: LocalisedCharacterString (GML), char (CSV), String (GKPG)

• Size: 30

• Multiplicity: [1]

Language

A code identifying the language in use for the record.

• Attribute Name: Not provided (GML), LANGUAGE (CSV), language (GKPG)

• Code List Name: LanguageCode

• Size: 3

• Multiplicity: [1]

Start date

Date this record was first created in the database.

• Attribute Name: Provided in EntityWithLifeCycle (GML), START_DATE (CSV), start_date (GKPG)

• Data Type: Date

• Multiplicity: [1]

End date

The date on which this record ceased to exist in the product database.

• Attribute Name: Provided in EntityWithLifeCycle (GML), END_DATE (CSV), end_date (GKPG)

• Data Type: Date

• Multiplicity: [0..1]

Last update date

The date on which any of the attributes on this record were last changed in the product database.

• Attribute Name: Provided in EntityWithLifeCycle (GML), LAST_UPDATE_DATE (CSV), last_update_date (GKPG)

• Data Type: Date

• Multiplicity: [1]

Entry date

The date on which the record was entered into the Local Authority database.

• Attribute Name: Provided in EntityWithLifeCycle (GML), ENTRY_DATE (CSV), entry_date (GKPG)

• Data Type: Date

• Multiplicity: [1]

AddressBase Premium Islands is supplied as non-geographic chunks only. This is a way of dividing up the data into chunks that are supplied in separate volumes, which have a fixed maximum number of records. The supply is not supplied with any reference to the geographic position of records.

Customers are able to take the AddressBase Premium Islands product as a full supply or a change only update (COU) supply for GML and CSV formats. The AddressBase Premium Islands GPKG is available as a full supply only.

Unzipped files

When you receive your data, the filename will be constructed as follows:

• productDescription_supply_ccyy-mm-dd_vvv.format

  • productDescription: AddressBasePremium_ISL

  • supply: FULL or COU

  • ccyy-mm-dd: the date the file was generated

  • vvv: volume number of the file

  • format: file format of the files received, for example csv, gmlL or gpkg

For example:

• AddressBasePremium_ISL_FULL_2015-10-28_001.gml (GML full supply)

• AddressBasePremium_ISL_COU_2015-10-28_001.csv (CSV COU supply)

• AddressbasePremium_ISL_FULL_2015-10-28_001.gpkg (GPKG full supply)

Zipped files

If the data has been provided in a ZIP file, the filename will be constructed as follows:

• productName_supply_ccyy-mm-dd_vvv_format.zip

For example:

• AddressBasePremium_ISL_FULL_2013-05-28_001_gml.zip (GML full supply zipped)

COU supply

AddressBase Premium Islands is available as a full or change-only update (COU) supply for CSV and GML formats. COU supplies are not available for GeoPackage format.

A COU supply of data contains records or files which have changed between product refresh cycles. The primary benefit in supplying data in this way is that data volumes are smaller, reducing the amount of data that requires processing when compared to a full supply.

COU data enables a user to identify three types of change:

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.

Archiving

When users are deleting, inserting or updating features, it is up to the user to consider their archiving requirements. If deleted records are important to your business requirements, you must take appropriate action to archive previous records.

This section describes the structured data types which make up the AddressBase Premium product, giving the following information about each attribute:

AddressBase Premium Islands 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

The AddressBase Premium Islands product contains Local Authority, Ordnance Survey and Royal Mail addresses. This includes provisional addresses (proposed planning developments) and historic information (demolished properties), where available.

Ordnance Survey addresses are added to the AddressBase Premium Islands product where necessary to ensure the schema meets the core AddressBase products.

Index

• Data formats

• Supply and update

• AddressBase Premium structure

• Feature types

• Structured data types

• Dataset metadata

• Code lists and enumerations

• Attribute names format comparison

• Example records

A structured entry which terminates the file. This includes information on the record counts, and next volume number.

Data type attributes

The following page provides details about the attributes included with this data type, their types in the different output formats, and other important metadata about them.

Record identifier

Identifies the record as a Trailer Record (type 99).

• Attribute Name: Not provided (GML), RECORD_IDENTIFIER (CSV), Not provided (GKPG)

• Data Type: Integer

• Size: 2

• Multiplicity: [1]

Next volume name

The sequential number of the next volume in the transfer set. For geographic supply this will always be zero (0). For non-geographic supply zero (0) will denote the last file in the transfer set.

• Attribute Name: Not provided (GML), NEXT_VOLUME_NAME (CSV), Not provided (GKPG)

• Data Type: Integer

• Size: 3

• Multiplicity: [1]

Record count

Count of the number of records in the volume (excluding the header record, metadata and trailer records).

• Attribute Name: Not provided (GML), RECORD_COUNT (CSV), Not provided (GKPG)

• Data Type: Integer

• Size: 16

• Multiplicity: [1]

Entry date

The date of data entry.

• Attribute Name: Not provided (GML), ENTRY_DATE (CSV), Not provided (GKPG)

• Data Type: Date

• Multiplicity: [1]

Time stamp

Time of creation in HH:MM:SS format.

• Attribute Name: Not provided (GML), TIME_STAMP (CSV), Not provided (GKPG)

• Data Type: Time

• Multiplicity: [1]

This feature holds the lifecycle information about the data type record.

Data type attributes

The following page provides details about the attributes included with this data type, their types in the different output formats, and other important metadata about them.

Start date

Date on which the record was first loaded into the database.

• Attribute Name: startDate (GML), Not provided (CSV), Not provided (GKPG)

• Data Type: Date

• Multiplicity: [1]

End date

The date on which the record ceased to exist.

• Attribute Name: endDate (GML), Not provided (CSV), Not provided (GKPG)

• Data Type: Date

• Multiplicity: [0..1]

Last update date

The date on which any attribute on this record was last changed.

• Attribute Name: lastUpdateDate (GML), Not provided (CSV), Not provided (GKPG)

• Data Type: Date

• Multiplicity: [0..1]

Entry date

The date on which the record was entered into the Local Authority database.

• Attribute Name: entryDate (GML), Not provided (CSV), Not provided (GKPG)

• Data Type: Date

• Multiplicity: [1]

The AddressBase Premium Islands product is distributed as comma-separated value (CSV), Geography Markup Language (GML) version 3.2.1 or GeoPackage (GPKG) formats. The CSV and GML formats can be supplied as a full supply or a change-only update (COU); the GPKG format is available as a full supply only.

CSV

The CSV supply of AddressBase Premium means:

• There will be one record per line in each file.

• Fields will be separated by commas.

• String fields will be delimited by double quotes.

• No comma will be placed at the end of each row in the file.

• Records will be terminated by Carriage Return / Line Feed.

• Double quotes inside strings will be escaped by doubling.

Where a field has no value in a record, two commas will be placed together in the record (one for the end of the previous field and one for the end of the null field). Where the null field is a text field double quotes will be included between the two commas, for example - “”.

AddressBase Premium CSV data will be transferred using Unicode encoded in UTF-8. Unicode includes all the characters in ISO-8859-14 (Welsh characters). Some accented characters are encoded differently.

The transfer will normally be in a single file, but the data can be split into multiple files using volume numbers. AddressBase Premium records are provided within continuous files cut at approximately 1 million lines as referred to above.

Street and Street Descriptor records are provided together and then a new file is started independent of count for the additional record types.

This means different record types, for example, BLPU and LPIs (see AddressBase Premium Island structure) can be found in the same CSV file.

The record types are provided in the following order:

• Street (Type 11)

• Street Descriptor (Type 15) – a new file is started after the last Street Descriptor record for your supply is reached

• BLPU (Type 21)

• LPI (Type 24)

• Delivery Point Address (Type 28)

• Organisation (Type 31)

• Classification (Type 32)

• Application Cross Reference (Type 23)

GML

The GML Encoding standard is an Extensible Markup Language (XML) grammar for expressing geographical features. XML schemas are used to define and validate the format and content of GML. The XML specifications that GML is based on are available from the World Wide Web Consortium (W3C) website: http://www.w3.org. More information can be found in the Open Geospatial Consortium (OGC) document, Geography Markup Language v3.2.1.

The GML 3.2.1 specification provides a set of schemas that define the GML feature constructs and geometric types. These are designed to be used as a basis for building application-specific schemas, which define the data content.

A GML document is described using an XML schema. The AddressBase Premium Islands schema document (addressbasepremium.xsd) defines the features in AddressBase Premium GML and is available on the Ordnance Survey website at: https://www.ordnancesurvey.co.uk/xml/products/AddressBasePremium.xml. It imports the GML 3.2.1 schemas which rely on XML, as defined by W3C at: http://www.w3.org/XML/1998/namespace.html.

The application schema uses the following XML namespaces:

Information about Unicode and UTF-8, the character encoding we have chosen, is available on the Unicode Consortium website.

Features

Each feature within the AddressBaseSupplySet:FeatureCollection is encapsulated in the following member element according to its feature type:

BLPU

• Feature Type: BasicLandPropertyUnit

• Member Element: <abpr:basicLandPropertyUnitMember>

The UPRN of the feature is provided in the XML attribute of the gml:id

<abpr: basicLandPropertyUnitMember> 
<abpr: BasicLandPropertyUnit gml:id=”uk.geoplace.uprn.1000011535314”> 
……………….. 
</abpr:BasicLandPropertyUnit> 
</abpr: basicLandPropertyUnitMember> 

Street

• Feature Type: Street

• Member Element: <abpr:streetMember>

The USRN of the feature is provided in the XML attribute of the gml:id

<abpr: streetMember> 
<abpr:Street gml:id=”uk.geoplace.usrn.14200295”> 
……………….. 
</abpr:Street> 
</abpr: streetMember>

See Example records > GML for specific GML examples.

Envelope

In the GML supply, you can determine the extent of your supply by the <gml: Envelope>. Because Latitude and Longitude are the mandatory coordinates in AddressBase Premium Islands the envelope uses these coordinates. For example:

<gml:boundedBy> 
<gml:Envelope srsName="urn:ogc:def:crs:EPSG::4258"> 
<gml:lowerCorner>48.40 -8.30</gml:lowerCorner> 
<gml:upperCorner>55.50 -1.80</gml:upperCorner> 
</gml:Envelope> 
</gml:boundedBy> 

GPKG

GPKG is an open, standards-based data format as defined by the Open Geospatial Consortium (OGC). It is designed to be a lightweight format that can contain large amounts of varied and complex data in a single, easy to distribute and ready to use file. Please be advised that older versions of GIS software may need updating before being able to display and interact with GPKG files.

GPKG offers the following benefits:

• The single file is easy to transfer and offers the end-user a rich experience.

• Attribute names are not limited in length, making it user friendly.

• The file size limit is very large at 140 TB1, so lots of data can be easily accommodated.

• It supports raster, vector and database formats, making it a highly versatile solution.

• It is an OGC Standard.

• In most cases, it is a plug-in-and-play format.

A structured entry that provides the code for the type of BLPU and the classification scheme from which the code is taken. This record holds the classification of a property and allows one to search upon the use of a feature.

Data type attributes

The following page provides details about the attributes included with this data type, their types in the different output formats, and other important metadata about them.

fid

A non-persistent integer which is autogenerated and is required within the OGC GPKG format.

• Attribute Name: Not provided (GML), Not provided (CSV), fid (GKPG)

• Data Type: Integer

• Multiplicity: [1]

Record identifier

Identifies this record as a Classification Record (type 32).

• Attribute Name: Not provided (GML), RECORD_IDENTIFIER (CSV), Not provided (GKPG)

• Data Type: Integer

• Size: 2

• Multiplicity: [1]

Change type

• Attribute Name: Not provided (GML), CHANGE_TYPE (CSV), change_type (GKPG)

• Size: 1

• Multiplicity: [1]

Pro order

The order in which the records were processed in to create the data supply.

• Attribute Name: Not provided (GML), PRO_ORDER (CSV), Not provided (GKPG)

• Data Type: Integer

• Size: 16

• Multiplicity: [1]

UPRN

Unique Property Reference Number (UPRN) - foreign key used to reference the LPI to the corresponding BLPU.

• Attribute Name: Not provided (GML), UPRN (CSV), uprn (GKPG)

• Data Type: Integer

• Size: 12

• Multiplicity: [1]

Class key

Unique key for the classification record and primary key for this table.

• Attribute Name: classKey (GML), CLASS_KEY (CSV), class_key (GKPG)

• Data Type: CharacterString (GML), char (CSV), String (GKPG)

• Size: 14

• Multiplicity: [1]

Classification codes

Classification of the address record, depicting its primary use.

• Attribute Name: classificationCode (GML), CLASSIFICATION_CODE (CSV), classification_code (GKPG)

• Data Type: CharacterString (GML), char (CSV), String (GKPG)

• Size: 6

• Multiplicity: [1]

Class scheme

The name of the classification scheme used for this record.

• Attribute Name: classScheme (GML), CLASS_SCHEME (CSV), class_scheme (GKPG)

• Data Type: CharacterString (GML), char (CSV), String (GKPG)

• Size: 60

• Multiplicity: [1]

Scheme version

The name of the classification scheme used for this record.

• Attribute Name: schemeVersion (GML), SCHEME_VERSION (CSV), scheme_version (GKPG)

• Data Type: CharacterString (GML), float (CSV), double (GKPG)

• Size: (precision, scale) – 2(1)

• Multiplicity: [1]

Start date

Date on which this classification record was first loaded into the database.

• Data Type: Date

• Multiplicity: [1]

End date

Date this classification record ceased to exist in the product database.

• Data Type: Date

• Multiplicity: [0..1]

Last update date

The date on which any attribute on this record was last changed.

• Data Type: Date

• Multiplicity: [1]

Entry date

The date on which the address record associated with this classification record was inserted into the Local Authority database.

• Data Type: Date

• Multiplicity: [1]

A structured entry providing metadata information such as the gazetteer owner, scope and character sets.

Data type attributes

The following page provides details about the attributes included with this data type, their types in the different output formats, and other important metadata about them.

Record identifier

Identifies the record as a Metadata Record (type 29).

• Attribute Name: Not provided (GML), RECORD_IDENTIFIER (CSV), Not provided (GKPG)

• Data Type: Integer

• Size: 2

• Multiplicity: [1]

Gaz name

Name of the Gazetteer, this will most likely reflect the product name, for example, AddressBase Premium.

• Attribute Name: Not provided (GML), GAZ_NAME (CSV), Not provided (GKPG)

• Data Type: char

• Size: 60

• Multiplicity: [1]

Gaz scope

Description of the content of the gazetteer.

• Attribute Name: Not provided (GML), GAZ_SCOPE (CSV), Not provided (GKPG)

• Data Type: char

• Size: 60

• Multiplicity: [1]

Ter of use

Geographic domain of the gazetteer, for example, England, Wales and Scotland.

• Attribute Name: Not provided (GML), TER_OF_USE (CSV), Not provided (GKPG)

• Data Type: char

• Size: 60

• Multiplicity: [1]

Linked data

List of other datasets used to contribute to the creation of the product.

• Attribute Name: Not provided (GML), LINKED_DATA (CSV), Not provided (GKPG)

• Data Type: char

• Size: 100

• Multiplicity: [1]

Gaz owner

The organisation with overall responsibility for the gazetteer.

• Attribute Name: Not provided (GML), GAZ_OWNER (CSV), Not provided (GKPG)

• Data Type: char

• Size: 15

• Multiplicity: [1]

Ngaz freq

Frequency with which the data is maintained and sent to the customer.

• Attribute Name: Not provided (GML), NGAZ_FREQ (CSV), Not provided (GKPG)

• Data Type: char

• Size: 1

• Multiplicity: [1]

Custodian name

Organisation or department responsible for the compilation and maintenance of the data, for example Geoplace.

• Attribute Name: Not provided (GML), CUSTODIAN_NAME (CSV), Not provided (GKPG)

• Data Type: char

• Size: 40

• Multiplicity: [1]

Local custodian code

Four-digit code identifying the gazetteer custodian.

• Attribute Name: Not provided (GML), LOCAL_CUSTODIAN_CODE (CSV), Not provided (GKPG)

• Data Type: Integer

• Size: 4

• Multiplicity: [1]

Co-ord system

Coordinate Reference System used in the gazetteer to describe the position, for example British National Grid.

• Attribute Name: Not provided (GML), CO_ORD_SYSTEM (CSV), Not provided (GKPG)

• Data Type: char

• Size: 40

• Multiplicity: [1]

Co-ord unit

Unit of measurement of coordinates.

• Attribute Name: Not provided (GML), CO_ORD_SYSTEM (CSV), Not provided (GKPG)

• Data Type: char

• Size: 10

• Multiplicity: [1]

Meta date

Date metadata was last updated.

• Attribute Name: Not provided (GML), META_DATE (CSV), Not provided (GKPG)

• Data Type: Date

• Multiplicity: [1]

Class scheme

Classification scheme (s) used in the Gazetteer.

• Attribute Name: Not provided (GML), CLASS_SCHEME (CSV), Not provided (GKPG)

• Data Type: char

• Size: 60

• Multiplicity: [1]

Gaz date

Date at which the gazetteer can be considered to be current.

• Attribute Name: Not provided (GML), GAZ_DATE (CSV), Not provided (GKPG)

• Data Type: Date

• Multiplicity: [1]

Language

Language used for the descriptors within the gazetteer, for example ‘ENG’.

• Attribute Name: Not provided (GML), CLASS_SCHEME (CSV), Not provided (GKPG)

• Size: 3

• Multiplicity: [1]

Character set

The character set used in this gazetteer.

• Attribute Name: Not provided (GML), CHARACTER_SET (CSV), Not provided (GKPG)

• Data Type: char

• Size: 30

• Multiplicity: [1]

A BLPU is defined as a real-world object that is an ‘area of land, property or structure of fixed location having uniform occupation, ownership or function’. It is a real-world object that is of interest and within scope of the CLASS_SCHEME.

Feature type attributes

The following page provides details about the attributes included with this feature, their data types in the different output formats, and other important metadata about them.

fid

A non-persistent integer which is autogenerated and is required within the OGC GPKG format.

• Attribute Name: Not provided (GML), Not provided (CSV), fid (GKPG)

• Data Type: Integer

• Multiplicity: [1]

Record identifier

Identifies this record as a BLPU Record (type 21).

• Attribute Name: Not provided (GML), RECORD_IDENTIFIER (CSV), Not provided (GKPG)

• Data Type: Integer (CSV)

• Size: 2

• Multiplicity: [1]

Change type

• Size: 1

• Multiplicity: [1]

Pro order

The order in which the records were processed in to create the data supply.

• Attribute Name: Not provided (GML), PRO_ORDER (CSV), Not provided (GKPG)

• Data Type: Integer

• Size: 16

• Multiplicity: [1]

UPRN

The order in which the records were processed in to create the data supply.

• Attribute Name: uprn (GML), UPRN (CSV), uprn (GKPG)

• Data Type: Integer

• Size: 12

• Multiplicity: [1]

Logical status

Logical status of this address record as given by the local custodian. This attribute shows whether the address is currently live, provisional or historic.

• Attribute Name: logicalStatus (GML), LOGICAL_STATUS (CSV), logical_status (GKPG)

• Size: 1

• Multiplicity: [1]

BLPU state

A code identifying the current state of the BLPU.

• Attribute Name: blpuState (GML), BLPU_STATE (CSV), blpu_state (GKPG)

• Size: 1

• Multiplicity: [0..1]

BLPU state date

Date at which the BLPU achieved its current state as defined in the BLPU State field.

• Attribute Name: blpuStateDate (GML), BLPU_STATE_DATE (CSV), blpu_state_date (GKPG)

• Condition: BLPU State Date must be present if BLPU State is present.

• Data Type: Date

• Size: 1

• Multiplicity: [0..1]

Parent UPRN

UPRN of the parent Record if a parent child relationship exists.

• Attribute Name: parentUPRN (GML), PARENT_UPRN (CSV), parent_uprn (GKPG)

• Data Type: Integer

• Size: 12

• Multiplicity: [0..1]

Position

A value in metres defining the x and y location in accordance with the British National Grid.

• Attribute Name: position (GML) <<VOIDABLE>>, X_COORDINATE, Y_COORDINATE (CSV), x_coordinate, y_coordinate (GKPG)

• Condition: Must be populated if COUNTRY = ‘M’

• Data Type: GM_POINT (GML), Float (CSV), Double (GPKG)

• Size: X_COORDINATE (precision, scale) – (8, 2), Y_COORDINATE (precision, scale) – (9, 2)

• Multiplicity: [1] (GML), [0..1] (CSV), [0..1] (GPKG)

Position lat long

A value defining the Latitude and Longitude location in accordance with the ETRS89 coordinate reference system.

• Attribute Name: positionLatLong (GML), LATITUDE, LONGITUDE (CSV), latitude, longitude (GKPG)

• Data Type: GM_POINT (GML), Float (CSV), Double (GPKG)

• Size: LATITUDE (precision, scale) – (9, 7), LONGITUDE (precision, scale) – (8, 7)

• Multiplicity: [1]

RPC

Representative Point Code (RPC). This code is used to reflect the positional accuracy of the address location.

• Attribute Name: rpc (GML), RPC (CSV), rpc (GKPG)

• Size: 1

• Multiplicity: [1]

Local custodian code

Unique identifier of the Local Authority Custodian responsible for the maintenance of this record.

• Attribute Name: localCustodianCode (GML), LOCAL_CUSTODIAN_C ODE (CSV), local_custodian_code (GKPG)

• Data Type: Integer

• Size: 4

• Multiplicity: [1]

Country

The country in which an address record can be found within, determined by the data supply.

• Attribute Name: country (GML), COUNTRY (CSV), country (GKPG)

• Size: 1

• Multiplicity: [1]

Start date

The date on which the address record was inserted into the database.

• Data Type: Date

• Multiplicity: [1]

End date

The date on which the address record was closed in the database.

• Data Type: Date

• Multiplicity: [0..1]

Last update date

The date on which any of the attributes on this record were last changed.

• Data Type: Date

• Multiplicity: [1]

Entry date

The date on which this record was inserted into the Local Authority database.

• Data Type: Date

• Multiplicity: [1]

AddressBase postal

Identifies addresses which are believed to be capable of receiving mail as defined specifically for the AddressBase products and details their relationship with other AddressBase Postal records.

• Attribute Name: addressbasePostal (GML), ADDRESSBASE_POSTAL (CSV), addressbase_postal (GKPG)

• Size: 1

• Multiplicity: [1]

Postcode locator

This field contains the Royal Mail Postcode Address File (PAF) postcode where the local authority address has been matched to PAF, that is, the POSTCODE field.

Where a match has not been made, the postcode information is sourced from the local authority in collaboration with Royal Mail. Where the local authority does not hold a current valid postcode Code-Point is used in the areas where this is possible, if not, spatial methods are used to allocate a Postcode value.

• Attribute Name: postcodeLocator (GML), POSTCODE_LOCATOR (CSV), postcode_locator (GKPG)

• Data Type: CharacterString (GML), char (CSV), String (GPKG)

• Size: 8

• Multiplicity: [1]

• Source: Royal Mail, Contributing Local Authority or Ordnance Survey

Postcode locator

This is a count of all of the child UPRNs for this record where a parent-child relationship exists.

• Attribute Name: multiOccCount (GML), MULTI_OCC_COUNT (CSV), multi_occ_count (GKPG)

• Data Type: Integer

• Size: 4

• Multiplicity: [1]

Multi occ count

This is a count of all of the child UPRNs for this record where a parent-child relationship exists.

• Attribute Name: multiOccCount (GML), MULTI_OCC_COUNT (CSV), multi_occ_count (GKPG)

• Data Type: Integer

• Size: 4

• Multiplicity: [1]

A structured entry that provides key information about the source, time and supply mechanism of the AddressBase Premium file.

Data type attributes

The following page provides details about the attributes included with this data type, their types in the different output formats, and other important metadata about them.

Record identifier

Identifies the record as a Header Record (type 10).

• Attribute Name: Not provided (GML), RECORD_IDENTIFIER (CSV), Not provided (GKPG)

• Data Type: Integer

• Size: 2

• Multiplicity: [1]

Custodian name

Name of the data provider organisation.

• Attribute Name: Not provided (GML), CUSTODIAN_NAME (CSV), Not provided (GKPG)

• Data Type: char

• Size: 40

• Multiplicity: [1]

Local custodian code

Unique identifier for the data provider code.

• Attribute Name: Not provided (GML), LOCAL_CUSTODIAN_CODE (CSV), Not provided (GKPG)

• Data Type: Integer

• Size: 4

• Multiplicity: [1]

Process date

The date on which the data supply was generated.

• Attribute Name: Not provided (GML), PROCESS_DATE (CSV), Not provided (GKPG)

• Data Type: Date

• Multiplicity: [1]

Volume number

The sequential number of the volume in the transfer set.

• Attribute Name: Not provided (GML), VOLUME_NUMBER (CSV), Not provided (GKPG)

• Data Type: Integer

• Size: 3

• Multiplicity: [1]

Entry date

Date of data entry for this volume.

• Attribute Name: Not provided (GML), ENTRY_DATE (CSV), Not provided (GKPG)

• Data Type: Date

• Multiplicity: [1]

Time stamp

Time of file creation in HH:MM:SS.

• Attribute Name: Not provided (GML), TIME_STAMP (CSV), Not provided (GKPG)

• Data Type: Time

• Multiplicity: [1]

Version

Version number of the product schema, for example, 1.0, 2.0.

• Attribute Name: Not provided (GML), VERSION (CSV), Not provided (GKPG)

• Data Type: char

• Size: 7

• Multiplicity: [1]

File type

States whether the data supply is a full supply or change only supply.

• Attribute Name: Not provided (GML), FILE_TYPE (CSV), Not provided (GKPG)

• Size: 1

• Multiplicity: [1]

A structured entry identifying the name of the current non-domestic occupier of the BLPU. This record holds information about the organisation of the record.

Data type attributes

The following page provides details about the attributes included with this data type, their types in the different output formats, and other important metadata about them.

fid

A non-persistent integer which is autogenerated and is required within the OGC GPKG format.

• Attribute Name: Not provided (GML), Not provided (CSV), fid (GKPG)

• Data Type: Integer

• Multiplicity: [1]

Record identifier

Identifies this as an Organisation Record (type 31).

• Attribute Name: Not provided (GML), RECORD_IDENTIFIER (CSV), Not provided (GKPG)

• Data Type: Integer

• Size: 2

• Multiplicity: [1]

Change type

• Attribute Name: Not provided (GML), CHANGE_TYPE (CSV), change_type (GKPG)

• Size: 1

• Multiplicity: [1]

Pro order

The order in which the records were processed in to create the data supply.

• Attribute Name: Not provided (GML), PRO_ORDER (CSV), Not provided (GKPG)

• Data Type: Integer

• Size: 16

• Multiplicity: [1]

UPRN

Unique Property Reference Number (UPRN) - foreign key used to reference the LPI to the corresponding BLPU.

• Attribute Name: Not provided (GML), UPRN (CSV), uprn (GKPG)

• Data Type: Integer

• Size: 12

• Multiplicity: [1]

Org key

Unique key for the organisation record and primary key for this table.

• Attribute Name: orgKey (GML), ORG_KEY (CSV), org_key (GKPG)

• Data Type: CharacterString (GML), CSV – char (CSV),

  String (GKPG)

• Size: 14

• Multiplicity: [1]

Organisation

Name of the organisation currently occupying the address record as provided by the local authority custodian.

• Attribute Name: organisation (GML), ORGANISATION (CSV), organisation (GKPG)

• Data Type: CharacterString (GML), char (CSV), String (GKPG)

• Size: 100

• Multiplicity: [1]

Legal name

Registered legal name of the organisation.

• Attribute Name: legalName (GML), LEGAL_NAME (CSV), legal_name (GKPG)

• Data Type: CharacterString (GML), char (CSV), String (GKPG)

• Size: 60

• Multiplicity: [0..1]

Start date

Date on which the record was first loaded into the database.

• Data Type: Date

• Multiplicity: [1]

End date

The date on which the record ceased to exist.

• Data Type: Date

• Multiplicity: [0..1]

Last update date

The date on which any attribute on this record was last changed.

• Data Type: Date

• Multiplicity: [1]

Entry date

The date on which the UPRN attached to this record was entered into the Local Authority database.

• Data Type: Date

• Multiplicity: [1]

This release note provides information about the June 2024 release of the AddressBase Islands products. These products were released to customers on 27th June 2024.

Record Counts

Changed Records

If you receive a Change-Only Update (COU) supply for your AddressBase Islands product, you will receive Insert, Update and Delete records within the supplied file. The following tables detail the count of these records.

AddressBase Plus Islands

AddressBase Premium Islands

It is important that COUs are processed with Deletes first, then Inserts and Updates. This is to ensure that updates are applied in the correct order. Guidance on this can be found in the Getting Started Guide – AddressBase, AddressBase Plus and AddressBase Plus Islands in the AddressBase general documentation.

Source Data Currency

The following information relates to the currency of the source data used in the creation of Epoch 111:

Data Issues

AddressBase Plus Islands Issues

There are no reported issues in this release of AddressBase Plus Islands.

AddressBase Premium Islands issues

Affected output formats: CSV and GML

• Street incorrect coordinates – There are two Streets which have incorrect start or end coordinates of 000000. The unique identifiers can be provided upon request through your OS Relationship Manager.

Next Release

The next release of AddressBase Islands products, Epoch 112, is scheduled for 15th August 2024.

The AddressBase Premium Islands product is constructed as per the following UML diagrams.

Model overview for CSV and GKPG

This diagram shows the relationships between each of the record types and their foreign keys.

A UML model of AddressBase Premium Islands in CSV and GKPG formats can be seen in the diagram below. In the UML diagram, feature types from the Ordnance Survey product specification are orange and data types are purple.

Model overview for GML

The diagram below shows a high-level data model representing the GML AddressBase Premium Islands data model. This diagram shows the relationships between each of the record types and their foreign keys.

The diagram below is a UML model of AddressBase Premium Islands in GML format; feature types from the Ordnance Survey product specification are orange and data types are purple.

A UML model of AddressBase Premium Islands in GML format can be seen in Figure 4 on the following page. In the UML diagram, feature types from the Ordnance Survey product specification are orange and data types are purple.

Table Descriptions

Street – record identifier 11

• Definition: A way or thoroughfare providing a right of way on foot, by cycle or by motor vehicle, or access to more than one property.

• Description: This record assigns a Unique Street Reference Number (USRN) to each street and holds the start and end coordinates of the street feature with information about surface type and classification.

Street Descriptor – record identifier 15

• Definition: A descriptive identifier providing additional information about the street feature.

• Description: This record holds information about locality, town name and street name.

Basic Land and Property Unit (BLPU) – record identifier 21

• Definition: A BLPU is defined as a real-world object that is an ‘area of land, property or structure of fixed location having uniform occupation, ownership or function’.

• Description: A real-world object that is of interest and within scope of the CLASS_SCHEME.

Application Cross Reference – record identifier 23

• Definition: Application cross reference links to third party identifiers.

• Description: AddressBase Premium Islands application cross references contain a lookup between the AddressBase Premium UPRN and the unique identifiers of other relevant datasets.

Land and Property Identifier (LPI) – record identifier 24

• Definition: An LPI is a structured entry that identifies a BLPU.

• Description: A simple identifier or description for the object. The richness of the data structure within AddressBase Premium Islands provides the facility to describe a BLPU by more than one LPI.

Delivery Point Address – record identifier 28

• Definition: A Delivery Point Address is defined as a property that receives deliveries from Royal Mail.

• Description: The structure of this address is taken from Royal Mail Postcode Address File (PAF) and other supplementary data files.

Successor Record – record identifier 30

• Definition: This record holds references to a UPRN and to any replacement UPRN, for example, if a building is split into two sub-buildings; the sub-building UPRNs will be referenced in the successor record.

• Description: This record holds information about a UPRN and the UPRNs of the records that succeed that record.

Organisation – record identifier 31

• Definition: A structured entry identifying the name of the current non-domestic occupier of the BLPU.

• Description: This record holds information about the organisation of the record.

Classification – record identifier 32

• Definition: A structured entry that provides the code for the type of BLPU and the classification scheme from which the code is taken.

• Description: This record holds the classification of a property and allows one to search upon the use of a feature.

Table descriptions - CSV only

The following are contained within CSV only:

Header – record identifier 10

• Definition: A structured entry that provides key information about the source, time and supply mechanism of the AddressBase Premium file.

Metadata – record identifier 29

• Definition: A structured entry providing metadata information such as the gazetteer owner, scope and character sets.

Trailer – record identifier 99

• Definition: A structured entry which terminates the file. This includes information on the record counts, and next volume number.

Table descriptions - GML only

The following are contained within GML only:

EntityWithLifeCycle

• Definition: This feature holds the lifecycle information about the data type record.

FeatureWithLifeCycle

• Definition: This feature holds the lifecycle information about the whole feature.

AddressBaseSupplySet

• Definition: This feature is formally known as the GML feature collection and is used to define a collection of features.

The pages in this section define dataset metadata for the CSV format of AddressBase Premium Islands product:

AddressBase Premium Islands dataset metadata

• ​

• ​

• ​

A code list or enumeration is a controlled set of values which can be used to populate a specific column.

The diagram below shows the code list and enumeration UML model associated with AddressBase Premium Islands with their appropriate descriptions.

AddressBase Premium code list and enumerations

An LPI is a structured entry that identifies a BLPU. It is a simple identifier or description for the object. The richness of the data structure within AddressBase Premium provides the facility to describe a by more than one LPI.

Data type attributes

The following page provides details about the attributes included with this data type, their types in the different output formats, and other important metadata about them.

fid

A non-persistent integer which is autogenerated and is required within the OGC GPKG format.

• Attribute Name: Not provided (GML), Not provided (CSV), fid (GKPG)

• Data Type: Integer

• Multiplicity: [1]

Record identifier

Identifies this Record as an LPI Record (type 24).

• Attribute Name: Not provided (GML), RECORD_IDENTIFIER (CSV), Not provided (GKPG)

• Data Type: Integer

• Size: 2

• Multiplicity: [1]

Change type

• Attribute Name: Not provided (GML), CHANGE_TYPE (CSV), change_type (GKPG)

• Size: 1

• Multiplicity: [1]

Pro order

The order in which the records were processed in to create the data supply.

• Attribute Name: Not provided (GML), PRO_ORDER (CSV), Not provided (GKPG)

• Data Type: Integer

• Size: 16

• Multiplicity: [1]

UPRN

Unique Property Reference Number (UPRN) - foreign key used to reference the LPI to the corresponding BLPU.

• Attribute Name: Not provided (GML), UPRN (CSV), uprn (GKPG)

• Data Type: Integer

• Size: 12

• Multiplicity: [1]

LPI key

Unique key for the LPI and primary key for this table.

• Attribute Name: lpiKey (GML), LPI_KEY (CSV), lpi_key (GKPG)

• Data Type: CharacterString (GML), char (CSV), String (GKPG)

• Size: 14

• Multiplicity: [1]

Language

A code that identifies the language used for the LPI record.

• Attribute Name: Not provided (GML), LANGUAGE (CSV), language (GKPG)

• Size: 3

• Multiplicity: [1]

Logical status

Logical status of this record.

• Attribute Name: logicalStatus (GML), LOGICAL_STATUS (CSV), logical_status (GKPG)

• Size: 1

• Multiplicity: [1]

Start date

Date that this LPI record was first loaded into the database.

• Data Type: Date

• Multiplicity: [1]

End date

The date this record ceased to exist in the database.

• Data Type: Date

• Multiplicity: [0..1]

Last update date

The last date an attribute on this record was last changed in the product database.

• Data Type: Date

• Multiplicity: [1]

Entry date

The date on which the record was inserted into the Local Authority database.

• Data Type: Date

• Multiplicity: [1]

SAO start number

The number of the secondary addressable object (SAO) or the start of the number range.

• Attribute Name: saoStartNumber (GML), SAO_START_NUMBER (CSV), sao_start_number (GKPG)

• Condition: If a SAO Start Number is present a PAO Start Number or PAO text must also be present.

• Data Type: Integer

• Size: 4

• Multiplicity: [0..1]

SAO start suffix

The suffix to the SAO_START_NUMBER, for example ‘A’ or ‘B’.

• Attribute Name: saoStartSuffix (GML), SAO_START_SUFFIX (CSV), sao_start_suffix (GKPG)

• Condition: If a SAO Start Suffix is present a SAO Start Number must also be present.

• Data Type: CharacterString (GML), char (CSV), String (GKPG)

• Size: 2

• Multiplicity: [0..1]

SAO end number

The end of the number range for the SAO, where the SAO_START_NUMBER contains the first number in the range.

• Attribute Name: saoEndNumber (GML), SAO_END_NUMBER (CSV), sao_end_number (GKPG)

• Condition: If SAO End Number is present, a SAO Start Number must also be present.

• Data Type: Integer

• Size: 4

• Multiplicity: [0..1]

SAO end suffix

The suffix to the SAO_END_NUMBER, for example, ‘A’ or ‘B’.

• Attribute Name: saoEndSuffix (GML), SAO_END_SUFFIX (CSV), sao_end_suffix (GKPG)

• Condition: If a SAO End Suffix is present, a SAO End Number must also be present.

• Data Type: CharacterString (GML), char (CSV), String (GKPG)

• Size: 2

• Multiplicity: [0..1]

SAO text

Describes the SAO, such as ‘Maisonette’ or ‘Flat 1’.

• Attribute Name: saoText (GML), SAO_TEXT (CSV), sao_text (GKPG)

• Condition: If SAO Text is present, a PAO Start Number or PAO Text must also be present.

• Data Type: LocalisedCharacterString (GML), char (CSV), String (GKPG)

• Size: 90

• Multiplicity: [0..1]

PAO start number

The number of the primary addressable object (PAO) or the start of the number range.

• Attribute Name: paoStartNumber (GML), PAO_START_NUMBER (CSV), pao_start_number (GKPG)

• Condition: PAO Start Number must be present if PAO Text is not present.

• Data Type: Integer

• Size: 4

• Multiplicity: [0..1]

PAO start suffix

The suffix to the PAO_START_NUMBER, for example, ‘A’ or ‘B’.

• Attribute Name: paoStartSuffix (GML), PAO_START_SUFFIX (CSV), pao_start_suffix (GKPG)

• Condition: If a PAO Start Suffix is present, a PAO Start Number must also be present.

• Data Type: CharacterString (GML), char (CSV), String (GKPG)

• Size: 2

• Multiplicity: [0..1]

PAO end number

The end of the number range for the PAO where the PAO_START_NUMBER contains the first number in the range.

• Attribute Name: paoEndNumber (GML), PAO_END_NUMBER (CSV), pao_end_number (GKPG)

• Condition: If a PAO End Number is present, a PAO Start Number must also be present.

• Data Type: Integer

• Size: 4

• Multiplicity: [0..1]

PAO end suffix

The suffix to the PAO_END_NUMBER, for example, ‘A’ or ‘B’.

• Attribute Name: paoEndSuffix (GML), PAO_END_SUFFIX (CSV), pao_end_suffix (GKPG)

• Condition: If a PAO End Suffix is present, a PAO End Number must also be present.

• Data Type: CharacterString (GML), char (CSV), String (GKPG)

• Size: 2

• Multiplicity: [0..1]

PAO text

Name describing the PAO, this is normally a building name such as ‘Harbour View’.

• Attribute Name: paoText (GML), PAO_TEXT (CSV), pao_text (GKPG)

• Condition: PAO Text must be present if PAO Start Number is not present.

• Data Type: LocalisedCharacterString (GML), char (CSV), String (GKPG)

• Size: 90

• Multiplicity: [0..1]

USRN

Unique Street Reference Number (USRN) - foreign key linking the Street record to the LPI record.

• Attribute Name: usrn (GML), USRN (CSV), usrn (GKPG)

• Data Type: Integer

• Size: 8

• Multiplicity: [1]

USRN match indicator

This field indicates how the item was matched to a Street. 1 is matched manually to the most accessible USRN and 2 is matched spatially to the nearest USRN, which may not be the nearest accessible street.

• Attribute Name: usrnMatchIndicator (GML), USRN_MATCH_INDICATOR (CSV), usrn_match_indicator (GKPG)

• Size: 1

• Multiplicity: [1]

Area name

Third level of geographic area name, for example, to record island names (Guernsey) or contain the TOWNLAND value for Northern Ireland records.

• Attribute Name: areaName (GML), AREA_NAME (CSV), area_name (GKPG)

• Data Type: CharacterString (GML), char (CSV), String (GKPG)

• Size: 40

• Multiplicity: [0..1]

Level

Detail on the vertical position of the property if known and provided by the Local Authority Custodian.

• Attribute Name: level (GML), LEVEL (CSV), level (GKPG)

• Data Type: CharacterString (GML), char (CSV), String (GKPG)

• Size: 30

• Multiplicity: [0..1]

Official flag

Status of the Address.

• Attribute Name: officialFlag (GML), OFFICIAL_FLAG (CSV), official_flag (GKPG)

• Size: 1

• Multiplicity: [0..1]

he naming of attributes between CSV, GML and GPKG will be different due to the requirements of the file formats. The following tables map the CSV attribute name to the GML and GPKG attribute names.

Basic Land and Property Unit (BLPU)

Classification

Delivery Point Address

Land Property Identifier (LPI)

Organisation

Application Cross Reference

Street

Street Description

Successor

Entity with Life Cycle

Feature with Life Cycle

The following sections provides example records for both the CSV and GML supplies.

Header example

Street example

Street Descriptor example

Basic Land and Property Unit (BLPU) example

Application Cross Reference example

Land Property Identifier (LPI) example

Delivery Point Address example

Metadata example

Successor example

Organisation example

31,"I",13581,185433088,"8132O000002222","EXAMPLE ORGANISATION NAME","",2015-12-20,,2015-0112,2015-12-19

Classification example

32,"I",181860,185433088,"8132C000076448","R","AddressBase Premium Classification Scheme”,1.0,2015- 1221,,2015-12-21,2015-12-01

Trailer example