All pages
Powered by GitBook
1 of 6

OS NGD Buildings

Introduction to the theme

The OS NGD Buildings Theme contains building features which meet the definition of a permanent roofed construction, usually with walls. Embedded height attribution is available for Building and Building Part features, enabling users to create simple height models.

OS NGD Buildings data is the most comprehensive and high-quality set of buildings data available for Great Britain ever produced by OS.

In comparison to OS MasterMap Download products, OS NGD buildings data has been enriched with additional attribution, including the following:

  • Geometry change metadata

  • A Description attribute to provide a one-word or simple phrase description of a feature

  • Detailed land use classification

  • Detailed land cover classification

  • Capture specification to give details about the geography of the area a feature resides in (that is, urban, rural, or moorland)

  • Roof shape, aspect and material

  • Solar panel and green roof presence

  • Number of floors within a building

  • Building age

  • Basement presence

  • Building construction material

Data structure

The OS NGD Buildings Theme is made up of the OS NGD Building Features Collection, which in turn is comprised of Building, Building Access Location, Building Line and Building Part Feature Types.

Tree diagram showing the data structure of the OS NGD Buildings Theme. It lists the theme name, collection name, and feature type names.
OS NGD Buildings Theme data structure diagram showing the theme name, collection name and feature type names.

Unique identifiers

One main unique identifier is provided with each feature within the OS NGD Buildings Theme:

  • OSID (Ordnance Survey Identifier): The primary identifier and unique key for this theme.

A TOID (Topographic Identifier) is an additional secondary identifier which can aid further data linking. TOIDs are an optional attribute and therefore will not always be provided with every feature. TOIDS are usually provided for Building Line and Building Part features; they are not provided for Building or Building Access Location features.

Useful links

Building Features

The OS NGD Building Features Collection gives you access to the most current and comprehensive buildings data captured by Ordnance Survey as a standalone collection.

Example images showing what the feature types in the OS NGD Building Features Collection look like in the data. Background maps have been included to provide context.
Example images showing what the four feature types in the OS NGD Building Features Collection look like in the data. Background maps have been included to provide context.

Collection key elements, supply mechanism and summary

OS Building Features Collection provides:

  • Up to daily updates to data.

  • Plug and play – the data is simple and quick to implement as you don't need to pre-process it before you use it.

  • Rich attribution ensures the data is straightforward to navigate and query for items of interest, for example, using the Building Use or Connectivity attribution.

  • Simplified attribute naming helps make names easier to understand.

  • Persistent unique identifiers with lifecycle information.

  • Height data included.

  • Land use classification (for example, residential accommodation) provided for the Building Part Feature Type to indicate the prominent use of the site which contains the building.

  • National land use standards used to provide universal insights for human activity (NLUD classification and BS7666 national addressing classification).

  • An Office for National Statistics (ONS) Government Statistical Service (GSS) code is provided for Building Part features within Lower Tier Local Authority areas to indicate which Lower Tier Local Authority boundary the feature lies within.

  • Building Part features have a value provided for the Status attribute (i.e. 'Active', 'Derelict', 'Inactive', 'Under Construction' or 'Unknown') to indicate the state of the feature in relation to either its physical condition or the activity the feature is intended to support. This value is either inherent from the nature of the topographic feature or can be inherited from the Site the Building Part feature lies within. Individual Building Part features within a Site may not themselves be derelict, but the value provided for the Status attribute will reflect the general nature of the Site.

You can access OS Building Features data through the OS Data Hub via:

  • OS Select+Build (the bespoke OS NGD download service)

  • OS NGD API – Features

  • OS NGD API – Tiles (only available for one feature type in the collection: Building Part)

  • Coverage: Great Britain

  • Default coordinate reference system: British National Grid (EPSG: 27700)

  • Temporal filtering: The earliest date on which you can request a one-off snapshot of a date in the past for data in this collection is noted at the top of the individual feature type pages.

  • Supply formats:

    • GeoPackage

    • CSV (comma-separated values)

    • GeoJSON

    • Vector tiles (only available for one feature type in the collection: Building Part)

  • Using our data:

    • Included in the Public Sector Geospatial Agreement (PSGA) – therefore, it's free at point of use for Public Sector organisations.

    • Available to OS Partners for commercial resell in your solutions.

Collection applications

The OS NGD Building Features Collection allows you to:

  • Ensure your buildings data is always completely up to date with up to daily updates.

  • Perform powerful analytics, underpinned by unrivalled OS accuracy.

  • Use enhanced change metadata to monitor and understand how the building landscape is changing.

  • Determine whether buildings are residential or commercial by using the Building Use, Description or Address Count attributes. Alternatively, use the cross references to feature types in the OS NGD Address or OS NGD Land Use Themes.

Building Access Location Feature Type applications

The Building Access Location Feature Type allows you to:

  • Identify vehicle and pedestrian access locations for buildings.

  • Use detailed access point data to improve urban development projects.

  • Determine precise access information for emergency response planning and deployment.

  • Find quicker resolutions and potentially minimise the impact of incidents.

  • Support covert policing operations by providing additional information for intelligence-gathering purposes.

  • Enhance understanding and resilience planning for hazards, leading to more informed decision-making, better situational awareness and efficient management of various situations.

  • Identify wheelchair-friendly access points for disabled users, promoting inclusivity and enhancing accessibility.

  • Create better route planning for logistics and two-man delivery services.

  • Recognise new developments based on accessibility for vehicles and pedestrians.

  • Improve the planning and management of large-scale events.

  • Aid in travel modelling and accessibility to services for the public.

An example of how this feature type can be visualised is shown in the image below:

Example of Access Points data that shows the different types of access points within a football stadium on a colour background map for context. Image shows Access Points listed evenly around the perimeter of the stadium.
Example visualisation showing the different types of access points within a football stadium for purposes of emergency response and evacuations.

Building Part Feature Type applications

The Building Part Feature Type allows you to:

  • Quickly interpret building type (such as clock tower, multi-storey car park or archway) using the Description attribute.

  • Create simple height models of buildings by using the embedded height attribution.

Building Feature Type applications

The Building Feature Type allows you to:

  • Perform easy selection and analysis of individual buildings using new building footprint geometry.

  • Quickly understand the building use (for example, Commercial Retail) and building connectivity (for example, standalone) using the Building Use and Connectivity attributes.

Examples of how these attributes can be visualised are shown in the images below:

Example that shows the Building Use attribute of the Building Feature Type. A background map is included for context.
Example showing the Building Use attribute of the Building Feature Type. A background map is included for context.
Example that shows the Connectivity attribute of the Building Feature Type. A background map is included for context.
Example showing the Connectivity attribute of the Building Feature Type. A background map is included for context.

  • Perform easy data linkage both within and outside (to other OS NGD collections) the OS NGD Building Features Collection using the provisioned cross reference tables.

  • Quickly identify and select buildings of interest using integrated address count information.

  • Determine the age of a building using the Building Age Period or Building Age Year attributes to determine the condition and potential maintenance costs. Identify the source of this information using the Building Age Third Party Provenance attribute.

  • Identify the primary construction material for a building to develop an understanding of the building's energy performance (using the Construction Material attribute). Identify the source of this information using the Construction Material Third Party Provenance attribute.

  • Use the Basement Presence and Basement Presence Self Contained attributes to check whether a building has a basement or basement flat to inform building safety standards plans and / or emergency response plans, to improve insurance underwriting and to detect insurance fraud. Identify the source of this information using the Basement Presence Third Party Provenance attribute.

  • Quickly identify and select buildings of interest using the Building Description attribute. Examples of how these attributes can be visualised are shown in the images below:

Example that shows the Building Age Period attribute of the Building Feature Type. A background map is included for context.
Example showing the Building Age Period attribute of the Building Feature Type. A background map is included for context.
Example that shows the Basement Presence attribute of the Building Feature Type. A background map is included for context.
Example showing the Basement Presence attribute of the Building Feature Type. A background map is included for context.
Example that shows the Construction Material attribute of the Building Feature Type. A background map is included for context.
Example showing the Construction Material attribute of the Building Feature Type. A background map is included for context.
Example that shows the Building Description attribute of the Building Feature Type. A background map is included for context.
Example showing the Building Description attribute of the Building Feature Type. A background map is included for context.

Number of floors attribution

The Number of Floors attribution in the Building Feature Type allows you to:

  • Provide situational awareness for Emergency Services to ensure an appropriate response to incidents and to enable preparedness plans to be put in place.

  • Identify taller buildings for Building Fire Risk Reviews.

  • Identify and select buildings of interest due to buildings standards and regulation changes which could result in remedial action being required (for example, Post-Grenfell Disaster Report).

  • Identify cases for tax benefits which are available to businesses who are building or doing renovations on buildings with a significant number of floors (HMRC).

  • Potentially use the data as a proxy to indicate potential occupancy to aid service provision planning (for example, by the Utilities Sector).

  • Use the data as a proxy for floor height to estimate pressures required by utility companies.

  • Integrate the number of floors into 3D modelling and digital twin models.

An example of how the Number of Floors attribute can be visualised is shown in the image below:

Example that shows the Number of Floors attribute of the Building Feature Type. A background map is included for context.
Example showing the Number of Floors attribute of the Building Feature Type. A background map is included for context.

Roof enhancements attribution

The roof enhancements attribution in the Building Feature Type allows you to:

  • Identify buildings suitable for solar panel installations by combining data on roof material, roof shape, roof aspect, and solar panel presence. This supports initiatives for sustainable energy and helps in achieving carbon neutrality goals.

  • Model potential heat loss from buildings using integrated roof material and roof shape data. This is crucial for developing energy-efficient buildings and retrofitting existing structures to improve insulation.

  • Assess the vulnerability of buildings to fire and flood risks.

  • Create insights into the potential rebuild costs of a building in case of damage; this helps insurers in setting accurate premiums and managing risk.

  • Predict when repairs and maintenance might be needed.

  • Maintain an up-to-date view of roof materials for listed buildings, which is crucial for preservation efforts and compliance with regulations.

  • Monitor the progress of government policies aimed at reducing carbon emissions; this data can also help in planning future initiatives and setting realistic targets.

  • Identify areas that contribute to the urban heat island effect and implement measures to mitigate it.

Examples of how the roof enhancement attributes can be visualised are shown in the images below:

Example showing the Roof Aspect attribution available for the Building Feature Type. Image shows summed geometric area values that are aggregated to the cardinal and ordinal direction they face.
Example showing the Roof Aspect attribution of the Building Feature Type.
Example showing the primary roof material present on OS NGD Building features against a background map. Four types of roof material are shown.
Example showing the primary roof material present on Building features. A background map is included for context.
Example showing solar panel presence on OS NGD Building features against a background map. Image shows five buildings marked with solar panel presence in yellow.
Example showing solar panel presence on Building features. A background map is included for context.
Example that shows Green Roof attribution of the Building Feature Type. Image shows a building where roof is present, indicated in green against a background map.
Example showing the Green Roof attribution of the Building Feature Type. A background map is included for context.
Example showing the primary form of roofs present on OS NGD Building features against a background map. Image shows multiple types of roofs, including Flat, Mixed, and Pitched present in an area.
Example showing the primary form of roofs present on Building features. A background map is included for context.

Physical State attribution

The Physical State attribute in the Building Feature Type allows you to:

  • Assess the pace and progress of construction projects from start through to completion (Developers).

  • Conduct market analysis of fibre network targets (Telecoms companies).

  • Identify derelict buildings with active gas or electricity meters to help prevent safety hazards, reduce financial losses and ensure accurate billing (Utility companies).

  • Conduct insurance risk assessments for buildings based on their physical state (Insurance companies).

  • Conduct risk planning and situational awareness (Emergency Services).

  • Quickly and easily identity derelict buildings (supporting both Local Authorities' remit on bringing derelict buildings back into use and Government's target for new homes).

Examples of how the Physical State attribute can be visualised are shown in the images below:

Example showing the Physical State attribution of the Building Feature Type. A background map is included for context. Built buildings are coloured blue on the map; Under Constructions buildings are coloured yellow on the map; Derelict buildings are coloured red on the map.
Example showing the Physical State attribute of the Building Feature Type. A background map is included for context.
Visualisation showing the three building lifecycle values for the Physical State attribute of the Building Feature Type: Under Construction, Built and Derelict. Three images of a house are shown, with one house being under construction, one being complete and built, and one house being derelict and in a state of disrepair.
Visualisation showing the three building lifecycle values for the Physical State attribute of the Building Feature Type: Under Construction, Built and Derelict.

Building

A new building geometry which represents a single building footprint. This geometry consists of adjoining building parts which have been determined to be part of the same building. When contained in a Land Use Site, adjoining building parts will be represented by a single feature.

Data schema versioning

The following table provides details about this feature type’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

Data schema version table

Version ↓
Launch Date
Latest Date
Change

4.0

27 March 2025

Ongoing

Major version increment adding new Height metadata, Physical State, Roof Material, and Roof Shape Aspect attribution.

3.0

25 September 2024

Ongoing

Major version increment adding new Number Of Floors attribution and amending the names of some existing attributes.

2.0

27 March 2024

Ongoing

Major version increment adding new Description, Construction Material, Building Age, and Basement Presence attribution.

1.0

27 September 2023

Ongoing

Initial launch of the Building Feature Type.

Please see Data schema versioning for in-depth information about data schema versioning in the OS NGD.

Temporal filtering

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 feature type'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 on OS NGD feature types is available from the Getting started with temporal filtering guide.

Feature type attributes

The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

Loading OS NGD CSV files into databases

Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our OS NGD Resources GitHub repository.

For instructions on loading CSV files, see the Getting Started with CSV guide.

osid

Primary identifier for the feature. The OSID is a Globally Unique Identifier (GUID) and requires no centralised authority to ensure uniqueness. Note that the same OSID can occur in more than one feature type when a single feature is represented multiple times in the OS NGD.

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

  • Nullable: false

  • Max Length: 36

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

versiondate

Date when the version was last updated.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

versionavailablefromdate

The date this version of the feature became the latest version.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

versionavailabletodate

The date this version of the feature was superseded by an update or ceased to exist.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

changetype

The type of change that generated a new version of the feature.

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

  • Nullable: false

  • Code List Name: changetypevalue

  • Max Length: 50

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

geometry

Geometry for the feature.

  • Data Types: Geometry (GeoJSON), Geometry (GPKG), WKT (CSV)

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

  • Geometry Type: Polygon

geometry_area_m2

The measured area of the geometry in square metres.

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

  • Nullable: false

  • Precision: 15

  • Scale: 3

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

geometry_updatedate

Date when the attribute was last updated.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

theme

The OS NGD theme to which the feature belongs.

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

  • Nullable: false

  • Code List Name: themevalue

  • Max Length: 40

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

description

A single descriptive value intended for a quick understanding of what the feature represents.

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

  • Nullable: false

  • Code List Name: buildingdescriptionvalue

  • Max Length: 45

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 2.0, 3.0, 4.0

description_updatedate

Date when the description was last updated.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.0, 3.0, 4.0

physicalstate

The state of the building in relation to its physical condition.

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

  • Nullable: false

  • Code List Name: physicalstatevalue

  • Max Length: 20

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 4.0

physicalstate_updatedate

Date when the physical state was last updated.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

buildingpartcount

Count of building parts within the building.

  • Data Types: Integer (GeoJSON), Integer (GPKG), Integer (CSV)

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

isinsite

Flag to indicate whether the building is within a Land Use Site.

  • Data Types: Boolean (GeoJSON), Integer (GPKG), String (CSV)

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

primarysiteid (formerly primarysite_id)

This attribute was called primarysite_id in data schema versions 1.0 and 2.0, and was renamed primarysiteid from version 3.0 onward.

Identifier of the primary site associated with the building. The primary site is the smallest site which contains the building feature.

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

  • Nullable: true

  • Max Length: 36

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

containingsitecount

Count of sites that the building is contained within.

  • Data Types: Integer (GeoJSON), Integer (GPKG), Integer (CSV)

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

mainbuildingid (formerly mainbuilding_id)

This attribute was called mainbuilding_id in data schema versions 1.0 and 2.0, and was renamed mainbuildingid from version 3.0 onward.

Populated if the feature is not the main building. Can be used to identify the main building within the same site.

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

  • Nullable: true

  • Max Length: 36

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

mainbuildingid_ismainbuilding (formerly ismainbuilding)

This attribute was called ismainbuilding in data schema versions 1.0 and 2.0, and was renamed mainbuildingid_ismainbuilding from version 3.0 onward.

Flag to indicate whether the building is the primary building within the site. This has been captured by OS surveyors as the most normal building a casual visitor would report to within the Land Use Site.

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

  • Nullable: true

  • Code List Name: yesnovalue

  • Max Length: 5

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 3.0, 4.0

  • Data Types: Boolean (GeoJSON), Integer (GPKG), String (CSV)

  • Nullable: true

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0

mainbuildingid_updatedate (formerly mainbuilding_updatedate)

This attribute was called mainbuilding_updatedate in data schema versions 1.0 and 2.0, and was renamed mainbuildingid_updatedate from version 3.0 onward.

Date when the main building was updated.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

buildinguse

Describes what the Building is used for and can have up to two values. The value will be 'Mixed Use' where more than two uses are identified.

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

  • Nullable: false

  • Code List Name: buildingusevalue

  • Max Length: 100

  • Multiplicity: [1..2]

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

buildinguse_oslandusetiera (formerly oslandusetiera)

This attribute was called oslandusetiera in data schema versions 1.0 and 2.0, and was renamed buildinguse_oslandusetiera from version 3.0 onward.

A high-level description of the main activity that takes place at the location or that the feature supports.

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

  • Nullable: true

  • Code List Name: landusetieravalue

  • Max Length: 50

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

buildinguse_addresscount_total (formerly addresscount_total)

This attribute was called addresscount_total in data schema versions 1.0 and 2.0, and was renamed buildinguse_addresscount_total from version 3.0 onward.

Total count of built in-use address UPRNs associated with the building.

  • Data Types: Integer (GeoJSON), Integer (GPKG), Integer (CSV)

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

buildinguse_addresscount_residential (formerly addresscount_residential)

This attribute was called addresscount_residential in data schema versions 1.0 and 2.0, and was renamed buildinguse_addresscount_residential from version 3.0 onward.

Count of residential built in-use address UPRNs associated with the building.

  • Data Types: Integer (GeoJSON), Integer (GPKG), Integer (CSV)

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

buildinguse_addresscount_commercial (formerly addresscount_commercial)

This attribute was called addresscount_commercial in data schema versions 1.0 and 2.0, and was renamed buildinguse_addresscount_commercial from version 3.0 onward.

Count of commercial built in-use address UPRNs associated with the building.

  • Data Types: Integer (GeoJSON), Integer (GPKG), Integer (CSV)

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

buildinguse_addresscount_other (formerly addresscount_other)

This attribute was called addresscount_other in data schema versions 1.0 and 2.0, and was renamed buildinguse_addresscount_other from version 3.0 onward.

Count of other (not residential or commercial) built in-use address UPRNs associated with the building.

  • Data Types: Integer (GeoJSON), Integer (GPKG), Integer (CSV)

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

buildinguse_updatedate

Date when the building use was updated.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

connectivity

Describes how the building is connected to other buildings.

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

  • Nullable: false

  • Code List Name: buildingconnectivitytypevalue

  • Max Length: 15

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

connectivity_count (formerly connectivitycount)

This attribute was called connectivitycount in data schema versions 1.0 and 2.0, and was renamed connectivity_count from version 3.0 onward.

Count of connected buildings.

  • Data Types: Integer (GeoJSON), Integer (GPKG), Integer (CSV)

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

connectivity_updatedate

Date when the building connectivity was updated.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

constructionmaterial

The primary material from which the building is constructed. Construction material is recorded for addressable buildings. It may be recorded for some non-addressable buildings, but the majority of these will have construction material recorded as NULL.

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

  • Nullable: true

  • Code List Name: constructionmaterialvalue

  • Max Length: 40

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 2.0, 3.0, 4.0

constructionmaterial_evidencedate

The date on which the latest evidence was gathered to make an update if required. For example, the date of collection by a surveyor or third party information received.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.0, 3.0, 4.0

constructionmaterial_updatedate

Date when the construction material was last updated.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.0, 3.0, 4.0

constructionmaterial_source

Indicates the data source of the construction material.

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

  • Nullable: true

  • Code List Name: constructionmaterialsourcevalue

  • Max Length: 85

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.0, 3.0, 4.0

constructionmaterial_capturemethod

The capture method describes how the construction material was created, for example, via remote survey or via an automated process.

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

  • Nullable: true

  • Code List Name: capturemethodvalue

  • Max Length: 25

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.0, 3.0, 4.0

constructionmaterial_thirdpartyprovenance

The provenance of the construction material provided by the third party data provider, for example, the name of an organisation and the specific dataset provided by that organisation.

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

  • Nullable: true

  • Max Length: 65

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.0, 3.0, 4.0

buildingage_period

The period (i.e. a range of years) in which the building was constructed. Construction period is recorded for addressable buildings. It may be recorded for some non-addressable buildings, but the majority of these will have construction period recorded as NULL.

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

  • Nullable: true

  • Code List Name: buildingageperiodvalue

  • Max Length: 10

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 2.0, 3.0, 4.0

buildingage_year

The year in which the building was constructed, for buildings constructed post-1999 and where available.

  • Data Types: Integer (GeoJSON), Integer (GPKG), Integer (CSV)

  • Nullable: true

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 2.0, 3.0, 4.0

buildingage_evidencedate

The date on which the latest evidence was gathered to make an update if required. For example, the date of collection by a surveyor or third party information received.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.0, 3.0, 4.0

buildingage_updatedate

Date when the building age was last updated.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.0, 3.0, 4.0

buildingage_source

Indicates the data source of the building age.

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

  • Nullable: true

  • Code List Name: buildingagesourcevalue

  • Max Length: 85

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.0, 3.0, 4.0

buildingage_capturemethod

The capture method describes how the building age was created, for example, via remote survey or via an automated process.

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

  • Nullable: true

  • Code List Name: capturemethodvalue

  • Max Length: 25

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.0, 3.0, 4.0

buildingage_thirdpartyprovenance

The provenance of the building age provided by the third party data provider, for example, the name of an organisation and the specific dataset provided by that organisation.

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

  • Nullable: true

  • Max Length: 65

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.0, 3.0, 4.0

basementpresence

Indicates if a basement is present in the building. Basement presence is recorded for addressable buildings. It may be recorded for some non-addressable buildings, but the majority of these will have basement presence recorded as NULL.

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

  • Nullable: true

  • Code List Name: presencevalue

  • Max Length: 15

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 2.0, 3.0, 4.0

basementpresence_selfcontained

Indicates if the basement contains a self-contained flat.

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

  • Nullable: true

  • Code List Name: presencevalue

  • Max Length: 15

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 2.0, 3.0, 4.0

basementpresence_evidencedate

The date on which the latest evidence was gathered to make an update if required. For example, the date of collection by a surveyor or third party information received.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.0, 3.0, 4.0

basementpresence_updatedate

Date when the basement presence was last updated.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.0, 3.0, 4.0

basementpresence_source

Indicates the data source of the basement presence.

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

  • Nullable: true

  • Code List Name: basementpresencesourcevalue

  • Max Length: 85

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.0, 3.0, 4.0

basementpresence_capturemethod

The capture method describes how the basement presence was created, for example, via remote survey or via an automated process.

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

  • Nullable: true

  • Code List Name: capturemethodvalue

  • Max Length: 25

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.0, 3.0, 4.0

basementpresence_thirdpartyprovenance

The provenance of the basement presence provided by the third party data provider, for example, the name of an organisation and the specific dataset provided by that organisation.

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

  • Nullable: true

  • Max Length: 65

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.0, 3.0, 4.0

numberoffloors

The maximum number of occupiable floors at or above ground level within a building.

  • Data Types: Integer (GeoJSON), Integer (GPKG), Integer (CSV)

  • Nullable: true

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 3.0, 4.0

numberoffloors_evidencedate

The date on which the latest evidence was gathered to make an update if required. For example, the date of collection by a surveyor or third party information received.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 3.0, 4.0

numberoffloors_updatedate

Date when the number of floors was last updated.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 3.0, 4.0

numberoffloors_source

Indicates the data source of the number of floors. For buildings with a populated number of floors value, this can be either 'Ordnance Survey' or 'Energy Performance Certificate Authority'.

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

  • Nullable: true

  • Max Length: 40

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 3.0, 4.0

numberoffloors_capturemethod

The capture method describes how the number of floors was created, for example, via remote sensing survey or via an automated process.

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

  • Nullable: true

  • Code List Name: capturemethodvalue

  • Max Length: 25

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 3.0, 4.0

height_absolutemin_m

The height, above datum, of the underlying ground surface.

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

  • Nullable: true

  • Precision: 5

  • Scale: 1

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 4.0

height_absoluteroofbase_m

The height, above datum, of the base of the roof, that is, where the roof intersects the building walls.

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

  • Nullable: true

  • Precision: 5

  • Scale: 1

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 4.0

height_absolutemax_m

The height, above datum, of the highest point of the building; this could include a chimney or other structure on a building.

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

  • Nullable: true

  • Precision: 5

  • Scale: 1

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 4.0

height_relativeroofbase_m

The difference in height between the intersection of the external building walls and the underlying ground surface and the base of the roof of the building.

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

  • Nullable: true

  • Precision: 4

  • Scale: 1

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 4.0

height_relativemax_m

The difference in height between the intersection of the external building walls and the underlying ground surface and the highest point on the building.

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

  • Nullable: true

  • Precision: 4

  • Scale: 1

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 4.0

height_confidencelevel

The confidence in the quality of the height attributes for the building expressed in qualitative terms.

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

  • Nullable: true

  • Code List Name: builtstructureheightconfidencevalue

  • Max Length: 15

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

height_evidencedate

The date on which the latest evidence was gathered to make an update if required. For example, the date the imagery was captured that has been used to derive the height information.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

height_updatedate

Date when the height was last updated.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

roofmaterial_primarymaterial

The primary roof material present on the building.

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

  • Nullable: true

  • Code List Name: roofmaterialvalue

  • Max Length: 35

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 4.0

roofmaterial_solarpanelpresence

Indicates if solar panels are present on the roof of the building.

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

  • Nullable: true

  • Code List Name: presencevalue

  • Max Length: 15

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 4.0

roofmaterial_greenroofpresence

Indicates if the roof of the building is at least partially covered with vegetation. This is usually specifically installed on a growing medium with a waterproof membrane, for environmental reasons.

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

  • Nullable: true

  • Code List Name: presencevalue

  • Max Length: 15

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 4.0

roofmaterial_confidenceindicator

An indication of whether the roof material output was expected, or if not, the reason why the quality may be lower.

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

  • Nullable: true

  • Code List Name: roofconfidenceindicatorvalue

  • Max Length: 50

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

roofmaterial_evidencedate

The date on which the latest evidence was gathered to make an update if required. For example, the date the imagery was captured that has been used to derive the roof material information.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

roofmaterial_updatedate

Date when the roof material was last updated.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

roofmaterial_capturemethod

The capture method describes how the roof material attributes were created, for example, via remote sensing survey or via an automated process.

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

  • Nullable: true

  • Code List Name: capturemethodvalue

  • Max Length: 25

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

roofshapeaspect_shape

An indication of the general shape characteristic of the roof of the building.

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

  • Nullable: true

  • Code List Name: roofshapevalue

  • Max Length: 10

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 4.0

roofshapeaspect_areapitched_m2

The sum of all roof face areas that have a pitch value of > 15°. Note that this measured area value is geometric (3D) rather than the planimetric (2D) measured area represented by geometry_area_m2.

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

  • Nullable: true

  • Precision: 7

  • Scale: 1

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

roofshapeaspect_areaflat_m2

The sum of all roof face areas that have a pitch value of <= 15°. Note that this measured area value is geometric (3D) rather than the planimetric (2D) measured area represented by geometry_area_m2.

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

  • Nullable: true

  • Precision: 7

  • Scale: 1

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

roofshapeaspect_areafacingnorth_m2

The sum of all roof face areas with an aspect >= 337.5° and < 360° or >= 0 and < 22.5°. Note that this measured area value is geometric (3D) rather than the planimetric (2D) measured area represented by geometry_area_m2.

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

  • Nullable: true

  • Precision: 7

  • Scale: 1

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

roofshapeaspect_areafacingnortheast_m2

The sum of all roof face areas with an aspect >= 22.5° and < 67.5°. Note that this measured area value is geometric (3D) rather than the planimetric (2D) measured area represented by geometry_area_m2.

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

  • Nullable: true

  • Precision: 7

  • Scale: 1

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

roofshapeaspect_areafacingeast_m2

The sum of all roof face areas with an aspect >= 67.5° and < 112.5°. Note that this measured area value is geometric (3D) rather than the planimetric (2D) measured area represented by geometry_area_m2.

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

  • Nullable: true

  • Precision: 7

  • Scale: 1

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

roofshapeaspect_areafacingsoutheast_m2

The sum of all roof face areas with an aspect >= 112.5° and < 157.5°. Note that this measured area value is geometric (3D) rather than the planimetric (2D) measured area represented by geometry_area_m2.

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

  • Nullable: true

  • Precision: 7

  • Scale: 1

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

roofshapeaspect_areafacingsouth_m2

The sum of all roof face areas with an aspect >= 157.5° and < 202.5°. Note that this measured area value is geometric (3D) rather than the planimetric (2D) measured area represented by geometry_area_m2.

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

  • Nullable: true

  • Precision: 7

  • Scale: 1

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

roofshapeaspect_areafacingsouthwest_m2

The sum of all roof face areas with an aspect >= 202.5° and < 247.5°. Note that this measured area value is geometric (3D) rather than the planimetric (2D) measured area represented by geometry_area_m2.

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

  • Nullable: true

  • Precision: 7

  • Scale: 1

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

roofshapeaspect_areafacingwest_m2

The sum of all roof face areas with an aspect >= 247.5° and < 292.5°. Note that this measured area value is geometric (3D) rather than the planimetric (2D) measured area represented by geometry_area_m2.

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

  • Nullable: true

  • Precision: 7

  • Scale: 1

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

roofshapeaspect_areafacingnorthwest_m2

The sum of all roof face areas with an aspect >= 292.5° and < 337.5°. Note that this measured area value is geometric (3D) rather than the planimetric (2D) measured area represented by geometry_area_m2.

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

  • Nullable: true

  • Precision: 7

  • Scale: 1

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

roofshapeaspect_areaindeterminable_m2

The sum of all roof face areas that have an indeterminable aspect. For example, areas obscured by vegetation or shadow, such as in an urban 'canyon'. Note that this measured area value is planimetric (2D) rather than geometric (3D), and is different to the other roofshapeaspect_area values.

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

  • Nullable: true

  • Precision: 7

  • Scale: 1

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

roofshapeaspect_areatotal_m2

The sum of all roof face areas, excluding those with indeterminable aspects. Note that this measure area value is a combination of geometric (3D) and planimetric (2D) area values because it is comprised of all known and unknown areas. Where the roofshapeaspect_areaindeterminable_m2 value is equal to 0, this value will be entirely a geometric (3D) area value.

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

  • Nullable: true

  • Precision: 7

  • Scale: 1

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

roofshapeaspect_confidenceindicator

An indication of whether the roof shape and aspect output was expected, or if not, the reason why the quality may be lower.

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

  • Nullable: true

  • Code List Name: roofconfidenceindicatorvalue

  • Max Length: 50

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

roofshapeaspect_evidencedate

The date on which the latest evidence was gathered to make an update if required. For example, the date the imagery was captured that has been used to derive the roof shape aspect information.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

roofshapeaspect_updatedate

Date when the roof shape aspect was last updated.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

roofshapeaspect_capturemethod

The capture method describes how the roof shape and aspect attributes were created, for example, via remote sensing survey or via an automated process.

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

  • Nullable: true

  • Code List Name: capturemethodvalue

  • Max Length: 25

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 4.0

Site Reference

A cross reference table mapping Building to Site. The following sub-sections provide details about the attributes included in this cross reference table, their data types in the different output formats, and other important metadata about them.

siteid

The identifier of the site the Building is within.

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

  • Nullable: false

  • Max Length: 36

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

buildingid

The identifier of the Building.

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

  • Nullable: false

  • Max Length: 36

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

buildingversiondate

The date this version of the feature entered the OS National Geographic Database.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

Building Part Reference

A cross reference table mapping Building to Building Part. The following sub-sections provide details about the attributes included in this cross reference table, their data types in the different output formats, and other important metadata about them.

buildingpartid

The identifier of the Building Part the Building is created from.

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

  • Nullable: false

  • Max Length: 36

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

buildingid

The identifier of the Building.

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

  • Nullable: false

  • Max Length: 36

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

buildingversiondate

The date this version of the feature entered the OS National Geographic Database.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

UPRN Reference

A cross reference table mapping Address to Building. The following sub-sections provide details about the attributes included in this cross reference table, their data types in the different output formats, and other important metadata about them.

uprn

The identifier of the addressable feature that is located within the Building.

  • Data Types: Number (GeoJSON), Integer (GPKG), Integer (CSV)

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

buildingid

The identifier of the Building.

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

  • Nullable: false

  • Max Length: 36

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

buildingversiondate

The date this version of the feature entered the OS National Geographic Database.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0, 2.0, 3.0, 4.0

Building Access Location

Feature which has a point geometry and represents the locations where pedestrians and / or vehicles can enter or exit a building.

Temporal filtering

The earliest date on which you can request a one-off snapshot of a date in the past for data in this feature type is 27 March 2025.

Any data temporally filtered earlier than the specified earliest date noted above for the data schema version may contain data inconsistencies.

Feature type attributes

The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

Loading OS NGD CSV files into databases

Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our OS NGD Resources GitHub repository.

For instructions on loading CSV files, see the Getting Started with CSV guide.

osid

Primary identifier for the feature. The OSID is a Globally Unique Identifier (GUID) and requires no centralised authority to ensure uniqueness. Note that the same OSID can occur in more than one feature type when a single feature is represented multiple times in the OS NGD.

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

  • Nullable: false

  • Max Length: 36

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

versiondate

Date when the version was last updated.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

versionavailabletodate

The date this version of the feature was superseded by an update or ceased to exist.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

versionavailablefromdate

The date this version of the feature became the latest version.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

changetype

The type of change that generated a new version of the feature.

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

  • Nullable: false

  • Code List Name: changetypevalue

  • Max Length: 50

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

geometry

Geometry for the feature.

  • Data Types: Geometry (GeoJSON), Geometry (GPKG), WKT (CSV)

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Geometry Type: Point

geometry_evidencedate

The date on which the latest evidence was gathered to make an update if required. For example, the date of a field visit or the date of imagery capture.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

geometry_updatedate

Date when the geometry was last updated.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

geometry_capturemethod

The capture method describes how the Building Access Location attributes were created, for example, via Field Survey.

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

  • Nullable: false

  • Code List Name: capturemethodvalue

  • Max Length: 25

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

theme

The OS NGD theme to which the feature belongs.

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

  • Nullable: false

  • Code List Name: themevalue

  • Max Length: 40

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

description

A single descriptive value intended for a quick understanding of what the feature represents.

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

  • Nullable: false

  • Code List Name: buildingaccesslocationdescriptionvalue

  • Max Length: 25

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

access_mode

A description of the method(s) of access normally utilised at the Building Access Location (for example, Pedestrian).

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

  • Nullable: false

  • Code List Name: accessmodevalue

  • Max Length: 25

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0

access_purpose

A description of the principal access function at the Building Access Location (for example, Private or Public).

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

  • Nullable: false

  • Code List Name: accesspurposevalue

  • Max Length: 15

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0

access_obstruction

An indicator of possible accessibility obstruction(s) at the Building Access Location (for example, Ramp or Step).

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

  • Nullable: false

  • Code List Name: accessobstructionvalue

  • Max Length: 20

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

access_level

An indicator of the relative location of the Building Access Location with respect to surface level upon approach to the Building Access Location (for example, Above Surface Level).

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

  • Nullable: false

  • Code List Name: accesslevelvalue

  • Max Length: 20

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0

access_evidencedate

The date on which the latest evidence was gathered to make an update if required. For example, the date of a field visit or the date of imagery capture.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

access_updatedate

Date when the access was last updated.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

accessedbuildingid

Identifier of the Building associated with the Building Access Location.

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

  • Nullable: true

  • Max Length: 36

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

Building Line

A feature which has a line geometry and represents a wall between two buildings, building internal divisions, or an overhanging building edge.

Temporal filtering

The earliest date on which you can request a one-off snapshot of a date in the past for data in this feature type is 29 September 2022.

Any data temporally filtered earlier than the specified earliest date noted above for the data schema version may contain data inconsistencies.

Feature type attributes

The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

Loading OS NGD CSV files into databases

Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our OS NGD Resources GitHub repository.

For instructions on loading CSV files, see the Getting Started with CSV guide.

osid

Primary identifier for the feature. The OSID is a Globally Unique Identifier (GUID) and requires no centralised authority to ensure uniqueness. Note that the same OSID can occur in more than one feature type when a single feature is represented multiple times in the OS NGD.

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

  • Nullable: false

  • Max Length: 36

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

toid

Topographic identifier (TOID) of the feature, as published in the OS MasterMap suite of products.

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

  • Nullable: true

  • Max Length: 20

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

versiondate

Date when the version was last updated.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

versionavailablefromdate

The date this version of the feature became the latest version.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

versionavailabletodate

The date this version of the feature was superseded by an update or ceased to exist.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

firstdigitalcapturedate

Represents the date on which a feature was first digitally captured by Ordnance Survey.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

changetype

The type of change that generated a new version of the feature.

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

  • Nullable: false

  • Code List Name: changetypevalue

  • Max Length: 50

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

geometry

Geometry for the feature.

  • Data Types: Geometry (GeoJSON), Geometry (GPKG), WKT (CSV)

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

  • Geometry Type: LineString

geometry_length

The measured length of the geometry in metres.

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

  • Nullable: false

  • Precision: 15

  • Scale: 6

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

geometry_evidencedate

The date on which the latest evidence was gathered to make an update if required. For example the date of collection by a surveyor or third party information received.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

geometry_updatedate

Date when the attribute was last updated.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

geometry_source

The source organisation who provided the data.

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

  • Nullable: false

  • Max Length: 50

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

theme

The OS NGD theme to which this feature belongs.

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

  • Nullable: false

  • Code List Name: themevalue

  • Max Length: 40

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

description

A single descriptive value intended for a quick understanding of what the feature represents.

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

  • Nullable: false

  • Code List Name: buildinglinedescriptionvalue

  • Max Length: 50

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.0

description_evidencedate

The date on which the latest evidence was gathered to make an update if required. For example the date of collection by a surveyor or third party information received.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

description_updatedate

Date when the attribute was last updated.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

description_source

The source organisation who provided the data.

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

  • Nullable: true

  • Max Length: 50

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

isobscured

An indicator that the feature is at ground level but lies below another feature represented in the data. For example a road with a bridge over it will have the attribute set to 'True'.

  • Data Types: Boolean (GeoJSON), Integer (GPKG), String (CSV)

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

physicallevel

The relative relationship of the feature to ground surface level, where ground surface level is the lowest identifiable level that is not underground.

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

  • Nullable: false

  • Code List Name: physicallevelvalue

  • Max Length: 15

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

capturespecification

Indicates the capture specification used by OS when capturing the feature. This could either be Urban, Rural or Moorland.

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

  • Nullable: false

  • Code List Name: capturespecificationvalue

  • Max Length: 10

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.0

Building Part

Polygon feature representing either a complete separate building, or part of a larger building where internal divisions exist from ground to roof level which can be identified externally. Examples of Building Part features include a multi-storey car park, a castle or a windmill.

Data schema versioning

The following table provides details about this feature type’s data schema versions, including the reasons behind the changes and the related launch date when each version went live.

Data schema version table

Version ↓
Launch Date
Latest Date
Change

2.2

17 July 2025

Ongoing

Minor version increment. Update to OS Land Cover Tier A attribute's max length from 15 to 20 and OS Land Cover Tier B attribute's max length from 25 to 20. New value (Under Construction) added to Building Part Land Cover Tier A Value and Building Part Land Cover Tier B Value Code Lists.

2.1

27 March 2025

16 July 2025

Minor version increment. Update to Status attribute length from 10 to 20 to allow for 'Under Construction'.

2.0

25 September 2024

26 March 2025

Major version increment adding new Land Use attribution, NLUD attribution and a cross-reference table to Site. New value added to the Building Part Description Value Code List for Building Under Construction.

1.1

17 July 2025

Ongoing

Minor version increment. Update to OS Land Cover Tier A attribute's max length from 15 to 20 and OS Land Cover Tier B attribute's max length from 25 to 20. New value (Under Construction) added to Building Part Land Cover Tier A Value and Building Part Land Cover Tier B Value Code Lists.

1.0

29 September 2022

16 July 2025

Initial launch of the Building Part Feature Type.

Please see Data schema versioning for in-depth information about data schema versioning in the OS NGD.

Temporal filtering

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 feature type'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 on OS NGD feature types is available from the Getting started with temporal filtering guide.

Feature type attributes

The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.

Loading OS NGD CSV files into databases

Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our OS NGD Resources GitHub repository.

For instructions on loading CSV files, see the Getting Started with CSV guide.

osid

Primary identifier for the feature. The OSID is a Globally Unique Identifier (GUID) and requires no centralised authority to ensure uniqueness. Note that the same OSID can occur in more than one feature type when a single feature is represented multiple times in the OS NGD.

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

  • Nullable: false

  • Max Length: 36

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

toid

Topographic identifier (TOID) of the feature, as published in the OS MasterMap suite of products.

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

  • Nullable: true

  • Max Length: 20

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

versiondate

Date when the version was last updated.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

versionavailablefromdate

The date this version of the feature became the latest version.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

versionavailabletodate

The date this version of the feature was superseded by an update or ceased to exist.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

firstdigitalcapturedate

Represents the date on which a feature was first digitally captured by Ordnance Survey.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

changetype

The type of change that generated a new version of the feature.

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

  • Nullable: false

  • Code List Name: changetypevalue

  • Max Length: 50

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

geometry

Geometry for the feature.

  • Data Types: Geometry (GeoJSON), Geometry (GPKG), WKT (CSV)

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

  • Geometry Type: Polygon

geometry_area_m2 (formerly geometry_area)

This attribute was called geometry_area in data schema version 1.0 and was renamed geometry_area_m2 from version 2.0 onward.

The measured area of the geometry in square metres.

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

  • Nullable: false

  • Precision: 15

  • Scale: 3

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

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

  • Nullable: false

  • Precision: 15

  • Scale: 6

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

geometry_evidencedate

The date on which the latest evidence was gathered to make an update if required. For example, the date of collection by a surveyor or third party information received.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

geometry_updatedate

Date when the attribute was last updated.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

geometry_source

The source organisation who provided the data.

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

  • Nullable: true

  • Max Length: 50

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

geometry_capturemethod

Indication of the method used to capture or produce the data.

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

  • Nullable: false

  • Code List Name: capturemethodvalue

  • Max Length: 25

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

theme

The OS NGD theme to which this feature belongs.

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

  • Nullable: false

  • Code List Name: themevalue

  • Max Length: 40

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

description

A single descriptive value intended for a quick understanding of what the feature represents.

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

  • Nullable: false

  • Code List Name: buildingpartdescriptionvalue

  • Code List version: 2.0

  • Max Length: 50

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.1, 2.2

description_evidencedate

The date on which the latest evidence was gathered to make an update if required. For example, the date of collection by a surveyor or third party information received.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

description_updatedate

Date when the attribute was last updated.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

description_source

The source organisation who provided the data.

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

  • Nullable: true

  • Max Length: 50

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

description_capturemethod

Indication of the method used to capture or produce the data.

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

  • Nullable: false

  • Code List Name: capturemethodvalue

  • Max Length: 25

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

oslandcovertiera

A high-level description of the land cover; more detail is provided in the OS Land Cover Tier B attribute.

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

  • Nullable: false

  • Code List Name: buildingpartlandcovertieravalue

  • Code List Version: 2.0

  • Max Length: 20

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

oslandcovertierb

A detailed description of the land cover type. Up to five distinct land cover types can be applied.

Note that in GPKG and CSV formats the array elements will be concatenated together into a comma-separated string. The max length specified below is the maximum length of 1 permissible value.

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

  • Nullable: false

  • Code List Name: buildingpartlandcovertierbvalue

  • Code List Version: 2.0

  • Max Length: 20

  • Multiplicity: [1..5]

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

oslandcover_evidencedate

The date on which the latest evidence was gathered to make an update if required. For example, the date of collection by a surveyor or third party information received.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

oslandcover_updatedate

Date when the attribute was last updated.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

oslandcover_source

The organisation that provided the information.

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

  • Nullable: true

  • Max Length: 50

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

oslandcover_capturemethod

Indication of the method used to capture or produce the data.

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

  • Nullable: false

  • Code List Name: capturemethodvalue

  • Max Length: 25

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

oslandusetiera

A high-level description of the main activity that takes place at the location or that the feature supports.

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

  • Nullable: false

  • Code List Name: landusetieravalue

  • Max Length: 50

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.1, 2.2

oslandusetierb

A detailed description of the main activity that takes place at the location or that the feature supports.

The max length specified below is the maximum length of 1 permissible value. This attribute can have up to 2 permissible values.

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

  • Nullable: true

  • Code List Name: landusetierbvalue

  • Max Length: 200

  • Multiplicity: [0..2]

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

oslanduse_evidencedate

The date on which the latest evidence was gathered to make an update if required. For example, the date of collection by a surveyor or third party information received.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

oslanduse_updatedate

Date when the attribute was last updated.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

oslanduse_source

The organisation that provided the information.

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

  • Nullable: true

  • Max Length: 50

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

oslanduse_capturemethod

Indication of the method used to capture or produce the data.

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

  • Nullable: false

  • Code List Name: capturemethodvalue

  • Max Length: 25

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

height_absoluteroofbase_m (formerly absoluteheightroofbase)

This attribute was called absoluteheightroofbase in data schema version 1.0 and was renamed height_absoluteroofbase_m from version 2.0 onward.

The height, above datum, of the base of the roof, that is, where the roof intersects the building walls.

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

  • Nullable: true

  • Precision: 5

  • Scale: 1

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

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

  • Nullable: true

  • Precision: 6

  • Scale: 2

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

height_relativeroofbase_m (formerly relativeheightroofbase)

This attribute was called relativeheightroofbase in data schema version 1.0 and was renamed height_relativeroofbase_m from version 2.0 onward.

The difference in height between the intersection of the external building walls and the underlying ground surface and the base of the roof of the building.

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

  • Nullable: true

  • Precision: 4

  • Scale: 1

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

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

  • Nullable: true

  • Precision: 6

  • Scale: 2

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

height_absolutemax_m (formerly absoluteheightmaximum)

This attribute was called absoluteheightmaximum in data schema version 1.0 and was renamed height_absolutemax_m from version 2.0 onward.

The height, above datum, of the highest point of the building; this could include a chimney or other structure on a building.

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

  • Nullable: true

  • Precision: 5

  • Scale: 1

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 2.2

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

  • Nullable: true

  • Precision: 6

  • Scale: 2

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.1

height_relativemax_m (formerly relativeheightmaximum)

This attribute was called relativeheightmaximum in data schema version 1.0 and was renamed height_relativemax_m from version 2.0 onward.

The difference in height between the intersection of the external building walls and the underlying ground surface and the highest point on the building.

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

  • Nullable: true

  • Precision: 4

  • Scale: 1

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

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

  • Nullable: true

  • Precision: 6

  • Scale: 2

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

height_absolutemin_m (formerly absoluteheightminimum)

This attribute was called absoluteheightminimum in data schema version 1.0 and was renamed height_absolutemin_m from version 2.0 onward.

The height, above datum, of the underlying ground surface.

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

  • Nullable: true

  • Precision: 5

  • Scale: 1

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 2.2

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

  • Nullable: true

  • Precision: 6

  • Scale: 2

  • OS NGD API – Features Filterable: Yes

  • OS Select+Build Filterable: Yes

  • Data Schema Version: 1.1

height_confidencelevel (formerly heightconfidencelevel )

This attribute was called heightconfidencelevel in data schema version 1.0 and was renamed height_confidencelevel from version 2.0 onward.

The confidence in the quality of the height attributes for the building or structure expressed in qualitative terms.

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

  • Nullable: true

  • Code List Name: builtstructureheightconfidencevalue

  • Max Length: 15

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

height_evidencedate

The date on which the latest evidence was gathered to make an update if required. For example, the date of collection by a surveyor or third party information received.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

height_updatedate

Date when the attribute was last updated.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

height_source

The organisation that provided the information.

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

  • Nullable: true

  • Max Length: 50

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1

associatedstructure

Indicates whether the feature is part of a larger structure and the nature of the structure, for example, a dam, bridge or breakwater.

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

  • Nullable: true

  • Code List Name: compoundstructuredescriptionvalue

  • Code List Version: 1.0

  • Max Length: 25

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

isobscured

An indicator that the feature is at ground level but lies below another feature represented in the data. For example, a road with a bridge over it will have the attribute set to 'True'.

  • Data Types: Boolean (GeoJSON), Integer (GPKG), String (CSV)

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

physicallevel

The relative relationship of the feature to ground surface level, where ground surface level is the lowest identifiable level that is not underground.

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

  • Nullable: false

  • Code List Name: physicallevelvalue

  • Max Length: 15

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

capturespecification

Indicates the capture specification used by OS when capturing the feature. This could either be Urban, Rural or Moorland.

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

  • Nullable: false

  • Code List Name: capturespecificationvalue

  • Max Length: 10

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 1.1, 2.2

containingsitecount

A count of the number of Land Use Sites the feature lies within.

  • Data Types: Integer (GeoJSON), Integer (GPKG), Integer (CSV)

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

smallestsite_siteid

The identifier of the smallest Land Use Site feature that the topographic area feature lies within.

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

  • Nullable: true

  • Max Length: 36

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

smallestsite_landusetiera

A high-level description of the main activity that takes place at the location of the smallest Land Use Site feature the feature lies within, if any.

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

  • Nullable: true

  • Code List Name: oslandusetieravalue

  • Max Length: 50

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

smallestsite_landusetierb

A more detailed description of the main activity that takes place at the location of the smallest Land Use Site feature the feature lies within, if any.

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

  • Nullable: true

  • Code List Name: oslandusetierbvalue

  • Max Length: 200

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

largestsite_landusetiera

A high-level description of the main activity that takes place at the location of the largest Land Use Site feature the feature lies within, if any.

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

  • Nullable: true

  • Code List Name: oslandusetieravalue

  • Max Length: 50

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

largestsite_landusetierb

A more detailed description of the main activity that takes place at the location of the largest Land Use Site feature the feature lies within, if any.

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

  • Nullable: true

  • Code List Name: oslandusetierbvalue

  • Max Length: 200

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

nlud_code

An alternative land use classification that uses a code defined in the National Land Use Database schema. Populated in the first instance from the land use of the largest Land Use Site (if any) that the feature lies within, and if that does not apply, then by any land use implicit in the nature of the feature itself.

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

  • Nullable: true

  • Max Length: 4

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

nlud_orderdescription

A description of the highest (least detailed) level of an alternative land use classification as defined in the National Land Use Database schema. Populated in the first instance from the land use of the largest Land Use Site (if any) that the feature lies within, and if that does not apply, then by any land use implicit in the nature of the feature itself.

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

  • Nullable: true

  • Max Length: 30

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

nlud_groupdescription

A description of the second level of an alternative land use classification as defined in the National Land Use Database schema. Populated in the first instance from the land use of the largest Land Use Site (if any) that the feature lies within, and if that does not apply, then by any land use implicit in the nature of the feature itself.

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

  • Nullable: true

  • Max Length: 40

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

address_classificationcode

An alternative land use classification that uses a code defined in the Address/BS7666 schema. Populated only where local authority address information lies within a Land Use Site that the feature also falls within. The value is derived by analysis of the attribution of Address information that falls within the extent of the smallest Land Use Site that the feature lies within. Where the address information within the extent of the Site contains differing primary level classifications, then no Address Code value is provided.

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

  • Nullable: true

  • Max Length: 2

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

address_primarydescription

The description of the highest (least detailed) level of an alternative land use classification as defined in the Address/BS7666 schema. Populated only where local authority address information lies within a Land Use Site that the feature also falls within. The value is derived by analysis of the attribution of Address information that falls within the extent of the smallest Land Use Site that the feature lies within. Where the address information within the extent of the Site contains differing primary level classifications, then a value of ‘Mixed’ is applied.

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

  • Nullable: true

  • Max Length: 120

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

address_secondarydescription

The description of the second level of an alternative land use classification as defined in the Address/BS7666 schema. Populated only where local authority address information lies within a Land Use Site that the feature also falls within. The value is derived by analysis of the attribution of Address information that falls within the extent of the smallest Land Use Site that the feature lies within. Where the address information within the extent of the Site contains differing secondary level classifications, then no value is provided.

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

  • Nullable: true

  • Max Length: 120

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

lowertierlocalauthority_gsscode

The unique identifier of the Lower Tier Local Authority administrative area provided by the Office for National Statistics that the Topographic feature lies within. Where a Topographic area falls into more than one Lower Tier Local Authority, then it will be assigned to the Lower Tier Local Authority that the majority of its area lies within. Where a Topographic area falls outside any Lower Tier Local Authority (for example, an offshore feature), then no code will be provided.

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

  • Nullable: true

  • Max Length: 10

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

lowertierlocalauthority_count

The total number of Lower Tier Local Authority administrative areas the feature lies within. Where a feature falls within more than one LTLA and the resultant subdivided areas are either less than 10% of original total area or are less than 2 square metres in area then the count excludes these smaller subdivided areas from the value provided.

  • Data Types: Integer (GeoJSON), Integer (GPKG), Integer (CSV)

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

status

The state of the feature in relation to either its physical condition or the activity the feature is intended to support.

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

  • Nullable: true

  • Code List Name: statusvalue

  • Max Length: 20

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

status_updatedate

Date when the attribute was last updated.

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

  • Nullable: true

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

Site Reference

A cross reference table mapping Building Part to Site. The following sub-sections provide details about the attributes included in this cross reference table, their data types in the different output formats, and other important metadata about them.

siteid

The identifier for the Site feature.

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

  • Nullable: false

  • Max Length: 36

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

buildingpartid

The identifier for the Building Part feature.

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

  • Nullable: false

  • Max Length: 36

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2

buildingpartversiondate

The date this version of the feature entered the OS National Geographic Database.

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

  • Nullable: false

  • OS NGD API – Features Filterable: No

  • OS Select+Build Filterable: No

  • Data Schema Version: 2.2