> For the complete documentation index, see [llms.txt](https://docs.os.uk/osngd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.os.uk/osngd/using-os-ngd-data/os-ngd-land-use/understanding-land-use-in-the-os-ngd/land-use-classifications.md). # Land use classifications ## OS land use values The [Site](/osngd/data-structure/land-use/land-use-features/site.md), [Building Part](/osngd/data-structure/buildings/building-features/building-part.md), [Land](/osngd/data-structure/land/land-features/land.md), [Rail](/osngd/data-structure/transport/transport-features/rail.md), [Road Track Or Path](/osngd/data-structure/transport/transport-features/road-track-or-path.md), [Structure](/osngd/data-structure/structures/structure-features/structure.md) and [Water](/osngd/data-structure/water/water-features/water.md) features use the same hierarchical classification of land use: * [Land Use Tier A](/osngd/code-lists/code-lists-overview/landusetieravalue.md) – A high-level description of the land use, where known. * [Land Use Tier B](/osngd/code-lists/code-lists-overview/landusetierbvalue.md) – A detailed description of the land use, where known. Specific Land Use Tier B values will always fall under the same Land Use Tier A value. A more detailed land use can often be inferred from the [Description attribute](/osngd/data-structure/land-use/land-use-features/site.md#description) used by each feature type, but these vary in their granularity and consistency of population, and are not intended for analytical use. A table showing how individual Site Description values have been mapped to OS Land Use Tier A and OS Land Use Tier B values is available on the [Hierarchy of land use classification values in the OS NGD](/osngd/using-os-ngd-data/os-ngd-land-use/understanding-land-use-in-the-os-ngd/hierarchy-of-land-use-classification-values-in-the-os-ngd.md#table-mapping-site-description-values-to-os-land-use-tier-a-and-os-land-use-tier-b-values) page Hierarchies of land use classification values can also be found on the [Hierarchy of land use classification values in the OS NGD](/osngd/using-os-ngd-data/os-ngd-land-use/understanding-land-use-in-the-os-ngd/hierarchy-of-land-use-classification-values-in-the-os-ngd.md#table-mapping-os-land-use-tier-a-values-to-os-land-use-tier-a-values) page. ## Unknown land use Where a Site feature is evident to OS but the specific land use cannot be determined or has no obvious current use, the value 'Unknown Use' is populated in the [Land Use Tier A attribution](/osngd/code-lists/code-lists-overview/landusetieravalue.md). For [Building Part](/osngd/data-structure/buildings/building-features/building-part.md), [Land](/osngd/data-structure/land/land-features/land.md), [Rail](/osngd/data-structure/transport/transport-features/rail.md), [Road Track Or Path](/osngd/data-structure/transport/transport-features/road-track-or-path.md), [Structure](/osngd/data-structure/structures/structure-features/structure.md) or [Water](/osngd/data-structure/water/water-features/water.md) features where OS cannot determine a land use, the values of 'Unknown Or Unused Artificial' or 'Unknown Or Unused Manmade' are applied to Land Use Tier A attribution – this includes an element of the land cover attribution to provide some context. ## Multiple land uses at a Site At some locations, there can be multiple activities taking place on a Site where none are clearly dominant (for example, a Site with a shop on the ground floor and a residential flat above). In cases like this, the [Site](/osngd/data-structure/land-use/land-use-features/site.md) feature is given a[ Description](/osngd/code-lists/code-lists-overview/sitedescriptionvalue.md) attribute value of ‘Mixed Use Site’ and a [Land Use Tier A](/osngd/code-lists/code-lists-overview/landusetieravalue.md) attribute value of 'Mixed Use'. At such locations, the summary of local authority address information provided as Site attribution can be used to better understand the types of activities occurring at the Site. ## National Land Use Database The [National Land Use Database](https://www.gov.uk/government/statistics/national-land-use-database-land-use-and-land-cover-classification) (NLUD) is a classification developed by central government to establish a national system for describing land use (and land cover). To provide a dataset that speaks to this standard, the land use values captured by OS are also mapped to the NLUD values defined in the [NLUD specification](https://assets.publishing.service.gov.uk/media/5a78b635ed915d07d35b1d52/144275.pdf) (see the [Mapping from Site description values to NLUD values](/osngd/using-os-ngd-data/os-ngd-land-use/understanding-land-use-in-the-os-ngd/mapping-from-site-description-values-to-nlud-values.md) page for a table mapping the values). This is provided as additional attribution against Site features: * [NLUD Code](/osngd/data-structure/land-use/land-use-features/site.md#newnlud_code) * [NLUD Order Description](/osngd/data-structure/land-use/land-use-features/site.md#newnlud_orderdescription) * [NLUD Group Description](/osngd/data-structure/land-use/land-use-features/site.md#newnlud_groupdescription) The mapping uses the most precise information that OS has collected, including the Description attribution, the OS Land Use Tier A attribution and OS Land Use Tier B attribution. As such, there is not a simple 1:1 correlation between OS land use values and NLUD values. Where an NLUD value is provided, the value may only be at the highest level of the hierarchical classification. Where OS does not have enough information, the NLUD values will not be provided, although this is rare. ### NLUD values for Sites NLUD values for [Site](/osngd/data-structure/land-use/land-use-features/site.md) features are assigned from the most precise information OS has captured. A mapping from the Description attribute used by the Site Feature Type to the NLUD value is provided in the table on the [Mapping from Site Description values to NLUD values](/osngd/using-os-ngd-data/os-ngd-land-use/understanding-land-use-in-the-os-ngd/mapping-from-site-description-values-to-nlud-values.md) page. Where there is not a recognised mapping from OS information to the NLUD, then no NLUD value is provided – for example, 'Mixed Use' and 'Unknown Use' are not recorded in the NLUD. Outside of these examples, almost all Site features have an NLUD equivalent. ### NLUD values for topographic areas NLUD values are also added to the topographic areas within a Site as attribution on their polygons. The following ruleset is used: * Where a [Building Part](/osngd/data-structure/buildings/building-features/building-part.md), [Land](/osngd/data-structure/land/land-features/land.md), [Rail](/osngd/data-structure/transport/transport-features/rail.md), [Road Track Or Path](/osngd/data-structure/transport/transport-features/road-track-or-path.md), [Structure](/osngd/data-structure/structures/structure-features/structure.md) or [Water](/osngd/data-structure/water/water-features/water.md) feature lies within one [Site](/osngd/data-structure/land-use/land-use-features/site.md) feature and that Site feature has a mapped NLUD value, then the NLUD value of the Site feature is assigned. * Where a Building Part, Land, Rail, Road Track Or Path, Structure or Water feature lies within more than one Site feature that has a mapped NLUD value, then the NLUD value of the largest Site feature (only) is assigned. * Where a Building Part, Land, Rail, Road Track Or Path, Structure or Water feature does not lie within a Site feature, then an NLUD value may be assigned if it can be inferred from the attribution on the feature – for example, a road carriageway or land identified as part of the railway curtilage. This includes features such as natural 'Boulders', 'Non-Coniferous Trees' or 'Rock' that, unless they lie within a Site feature, have been given an NLUD value of 'U130 - Unused Land'. * Building Part, Land, Rail, Road Track Or Path, Structure or Water features that do not fall into the NLUD categories are not given an NLUD value; these represent less than 5% of the total area of Great Britain. ## Populating land use values on topographic areas Land use values are recorded for individual [Building Part](/osngd/data-structure/buildings/building-features/building-part.md), [Land](/osngd/data-structure/land/land-features/land.md), [Rail](/osngd/data-structure/transport/transport-features/rail.md), [Road Track Or Path](/osngd/data-structure/transport/transport-features/road-track-or-path.md), [Structure](/osngd/data-structure/structures/structure-features/structure.md) or [Water](/osngd/data-structure/water/water-features/water.md) features using the following methods: * **The nature of the feature itself suggests its land use** – For example, a road carriageway or an agricultural field. * **The land use of the Site feature the feature lies within** – For example, an area of grass within a school 'inherits' a land use from the [Site](/osngd/data-structure/land-use/land-use-features/site.md) feature for the school. Up to three land use values may be recorded against a single Building Part, Land, Rail, Road Track Or Path, Structure or Water feature, though this is not a common occurrence. The following sub-section on Topographic areas with multiple uses describes the process. ### Topographic areas with multiple uses Where [Building Part](/osngd/data-structure/buildings/building-features/building-part.md), [Land](/osngd/data-structure/land/land-features/land.md), [Rail](/osngd/data-structure/transport/transport-features/rail.md), [Road Track Or Path](/osngd/data-structure/transport/transport-features/road-track-or-path.md), [Structure](/osngd/data-structure/structures/structure-features/structure.md) or [Water](/osngd/data-structure/water/water-features/water.md) features lie within more than one Site feature and / or by their nature they have an inherent land use (for example, a road), up to three land use values can be provided, including the land use of both the smallest Site feature and the largest Site feature (where applicable). Typical examples of this occur in extensive locations (such as hospitals or universities) containing smaller sites (such as utilities or communal accommodation), as well as roads or paths. The following table outlines the derivation process for each piece of land use attribution for the six feature types: | Land Use Attribution for Building Part, Land, Rail, Road Track Or Path, Structure and Water features | Derivation | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |

OS Land Use Tier A

Note: This value will always be populated and is the ‘simplest’ single attribute way to identify OS land use if the nuances of multiple land uses are not required.

|

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

| |

OS Land Use Tier B

Note: This value will only be populated where there more detailed information about land use is available.

|

A more detailed description of the main activity that takes place at the location.

| |

Smallest Site Land Use Tier A

Note: This value will only be populated where a feature lies within a Site feature – the value may be the same as that provided in OS Land Use Tier A if that attribute has been populated from the Site classification.

|

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

| |

Smallest Site Land Use Tier B

Note: This value will only be populated where a feature lies within a Site feature – the value may be the same as that provided in OS Land Use Tier B if that attribute has been populated from the Site classification

|

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

| |

Largest Site Land Use Tier A

Note: This value will only be populated where a feature lies within more than one Site feature. The value may be the same as that provided in Smallest Site Land Use Tier A if both Site features are performing the same function (for example, separate units providing medical care within an overall hospital site).

|

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

| |

Largest Site Land Use Tier B

Note: This value will only be populated where a feature lies within more than one Site feature. The value may be the same as that provided in Smallest Site Land Use Tier B if both Site features are performing the same function (for example, separate units providing medical care within an overall hospital site).

|

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

| | [Containing Site Count](/osngd/data-structure/land/land-features/land.md#newcontainingsitecount) | A count of the number of Site features the feature lies within. This attribute may be useful for the extremely rare cases where a feature lies within two or more Site features. If this is important to a use case, then the Site Reference cross-reference table may be required. | ## Capture and maintenance OS has been capturing land use information from its earliest map publications, typically as cartographic text that provides context to a map (for example, a church or school). Over the last 20 years, OS has gradually increased the scope and detail of land use information provided in premium data, made possible through increasing digitisation of data. Consequently, OS land use data has a mixed lineage, including derivation from original textual descriptions, inference from expert interpretation of both imagery and existing topographic features, and the use of open government sources. Land use values continue to be captured and maintained using remote sensing, field surveying and desk-based data analysis, in conjunction with authoritative third-party data. Information about when updates were made to land use values assigned to Site, Building Part, Land, Rail, Road Track Or Path, Structure and Water features are provided through the following attribution: * [OS Land Use Evidence Date](/osngd/data-structure/land-use/land-use-features/site.md#oslanduse_evidencedate) * [OS Land Use Update Date](/osngd/data-structure/land-use/land-use-features/site.md#oslanduse_updatedate) * [OS Land Use Source](/osngd/data-structure/land-use/land-use-features/site.md#oslanduse_source) * [OS Land Use Capture Method](/osngd/data-structure/land-use/land-use-features/site.md#newoslanduse_capturemethod) ## Maintenance cycles Land use data is maintained using the following techniques that OS uses to identify change: * **Continuous revision** – Updates are triggered by various sources of change intelligence using sources such as amended local authority address information. For example, new roads and houses. * **Land use updates where there is limited, or no, geometry changes** – These are predominantly identified by changes to local authority address information. These changes are reviewed and data is updated as appropriate. * **Cyclic revision** – Updates are triggered by change detection on aerial imagery flown and captured at regular intervals. These are typically changes such as watercourse alignments, agricultural buildings, or forestry. * **Data improvement** – Updates are triggered by user demand to improve the consistency of specific elements, for example, a more refined classification of specific types of commercial activity. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.os.uk/osngd/using-os-ngd-data/os-ngd-land-use/understanding-land-use-in-the-os-ngd/land-use-classifications.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.