> 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-cover-enhancements/habitat-mapping.md). # Habitat mapping Natural topographic area features are mapped to: * EUNIS habitat type hierarchical view (marine version 2022 & terrestrial version 2021) using Level 1 and Level 2 classification * UK BAP Broad Habitats classification 2008 A simple algorithm automatically maps the OS Land Cover Tier B attribute of natural topographic area features to EUNIS and UK BAP classification scheme values using a lookup table prior to product publication. These are output into the Habitat Coverage Reference table. Mapping the OS land cover classification to EUNIS Level 1 is mandatory. For EUNIS Level 2 and UK BAP it is not always possible to achieve a direct mapping as habitat classifications can be species-based, making it difficult to derive from a land cover classification. In such instances, there will be no entry for these records in the Habitat Coverage Reference table. Coastal features also receive a habitat mapping. Coastal features are defined as being within the intertidal zone +200metre buffer above the Mean High Water (Springs) Line. --- # 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-cover-enhancements/habitat-mapping.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.