> For the complete documentation index, see [llms.txt](https://docs.os.uk/more-than-maps/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.os.uk/more-than-maps/data-demonstrators/addressing-and-location-demonstrators/os-ngd-address/os-ngd-address.md). # OS NGD Address A Lightning Talk ## OS NGD Address Overview The OS National Geographic Database (NGD) Address theme provides a complete and definitive view of addresses in the UK. It is made up of two collections; GB Address (England, Wales and Scotland) and Islands Address (Northern Ireland, Channel Islands and Isle of Man). The collections within the OS NGD Address Theme contain all the address data from the AddressBase Premium product, including: * Local Authority and Royal Mail postal addresses where matched to a UPRN (Unique Property Reference Number). * Property Lifecycle information. * Addresses for features that are not conventionally addressable (e.g. churches, car parks, cattle grids). * Multi-lingual addresses. * Alternate addresses. However, with the OS NGD Address theme you can also: * Keep your address data current with up-to-daily updates. * Easily identify and download addresses by pre-build, built, and historic lifecycle stages. * Use the UPRN to easily link different data sets and other OS NGD themes (e.g. NGD Buildings). * Access additional Royal Mail datasets; Not Yet Built and Multiple Residence. * Access LPI address and alternative language information more easily. * Access additional attribution such as floor level and information on parent/child UPRN relationships. For a detailed comparison between AddressBase and OS NGD Address, see [here](https://docs.os.uk/more-than-maps/os-ngd-migration/comparison-of-end-of-life-address-products). {% hint style="info" %} The information on this page is applicable to the **latest data schema versions** of all address feature types as of October 2026 (that is, data schema version 3.0 of Built Address, Historic Address, Non-Addressable Object and Pre-Build Address, data schema version 1.0 of Street Address, and data schema version 2.0 of Royal Mail Address). For further information about previous schema versions and previous data structures, visit the OS NGD Address [theme page](https://docs.os.uk/osngd/data-structure/address). {% endhint %} ## What are the feature types within OS NGD Address? OS NGD Address data is made up of two collections, each comprising six feature types: ​ * [Built Address](https://docs.os.uk/osngd/data-structure/address/gb-address/built-address): Addresses that are currently built and live and can typically receive mail, deliveries, or services. For example: homes, shops, schools, and hospitals. * [Historic Address](https://docs.os.uk/osngd/data-structure/address/gb-address/historic-address): Addresses assigned to property units no longer in existence. This can occur as a result of the demolition or merging of two built properties to become one new single address. * [Pre-Build Address](https://docs.os.uk/osngd/data-structure/address/gb-address/pre-build-address): Addresses where the property is either yet to be built but has been granted planning permission or is under construction, and will be able to receive mail, deliveries or services in future. * [Non-Addressable Object](https://docs.os.uk/osngd/data-structure/address/gb-address/non-addressable-object): Live objects that would not be expected to be able to receive mail or deliveries. * [Street Address](https://docs.os.uk/osngd/data-structure/address/gb-address/street-address): Street address information for any road, footpath, cycleway, byway, or bridleway that has been uniquely identified by a Local Highway Authority or Street Naming and Numbering (SNN) Authority and that provides access to an address. * [Royal Mail Address](https://docs.os.uk/osngd/data-structure/address/gb-address/royal-mail-address): Delivery Point Address data defined by Royal Mail and additional attribution. {% hint style="info" %} In schema versions 1.0 and 2.0 of the Built Address, Historic Address, Non-Addressable Object and Pre-Build Address Feature Types, Royal Mail data existed as the [Postal Address Related Component](https://docs.os.uk/osngd/data-structure/address/address-related-components/postal-address). In schema versions 3.0 and onwards, the Postal Address related component table no longer exists as its contents are now part of the Royal Mail Address feature type. For further information about previous schema versions and previous data structures, visit the OS NGD Address [theme page](https://docs.os.uk/osngd/data-structure/address). {% endhint %}

Related Components in the OS NGD Address theme and the feature types that they are connected to

## What formats is​ OS NGD Address data supplied in?​​ The OS NGD Address data comes in two formats, CSV and GeoPackage (GPKG)​. * The GeoPackage format comes ready to load into the GIS package of the users choice with separate GeoPackage files for each layer. * The CSV format is more suited for loading into a database. It has all of the same layers and attribution as the GeoPackage format, however instead of storing the geometry in a GIS ready format, it is stored as a POINT attribute with the vertices stored as co-ordinates in the text file.​ ## What is the attribution?​

Attribution across feature types in OS NGD address. Attributes with a * were only introduced in version 2.0 of Built Address, Historic Address, Non-Addressable Object and Pre-Build Address Feature Types (click on the image to enlarge it).

### Built, Prebuild, Historic and Non-addressable Objects For the built, prebuild, historic and non addressable objects feature types, the attribution is consistent, for example: * These OS NGD Address Features have a UPRN and information on the versioning and change type​. * The LPI address for the record, including in alternate language. * Information on the classification of the address and the build status are present​. * There is a flag for denoting where a PAF match is present. * Information on the parent/child relationship with other UPRNs and information on the link to the USRN​. * There is information on the custodian that provided the original information and the geometry that has been provided​. In version 2.0 of these feature types, the following attributes were added: * ​Full Address and Alternative Language Full Address: A single line address field formed from Local Authority data. The single line address attribute pulls all of the address text into a single field.​ * ​Lowest Floor Level and Highest Floor Level​: Where an address occupies multiple floors within a building, the highest and lowest levels are available in these two new fields.​ * Primary / Secondary / Tertiary / Quaternary Classification Descriptions: These fields contain the classification descriptions instead of the alphanumeric codes.​
Image of a highlighted address and the attribution

Example attribution for OS NGD Address

Image of a highlighted address and the attribution for version 2

Example additional attribution for version 2.0 and onwards of OS NGD Address

### Street Address The Street Address feature type is structured differently to the feature types discussed above. As of October 2026, it has only had one version. The OS NGD Streets Address data has:​ * A Unique Street Reference Number (USRN), information ​\ on the versioning and change type​ * Information on the street type and classification​ * The street name, locality, town name, etc – with information on alternate language​ * Information on the custodian that provided the original information and the geometry that has been provided​
Image of a highlighted street address and the attribution

Example attribution for Street Address features in OS NGD Address

### Royal Mail Address Royal Mail Address feature type is structured differently to the other feature types. * OS NGD Royal Mail Address Features have a UDPRN and information on the Royal Mail source dataset​. * Where possible, the relationship between Royal Mail UDPRNs and Local Authority UPRNs is exposed through the presence of a ‘match’ and additional attribution explaining the nature of the match. * Information on the classification of the address is not present, but can be obtained by linking to other feature types (build address, pre-build address etc.) via the UPRN. * There is a flag for denoting where a PAF match is present. * Information on parent/child relationships can be inferred by linking to the Multiple Residence related component table. * Information on how OS has derived the geometry for each Royal Mail record. Please see our [dedicated page](https://docs.os.uk/more-than-maps/data-demonstrators/addressing-and-location-demonstrators/os-ngd-address/royal-mail-address-feature-type) on the Royal Mail Address feature type, including information on the latest updates. ## Related Component Tables Additional related component tables are supplied with Built Address, Historic Address, Non-Addressable Object and Pre-Build Address feature types that can be joined using UPRNs. These are: * [**Alternate Address**](https://docs.os.uk/osngd/data-structure/address/address-related-components/alternate-address): Alternative address labels where they exist for the ‘current’ address represented on a given feature type. * [**Other Classification**](https://docs.os.uk/osngd/data-structure/address/address-related-components/other-classification): Additional Valuation Office Agency (VOA) classification information. * [**Related Entity**](https://docs.os.uk/osngd/data-structure/address/address-related-components/related-entity): 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. Related component tables are also supplied with the Royal Mail Address feature type, as of schema version 2.0: * [**Multiple Residence**](https://docs.os.uk/osngd/data-structure/address/address-related-components/multiple-residence): Identify addresses that have a shared delivery point. * [**Delivery Point Alias**](https://docs.os.uk/osngd/data-structure/address/address-related-components/delivery-point-alias): Alias' for delivery points from Royal Mail's Delivery Point Alias (DPA) table. * [**Other Alias**](https://docs.os.uk/osngd/data-structure/address/address-related-components/other-alias): Alternate names for counties, localities and thoroughfares For further information on related components and how to use them, visit the [related components section](https://docs.os.uk/osngd/data-structure/address/address-related-components) of the OS NGD Address documentation. {% hint style="info" %} In schema versions 1.0 and 2.0 of the Built Address, Historic Address, Non-Addressable Object and Pre-Build Address Feature Types, Royal Mail data existed as the [Postal Address Related Component](https://docs.os.uk/osngd/data-structure/address/address-related-components/postal-address). In schema versions 3.0 and onwards, the Postal Address related component table no longer exists as its contents are now part of the Royal Mail Address feature type. For further information about previous schema versions, visit the OS NGD Address [theme page](https://docs.os.uk/osngd/data-structure/address). {% endhint %} *** Links that may be useful: {% embed url="" %} {% embed url="" %} This content has been developed from what was originally a Lightning Talk PowerPoint slide set. These slides are available to PSGA members to view and download from the [PSGA members area of the OS website](https://auth.ordnancesurvey.co.uk/my.policy) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.os.uk/more-than-maps/data-demonstrators/addressing-and-location-demonstrators/os-ngd-address/os-ngd-address.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.