Alternate Address

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.

  1. 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.

    Built Address: UPRN 12345: 12 High Street, addressstatus: Approved Alternate Address: UPRN 12345: Rose Cottage, addresstatus: Alternate

  2. 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. 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 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.

alternateaddressid

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

uprn

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

featuretypeversiondate

Date of the feature version to which this related entity applies.

  • Data Types: Date (GPKG), Date (CSV)

  • Nullable: false

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0

usrn

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

addressstatus

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

alternatesubname

The alternateSubName provides an alternative address label to the one provided in the subName. An alternative address label may be present for a number of reasons, e.g. 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

alternatename

The alternateName provides an alternative address label to the one provided in the name. An alternative address label may be present for a number of reasons, e.g. 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

alternatenumber

The alternateNumber 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

streetname

Name, number or descriptor that identifies the nearest accessable 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

locality

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

townname

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

islandname

Name of the island upon which an Address is located. Note: This attribute is currently only populated in the OS NGD Islands Address Collection.

  • Data Types: String (GPKG), String (CSV)

  • Nullable: true

  • Max Length: 50

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0

language

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

postcode

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

fulladdress 🆕

This is a new attribute in data schema version 2.0, available from the end of March 2023.

Concatenation of the following address components: organisation (Pre-Build and Built Address Feature Types only), subname and / or name and / or number, streetname, locality, townname, islandname and postcodelocator.

  • Data Types: String (GPKG), String (CSV)

  • Nullable: false

  • Max Length: 500

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.0

floorlevel

Floor level represents either: The level on which the access point to the Address is present, or the floor level or levels that the Address is located on, or fully occupies.

  • Data Types: String (GPKG), String (CSV)

  • Nullable: true

  • Max Length: 30

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0

lowestfloorlevel 🆕

This is a new attribute in data schema version 2.0, available from the end of March 2023.

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.

This attribute is derived from Floor Level attribute data. Where the floorlevel field is NULL, lowestfloorlevel values will also be NULL.

  • Data Types: Float (GPKG), Real (CSV)

  • Nullable: true

  • Precision: 3

  • Scale: 1

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.0

highestfloorlevel 🆕

This is a new attribute in data schema version 2.0, available from the end of March 2023.

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.

This attribute is derived from Floor Level attribute data. Where the floorlevel field is NULL, highestfloorlevel values will also be NULL.

  • Data Types: Float (GPKG), Real (CSV)

  • Nullable: true

  • Precision: 3

  • Scale: 1

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.0

updatedate

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

effectivestartdate

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

effectiveenddate

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

Last updated