> 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/products/water-portfolio/os-open-rivers/os-open-rivers-technical-specification/vector-tiles-overview.md).

# Vector tiles overview

OS Open Rivers is supplied as a national vector tile set in a single MBTiles file. This is a lightweight set of tiles that is efficient and fast to render in your software, provides high-resolution data and a seamless experience when zooming in and out. The data is supplied in Web Mercator projection (ESPG:3857).

The vector tiles schema as well as the zoom level for each attribute is detailed on the [Vector tiles schema page](/os-downloads/products/water-portfolio/os-open-rivers/os-open-rivers-technical-specification/vector-tiles-overview/vector-tiles-schema.md).

## Attribute mapping <a href="#id-6.2-attribute-mapping" id="id-6.2-attribute-mapping"></a>

The naming of attributes between vector tiles and GML is very similar as the vector tiles (set within the MBTiles file) do not limit in the number of characters for attribute names. The tables in the following pages map the GML attribute name its vector tiles equivalent for the WatercourseLink and HydroNode features:

* [WatercourseLink](/os-downloads/products/water-portfolio/os-open-rivers/os-open-rivers-technical-specification/vector-tiles-overview/watercourselink.md)
* [HydroNode](/os-downloads/products/water-portfolio/os-open-rivers/os-open-rivers-technical-specification/vector-tiles-overview/hydronode.md)

{% hint style="info" %}
The use of an asterisk symbol (\*) in the tables indicates that a particular attribute is not mapped in that format (for example, the fictitious attribute has no vector tile equivalent).
{% endhint %}


---

# 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/os-downloads/products/water-portfolio/os-open-rivers/os-open-rivers-technical-specification/vector-tiles-overview.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.