> 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/code-lists/code-lists-overview/capturespecificationvalue.md).

# capturespecificationvalue

This code list is used in association with the Capture Specification attribute which is present within multiple OS NGD feature types across various OS NGD themes. The code list indicates the expected positional accuracy of the base survey and provides information on the guidelines applied regarding the depiction of building juts, parallel features, vegetation and surface cover area representation, and so on, in the area where the feature is located. These are the minimum standards, and some features may be captured to a higher standard.

| Label    | Definition                                                                                                                                                                                                                                                                                                                                                                                                                                   |
| -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Moorland | The core data that the feature has been based upon was captured to an expected positional accuracy of 4.1m RMSE. In addition, this defines the guidelines that were applied regarding the depiction of building juts, parallel features, vegetation, and surface cover area representation, and so on; these are outlined in the NGD user documentation. These are minimum standards and some features may be captured to a higher standard. |
| Rural    | The core data that the feature has been based upon was captured to an expected positional accuracy of 1.1m RMSE. In addition, this defines the guidelines that were applied regarding the depiction of building juts, parallel features, vegetation, and surface cover area representation, and so on; these are outlined in the NGD user documentation. These are minimum standards and some features may be captured to a higher standard. |
| Urban    | The core data that the feature has been based upon was captured to an expected positional accuracy of 0.5m RMSE. In addition, this defines the guidelines that were applied regarding depiction of building juts, parallel features, vegetation, and surface cover area representation, and so on; these are outlined in the NGD user documentation. These are minimum standards and some features may be captured to a higher standard.     |


---

# 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/code-lists/code-lists-overview/capturespecificationvalue.md?ask=<question>&goal=<user_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.