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.
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.
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.
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:
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:
The new 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 this attribute can be visualised is shown in the image below:
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.
Great Britain.
British National Grid (EPSG: 27700).
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.
GeoPackage, CSV (comma-separated values), GeoJSON or vector tiles (the latter format is only available for one feature type in the collection: Building Part).
Accessed through the OS Data Hub via:
OS Select+Build
OS NGD API – Features
OS NGD API – Tiles (only available for one feature type in the collection: Building Part)
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.
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 parts, enabling users to create simple height models.
In comparison to existing OS data, the 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)
The OS NGD Buildings Theme is made up of the OS NGD Building Features Collection, which in turn is comprised of Building Line, Building Part, and Building Feature Types.
Two unique identifiers are provided with each feature within the OS NGD Buildings Theme:
OSID (Ordnance Survey Identifier): The primary identifier and unique key for this theme.
TOID (Topographic Identifier): 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.
A feature which has a line geometry and represents a wall between two buildings, building internal divisions, or an overhanging building edge.
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.
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.
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
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
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
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
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
Represents the date on which a feature was first digitised 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
The type of change that generated a new version of the feature.
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
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
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
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
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
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
The OS NGD theme to which this feature belongs.
Data Types: Array (GeoJSON), String (GPKG), String (CSV)
Nullable: false
Max Length: 40
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.0
A single descriptive value intended for a quick understanding of what the feature represents.
Data Types: String (GeoJSON), String (GPKG), String (CSV)
Nullable: false
Max Length: 50
OS NGD API – Features Filterable: Yes
OS Select+Build Filterable: Yes
Data Schema Version: 1.0
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
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
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
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
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
Max Length: 15
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.0
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
Max Length: 10
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.0
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.
The earliest and latest dates on which you can request a one-off snapshot of a date in the past for the data schema versions available for this feature type are detailed in the following table:
| Data schema version | Earliest date | Latest date |
|---|---|---|
Please see Data schema versioning for more information about versioning in the OS NGD Buildings Theme.
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.
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
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, 2.0
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
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
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
Represents the date on which a feature was first digitised 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, 2.0
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,
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
Geometry Type: Polygon
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.0
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
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, 2.0
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
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
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.0
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, 2.0
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
Max Length: 50
OS NGD API – Features Filterable: Yes
OS Select+Build Filterable: Yes
Data Schema Version: 1.0, 2.0
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, 2.0
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
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
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.0
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: buildingpartoslandcovertieravalue
Max Length: 15
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
A detailed description of the land cover type. Up to five distinct land cover types can be applied.
The max length specified below is the maximum length of 1 permissible value. This attribute can have up to 5 permissible values.
Data Types: Array (GeoJSON), String (GPKG), String (CSV)
Nullable: false
Code List Name: buildingpartoslandcovertierbvalue
Max Length: 25
Multiplicity: [1..5]
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
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, 2.0
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
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.0
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.0
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: oslandusetieravalue
Max Length: 50
OS NGD API – Features Filterable: Yes
OS Select+Build Filterable: Yes
Data Schema Version: 1.0, 2.0
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: oslandusetierbvalue
Max Length: 200
Multiplicity: [0..2]
OS NGD API – Features Filterable: Yes
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
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, 2.0
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
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.0
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.0
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.0
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.0
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.0
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.0
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.0
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.0
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.0
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.0
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.0
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.0
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.0, 2.0
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, 2.0
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.0, 2.0
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.0
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
Max Length: 25
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
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, 2.0
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, 2.0
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, 2.0
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.0
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.0
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.0
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.0
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.0
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.0
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.0
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.0
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.0
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.0
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.0
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.0
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.0
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.0
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.0
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.0
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.
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.0
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.0
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.0
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.
The earliest and latest dates on which you can request a one-off snapshot of a date in the past for the data schema versions available for this feature type are detailed in the following table:
| Data schema version | Earliest date | Latest date |
|---|---|---|
Please see Data schema versioning for more information about versioning in the OS NGD Buildings Theme.
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.
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
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
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
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
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
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
Geometry Type: Polygon
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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.
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
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
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
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.
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
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
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
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.
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
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
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
Code List Name:
Code List Name:
Code List Name:
Code List Name:
Code List Name:
1.0
29 September 2022
Ongoing
2.0
25 September 2024
Ongoing
1.0
27 September 2023
Ongoing
2.0
27 March 2024
Ongoing
3.0
25 September 2024
Ongoing
