> 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/known-limitations.md).
# Known limitations
Manual land cover classification is subjective and in the natural environment, features change over time, for example scrub becomes trees. OS carries out a flying programme each year, capturing each area of Great Britain at least once every three years. The aerial imagery derived from this capture programme can be impacted by seasonal variances, i.e. the time of year when the area was flown over, or even the time of day. Earlier in the year vegetated features may be captured with leaf-off, long shadows may impact the feature’s classification, or during a dry summer an area of marsh may look like rough grassland.
Additionally, the automated machine learning classification to derive the percentage cover value uses aerial imagery as a top-down view so some features on the ground may have their true nature obscured by overhanging trees.
The automated classification of some feature types is of lower confidence and therefore the percentage cover value for these features may be of lower quality, i.e. ‘Saltmarsh’, ‘Heath’, ‘Rough Grassland’.
---
# 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/known-limitations.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.