> For the complete documentation index, see [llms.txt](https://docs.os.uk/os-downloads/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/os-downloads/~/changes/AJZwzCsyrD9hiTbOxIbO/networks/os-mastermap-highways-network-roads/os-mastermap-highways-network-roads-technical-specification/code-lists-and-enumerations/provenancesourcevalue.md).

# ProvenanceSourceValue

The RoadLink and Street feature is attributed with a ‘provenance’ property with the data type of ProvenanceSourceValue. The following table describes the codes used to populate this field.

## **Code List: ProvenanceSourceValue**

{% embed url="<https://www.ordnancesurvey.co.uk/xml/codelists/highways/ProvenanceSourceValue.xml>" %}

| Code                                     | Description                                                                                                                             |
| ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| Highways England                         | The source for the geometry of the feature is Highways England.                                                                         |
| Local Highway Authority                  | The source for the geometry of the feature is Local Highways Authority.                                                                 |
| Ordnance Survey                          | The source for the geometry of the feature is Ordnance Survey.                                                                          |
| Transport Scotland                       | The source for the geometry of the feature is Transport Scotland.                                                                       |
| Welsh Government                         | The source for the geometry of the feature is Welsh Government.                                                                         |
| OS Urban And OS Height                   | Data captured to 0.5m planimetric accuracy and elevation obtained from drape of OS detailed height content.                             |
| OS Rural And OS Height                   | Data captured to 1.1 planimetric accuracy and elevation obtained from drape of OS detailed height content.                              |
| OS Moorland And OS Height                | Data captured to 4.1m planimetric accuracy and elevation obtained from drape of OS detailed height content.                             |
| OS Urban And Interpolated OS Height      | Data captured to 0.5m planimetric accuracy and elevation interpolated from OS detailed height content and other OS data.                |
| OS Rural And Interpolated OS Height      | Data captured to 1.1m planimetric accuracy and elevation interpolated from OS detailed height content and other OS data.                |
| OS Moorland And Interpolated OS Height   | Data captured to 4.1m planimetric accuracy and elevation interpolated from OS detailed height content and other OS data.                |
| OS Urban And Low Confidence OS Height    | Data captured to 0.5m planimetric accuracy, elevation obtained from drape of OS detailed height content but expected to be low quality. |
| OS Rural And Low Confidence OS Height    | Data captured to 1.1m planimetric accuracy, elevation obtained from drape of OS detailed height content but expected to be low quality. |
| OS Moorland And Low Confidence OS Height | Data captured to 4.1m planimetric accuracy, elevation obtained from drape of OS detailed height content but expected to be low quality. |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.os.uk/os-downloads/~/changes/AJZwzCsyrD9hiTbOxIbO/networks/os-mastermap-highways-network-roads/os-mastermap-highways-network-roads-technical-specification/code-lists-and-enumerations/provenancesourcevalue.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.