Related components provide supplementary non-geospatial information or context about addresses. They can be linked to an address record in a feature type using the Unique Property Reference Number (UPRN) as the foreign key.
There are three related components in the OS NGD:
Alternate Address: These provide alternative address labels where they exist for the ‘current’ address represented on a given feature type.
Other Classification: These provide additional Valuation Office Agency (VOA) classification information.
Related Entity: These contain cross-reference relationship information between addresses and features in other OS NGD themes (such as buildings, sites, roads and boundaries) or third-party data sets.
The OS NGD Address Theme data structure diagram below is applicable to the latest data schema versions of all address feature types (i.e. data schema version 3.0 of Built Address, Historic Address, Non-Addressable Object and Pre-Build Address, and data schema version 1.0 of Royal Mail Address and Street Address):
Until September 2025, Postal Address Related Component was the fourth related component in the OS NGD. It has been discontinued in the latest data schema version 3.0 of the Built Address, Historic Address, Non-Addressable Object and Pre-Build Address Feature Types in the GB Address and Islands Address Collections, which released in September 2025.
The Postal Address Related Component contained delivery point data from the Royal Mail Postcode Address File (PAF). This information is now available in the new Royal Mail Address Feature Type (which launched in September 2025), which can be found in the GB Address and Islands Address Collections.
The Postal Address Related Component is still provided against the older (maintenance) data schema versions 1.0 and 2.0 of the Built Address, Historic Address, Non-Addressable Object and Pre-Build Address Feature Types in the GB Address and Islands Address Collections. These data schema versions are available for customers to use, but they are now older and in maintenance mode. (Data schema version 3.0 is the latest and recommended data schema version to use for these feature types.)
Related components will always be provided if you have chosen to receive any of the four following feature types from the OS NGD Address Theme: Built Address, Historic Address, Non-Addressable Object or Pre-Build Address. The primary identifier for these four feature types is the URPN (Unique Property Reference Number).
Related components will not be provided for the Royal Mail Address or Street Address Feature Types as their primary identifiers are Royal Mail's Unique Delivery Point Reference Number (UDPRN) and Unique Street Reference Number (USRN), respectively, not UPRN.
The related components do not contain geometry and therefore need to be joined to the relevant feature type table using the UPRN. When data is supplied, you will receive related component data split out by feature type.
For example, customers taking data schema version 3.0 of the Pre-Build Address Feature Type in GeoPackage format will receive:
Feature type: Pre-Build Address
Related component: Pre-Build Alternate Address
Related component: Pre-Build Related Entity
Related component: Pre-Build Other Classification
The Related Entity Related Component provides cross-reference information to key identifiers from other datasets, allowing for the UPRN (Unique Property Reference Number) to be linked to them.
The following table provides details about this related component’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.
3.0
30 September 2025
Ongoing
Major version increment to align with concurrent major version increments made to four feature types in the GB Address and Islands Address Collections: Built Address, Historic Address, Non-Addressable Object, and Pre-Build Address. (Related components follow the versioning of the addressing feature types they are associated with.)
Modified the associated code list (Data Entity Catalogue Code List) for the Cross Reference Feature attribute.
2.0
28 March 2023
Ongoing
Major version increment to align with concurrent major version increments made to four feature types in the GB Address and Islands Address Collections: Built Address, Historic Address, Non-Addressable Object, and Pre-Build Address. (Related components follow the versioning of the addressing feature types they are associated with.) New attribution added to related component for Effective Start Date and Effective End Date.
1.0
02 November 2022
Ongoing
Initial launch of the Related Entity Related Component.
Please see Data schema versioning for in-depth information about data schema versioning in the OS NGD.
Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).
The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this related component's data schema versions are indicated in the Data schema version table above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.
More information about temporal filtering is available from the Getting started with temporal filtering guide.
The following sub-sections provide details about the attributes included with this related component, their data types in the different output formats, and other important metadata about them.
Primary key providing a unique row identifier assigned to enable indexing for efficient querying.
Data Types: String (GPKG), String (CSV)
Nullable: false
Max Length: 36
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
Unique Property Reference Number (UPRN) assigned by a local custodian or Ordnance Survey as a persistent identifier.
Data Types: Integer (GPKG), Integer (CSV)
Nullable: false
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
Date of the feature version to which this related component applies.
Data Types: Date (GPKG), Date (CSV)
Nullable: false
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
Description of the related dataset that the cross reference refers to, for example, VOA Council Tax.
Data Types: String (GPKG), String (CSV)
Nullable: false
Code List Name: dataentitycatalogue
Code List Version: 2.0
Max Length: 40
OS Select+Build Filterable: No
Data Schema Version: 3.0
Data Types: String (GPKG), String (CSV)
Nullable: false
Code List Name: dataentitycatalogue
Code List Version: 1.0
Max Length: 40
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
Identifier of the related data entity or feature type instance that is the target of the reference or link.
Data Types: String (GPKG), String (CSV)
Nullable: false
Max Length: 36
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
Type of relationship which has been formed between the source and target features, for example, 'Within' or 'Same As'.
Data Types: String (GPKG), String (CSV)
Nullable: true
Code List Name: relationshiptypevalue
Max Length: 30
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
Name of the originating data provider that defined the reference or link.
Data Types: String (GPKG), String (CSV)
Nullable: false
Max Length: 110
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
The date on which any attribute of the record was last changed.
Data Types: Date (GPKG), Date (CSV)
Nullable: false
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
The date on which this relationship was first added into the database.
Data Types: Date (GPKG), Date (CSV)
Nullable: true
OS Select+Build Filterable: No
Data Schema Version: 2.0, 3.0
The date on which the relationship ceased to exist.
Data Types: Date (GPKG), Date (CSV)
Nullable: true
OS Select+Build Filterable: No
Data Schema Version: 2.0, 3.0
The Other Classification Related Component provides additional classification data beyond that held by Local Authorities for an address record. This data type contains VOA Council Tax and Non-Domestic Rate classification information in the form of Special Category Codes (SCAT) and Primary Descript\ion codes where VOA information has been matched to a Local Authority address. Note that VOA classifications are only available for England and Wales.
The following table provides details about this related component’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.
3.0
30 September 2025
Ongoing
Major version increment to align with concurrent major version increments made to four feature types in the GB Address and Islands Address Collections: Built Address, Historic Address, Non-Addressable Object, and Pre-Build Address. (Related components follow the versioning of the addressing feature types they are associated with.) Data type updated for Scheme Version attribute from string to number.
2.0
28 March 2023
Ongoing
Major version increment to align with concurrent major version increments made to four feature types in the GB Address and Islands Address Collections: Built Address, Historic Address, Non-Addressable Object, and Pre-Build Address. (Related components follow the versioning of the addressing feature types they are associated with.)
1.0
02 November 2022
Ongoing
Initial launch of the Other Address Related Component.
Please see Data schema versioning for in-depth information about data schema versioning in the OS NGD.
Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).
The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this related component's data schema versions are indicated in the Data schema version table above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.
More information about temporal filtering is available from the Getting started with temporal filtering guide.
The following sub-sections provide details about the attributes included with this related component, their data types in the different output formats, and other important metadata about them.
Primary key providing a unique row identifier assigned to enable indexing for efficient querying.
Data Types: String (GPKG), String (CSV)
Nullable: false
Max Length: 36
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
Unique Property Reference Number (UPRN) assigned by a local custodian or Ordnance Survey as a persistent identifier.
Data Types: Integer (GPKG), Integer (CSV)
Nullable: false
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
Date of the feature version to which this related component applies.
Data Types: Date (GPKG), Date (CSV)
Nullable: false
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
Alphanumeric code used to classify the object using the AddressBase Classification Scheme, which is available to download from the AddressBase Classification Scheme page of the OS Download Products’ Documentation site.
Data Types: String (GPKG), String (CSV)
Nullable: false
Max Length: 6
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
Description of the classification code as defined in the AddressBase Classification Scheme, which is available to download from the AddressBase Classification Scheme page of the OS Download Products’ Documentation site.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 230
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
Name of the classification schema.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 60
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
Version of the classification schema.
Data Types: Float (GPKG), Real (CSV)
Nullable: true
Precision: 2
Scale: 1
OS Select+Build Filterable: No
Data Schema Version: 3.0
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 60
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The date on which any attribute of the record was last changed.
Data Types: Date (GPKG), Date (CSV)
Nullable: false
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
The Postal Address Related Component provides the Royal Mail delivery point address from Royal Mail's Postcode Address File (PAF) where it has been matched to a Local Authority address in the National Land and Property Gazetteer.
The following table provides details about this related component’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.
2.0
28 March 2023
Ongoing
Major version increment to align with concurrent major version increments made to four feature types in the GB Address and Islands Address Collections: Built Address, Historic Address, Non-Addressable Object, and Pre-Build Address. (Related components follow the versioning of the addressing feature types they are associated with.)
1.0
02 November 2022
Ongoing
Initial launch of the Postal Address Related Component.
Until September 2025, Postal Address Related Component was the fourth related component in the OS NGD. It has been discontinued in the latest data schema version 3.0 of the Built Address, Historic Address, Non-Addressable Object and Pre-Build Address Feature Types in the GB Address and Islands Address Collections, which released in September 2025.
The Postal Address Related Component contained delivery point data from the Royal Mail Postcode Address File (PAF). This information is now available in the new Royal Mail Address Feature Type (which launched in September 2025), which can be found in the GB Address and Islands Address Collections.
The Postal Address Related Component is still provided against the older (maintenance) data schema versions 1.0 and 2.0 of the Built Address, Historic Address, Non-Addressable Object and Pre-Build Address Feature Types in the GB Address and Islands Address Collections. These data schema versions are available for customers to use, but they are now older and in maintenance mode. (Data schema version 3.0 is the latest and recommended data schema version to use for these feature types.)
Please see Data schema versioning for in-depth information about data schema versioning in the OS NGD.
Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).
The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this related component's data schema versions are indicated in the Data schema version table above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.
More information about temporal filtering is available from the Getting started with temporal filtering guide.
The following sub-sections provide details about the attributes included with this related component, their data types in the different output formats, and other important metadata about them.
Royal Mail’s Unique Delivery Point Reference Number (UDPRN).
Data Types: Integer (GPKG), Integer (CSV)
Nullable: false
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
Unique Property Reference Number (UPRN) assigned by a local custodian or Ordnance Survey as a persistent identifier.
Data Types: Integer (GPKG), Integer (CSV)
Nullable: false
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
Date of the feature version to which this related component applies.
Data Types: Date (GPKG), Date (CSV)
Nullable: false
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The organisation name is the business name given to an Address within a building or small group of buildings. For example: TOURIST INFORMATION CENTRE. This field could also include entries for churches, public houses and libraries.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 60
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
For some organisations, department name is indicated because mail is received by subdivisions of the main organisation at distinct delivery points.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 60
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The sub building name and / or number are identifiers for subdivisions of properties.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 30
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The building name is a description applied to a single building or a small group of buildings, such as HIGHFIELD HOUSE. This also includes those building numbers that contain non-numeric characters, such as 44A. Some descriptive names, when included with the rest of the address, are sufficient to identify the property uniquely and unambiguously, for example, MAGISTRATES COURT. Sometimes the building name will be a blend of distinctive and descriptive naming, for example, RAILWAY TAVERN (PUBLIC HOUSE) or THE COURT ROYAL (HOTEL).
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 50
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The building number is a number given to a single building or a small group of buildings, thus identifying it from its neighbours, for example, 44. Building numbers that contain a range, decimals or non-numeric characters do not appear in this field but will be found in the Building Name or the Sub Building Name fields.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 4
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
In certain places, for example, town centres, there are named thoroughfares within other named thoroughfares, for example, parades of shops on a high street where different parades have their own identity. For example, KINGS PARADE, HIGH STREET and QUEENS PARADE, HIGH STREET.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 80
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
A thoroughfare is a road, track or named access route on which there are Royal Mail delivery points, for example, HIGH STREET.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 80
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
This is used to distinguish between similar thoroughfares or the same thoroughfare within a dependent locality. For example, Millbrook Industrial Estate and Cranford Estate in this situation: BRUNEL WAY, MILLBROOK INDUSTRIAL ESTATE, MILLBROOK, SOUTHAMPTON and BRUNEL WAY, CRANFORD ESTATE, MILLBROOK, SOUTHAMPTON.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 35
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
Dependent locality areas define an area within a post town. These are only necessary for postal purposes and are used to aid differentiation where there are thoroughfares of the same name in the same locality. For example, High Street in Shirley and Swaythling in this situation: HIGH STREET, SHIRLEY, SOUTHAMPTON and HIGH STREET, SWAYTHLING, SOUTHAMPTON.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 35
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The town or city in which the Royal Mail sorting office is located which services this record. There may be more than one, possibly several, sorting office in a town or city.
Data Types: String (GPKG), String (CSV)
Nullable: false
Max Length: 30
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The postcode unit that the Address is situated within. A postcode is an abbreviated form of address, made up of combinations of between five and seven alphanumeric characters. These alphanumeric characters are used by Royal Mail to help with the automated sorting of mail. A postcode may cover between 1 and 100 addresses. Postcodes (for example, NW6 4DP) are comprised of two components. The first component is the outward code (or ‘outcode’), which is the first two to four characters of a postcode, constituting the postcode area and the postcode district, for example, NW6. The outward code is the part of the postcode that enables mail to be sent from the accepting office to the correct area for delivery. The second component of a postcode is the inward code (or ‘incode’), which is the last three characters of the postcode, constituting the postcode sector and the postcode unit, for example, 4DP. The inward code is used to sort mail at the local delivery office. This field will contain the Royal Mail Postcode Address File (PAF) postcode where the Local Authority address has been matched to PAF. Where a match has not been made, the postcode information is sourced from Local Authority assigned data. In cases where the Local Authority do not hold a valid postcode, a spatial nearest neighbour function is used to spatially derive the postcode from the closest Address with a valid postcode.
Data Types: String (GPKG), String (CSV)
Nullable: false
Max Length: 8
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
Describes the address as a small or large user as defined by Royal Mail. A large user postcode typically receives over 100 pieces of mail per day.
Data Types: String (GPKG), String (CSV)
Nullable: false
Code List Name: postcodetypevalue
Max Length: 10
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
A two-character code uniquely identifying an individual delivery point within a postcode.
Data Types: String (GPKG), String (CSV)
Nullable: false
Max Length: 2
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The Welsh translation of Dependent Thoroughfare.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 80
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The Welsh translation of Thoroughfare.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 80
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The Welsh translation of Double Dependent Locality.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 35
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The Welsh translation of Dependent Locality.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 35
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The Welsh translation of Post Town.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 30
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
Post Office Box (PO Box) number or the British Forces Post Office (BFPO) number.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 6
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The date on which the PAF record was processed into the database.
Data Types: Date (GPKG), Date (CSV)
Nullable: false
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
Name of the originating data provider that defined the reference or link.
Data Types: String (GPKG), String (CSV)
Nullable: false
Max Length: 30
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The date on which any attribute of the record was last changed.
Data Types: Date (GPKG), Date (CSV)
Nullable: false
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The date on which this record was inserted into the Local Authority database.
Data Types: Date (GPKG), Date (CSV)
Nullable: false
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The date on which the record ceased to exist.
Data Types: Date (GPKG), Date (CSV)
Nullable: true
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The Alternate Address Related Component provides alternative address labels where they exist for the ‘current’ address represented on a given feature type.
There are two principal scenarios by which an Alternate Address can be created; both of these scenarios will result in addresses being present in the Alternate Address Related Component:
Official alternate addresses captured by Local Authorities
This occurs where there is a a variation on the official address held by Local Authorities that is represented by the preferred UPRN in the Built Address Feature Type.
For example, ‘10 High Street’ may have an Alternate Address label captured as ‘Rose Cottage’. These addresses are represented by an ‘Alternate’ classification in the Address Status attribute.
Examples:
Built Address: UPRN 12345: 12 High Street, addressstatus: Approved
Alternate Address: UPRN 12345: Rose Cottage, addresstatus: Alternate
An additional non-official address captured for lifecycle purposes
In the case of pre-build addresses, these alternate addresses commonly represent labels attached to the plot in earlier stages in the development cycle that have subsequently been updated. Historic Address Alternate Address labels, where held, will be early iterations of the address that became live and will be alternate addresses of the ‘current’ UPRN on the Pre-Build Feature Type.
Examples:
Built Address: UPRN 12345: Explorer House, Adanac Drive, SO15 0AS, addressstatus: Approved
Alternate Address: UPRN 12345: Development Site, addressstatus: Historic
Alternate Address: UPRN 12345: Plot 12, addressstatus: Historic
The following table provides details about this related component’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.
3.0
30 September 2025
Ongoing
Major version increment to align with concurrent major version increments made to four feature types in the GB Address and Islands Address Collections: Built Address, Historic Address, Non-Addressable Object, and Pre-Build Address. (Related components follow the versioning of the addressing feature types they are associated with.) Max length increased for the Alternate Sub Name and Full Address attributes.
2.0
28 March 2023
Ongoing
Major version increment to align with concurrent major version increments made to four feature types in the GB Address and Islands Address Collections: Built Address, Historic Address, Non-Addressable Object, and Pre-Build Address. (Related components follow the versioning of the addressing feature types they are associated with.) New attribution added to related component for Full Address, Lowest Floor Level and Highest Floor Level.
1.0
02 November 2022
Ongoing
Initial launch of the Alternate Address Related Component.
Please see Data schema versioning for in-depth information about data schema versioning in the OS NGD.
Temporal filtering allows you to order a one-off snapshot of data from the OS NGD from a current or past date. It is an optional step when you create a new data package in OS Select+Build (the OS NGD download service).
The earliest and latest dates on which you can request a one-off snapshot of a date in the past for this related component's data schema versions are indicated in the Data schema version table above. Please note that any data temporally filtered earlier than the specified launch date indicated in the table for the data schema versions may contain data inconsistencies.
More information about temporal filtering is available from the Getting started with temporal filtering guide.
The following sub-sections provide details about the attributes included with this related component, their data types in the different output formats, and other important metadata about them.
Primary key providing a unique row identifier assigned to enable indexing for efficient querying.
Data Types: String (GPKG), String (CSV)
Nullable: false
Max Length: 36
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
Unique Property Reference Number (UPRN) assigned by a local custodian or Ordnance Survey as a persistent identifier.
Data Types: Integer (GPKG), Integer (CSV)
Nullable: false
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
Date of the feature version to which this related component applies.
Data Types: Date (GPKG), Date (CSV)
Nullable: false
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
The Unique Street Reference Number (USRN), a unique and persistent identifier of a Street which is assigned by the Roads or Highway Authority.
Data Types: Integer (GPKG), Integer (CSV)
Nullable: false
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
The lifecycle status of a given Address, for example, Alternative, Approved, Historic.
Data Types: String (GPKG), String (CSV)
Nullable: false
Code List Name: addressstatuscode
Max Length: 11
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
The Alternate Sub Name provides an alternative address label to the one provided in the Sub Name. An alternative address label may be present for a number of reasons, for example, retention of an old address label or an alias address label has been recorded by the Local Authority.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 500
OS Select+Build Filterable: No
Data Schema Version: 3.0
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 110
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The Alternate Name provides an alternative address label to the one provided in the name. An alternative address label may be present for a number of reasons, for example, retention of an old address label or an alias address label has been recorded by the Local Authority.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 110
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
The Alternate Number provides an alternative address number to the one provided in the Number attribute.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 13
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
Name, number or descriptor that identifies the nearest accessible Street that an Address is located on or close to.
Data Types: String (GPKG), String (CSV)
Nullable: false
Max Length: 100
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
Name of a populated place within a settlement that the Street is located within. Where a locality can be a suburb, housing estate or commercial estate.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 35
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
Name of the settlement that the Street is located within. Where a settlement can be a City, Town, Village or Hamlet.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 35
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
Name of the island upon which an Address is located.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 50
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
The language in which the address label attribution has been captured for the alternative record.
Data Types: String (GPKG), String (CSV)
Nullable: false
Code List Name: languagevalue
Max Length: 3
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
The postcode unit that the Address is situated within. A postcode is an abbreviated form of address, made up of combinations of between five and seven alphanumeric characters. These alphanumeric characters are used by Royal Mail to help with the automated sorting of mail. A postcode may cover between 1 and 100 addresses. Postcodes (for example, NW6 4DP) are comprised of two components. The first component is the outward code (or ‘outcode’), which is the first two to four characters of a postcode, constituting the postcode area and the postcode district, for example, NW6. The outward code is the part of the postcode that enables mail to be sent from the accepting office to the correct area for delivery. The second component of a postcode is the inward code (or ‘incode’), which is the last three characters of the postcode, constituting the postcode sector and the postcode unit, for example, 4DP. The inward code is used to sort mail at the local delivery office. This field will contain the Royal Mail Postcode Address File (PAF) postcode where the Local Authority address has been matched to PAF. Where a match has not been made, the postcode information is sourced from Local Authority assigned data. In cases where the Local Authority do not hold a valid postcode, a spatial nearest neighbour function is used to spatially derive the postcode from the closest Address with a valid postcode.
Data Types: String (GPKG), String (CSV)
Nullable: false
Max Length: 8
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
Concatenation of the following address components: Organisation (Pre-Build and Built Address Feature Types only), Sub Name and / or Name and / or Number, Street Name, Locality, Town Name, Island Name and Postcode Locator.
Data Types: String (GPKG), String (CSV)
Nullable: false
Max Length: 1 000
OS Select+Build Filterable: No
Data Schema Version: 3.0
Data Types: String (GPKG), String (CSV)
Nullable: false
Max Length: 500
OS Select+Build Filterable: No
Data Schema Version: 2.0
Floor level represents either: the access point to the Address, or the floor level or levels that the Address is located on fully occupies or represents occupiable space within the property.
Data Types: String (GPKG), String (CSV)
Nullable: true
Max Length: 30
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
In cases where the Floor Level attribute contains a list of floor levels (for example, where a commercial organisation occupies multiple levels within a building), the first value provided will be taken as the lowest floor level. For example, where Floor Level attribute values are given as -1, 0, 1, 2, 3, the Lowest Floor Level is -1. Mezzanine levels may be represented by a partial number, for example, 1.5. If the Floor Level attribute only contains one value, that value will also be used by the Lowest Floor Level attribute.
Data Types: Float (GPKG), Real (CSV)
Nullable: true
Precision: 3
Scale: 1
OS Select+Build Filterable: No
Data Schema Version: 2.0, 3.0
In cases where the Floor Level attribute contains a list of floor levels (for example, where a commercial organisation occupies multiple levels within a building), the last value provided will be taken as the highest floor level. For example, where Floor Level attribute values are given as -1, 0, 1, 2, 3, the Highest Floor Level is 3. Mezzanine levels may be represented by a partial number, for example, 1.5. If the Floor Level attribute only contains one value, that value will also be used by the Highest Floor Level attribute.
Data Types: Float (GPKG), Real (CSV)
Nullable: true
Precision: 3
Scale: 1
OS Select+Build Filterable: No
Data Schema Version: 2.0, 3.0
The date on which any attribute of the record was last changed.
Data Types: Date (GPKG), Date (CSV)
Nullable: false
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
The date on which this record was inserted into the Local Authority database.
Data Types: Date (GPKG), Date (CSV)
Nullable: false
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0
The date on which the record ceased to exist.
Data Types: Date (GPKG), Date (CSV)
Nullable: true
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0, 3.0