> 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/land-and-terrain-portfolio/os-open-greenspace/os-open-greenspace-technical-specification/vector-tiles-overview.md).

# Vector tiles overview

OS Open Greenspace is provided in MBTiles, which is an open specification tileset format used for vector tiles. The format is designed to be simple, high resolution, customisable and efficient to load as a single file. The data is supplied in Web Mercator projection (ESPG:3857).

## Vector tiles schema <a href="#bookmark26" id="bookmark26"></a>

The vector tiles schema, as well as the zoom level for each attribute, is detailed in the following table:

{% hint style="info" %}
*In the Zoom levels columns, 'N' (no) indicates that the specified layer and attribute does not display within that zoom level, whereas 'Y' (yes) indicates that the specified layer and attribute does display within that zoom level*.
{% endhint %}

### Greenspace Site

#### Attributes:

* id
* function
* distinctive\_name\_1
* distinctive\_name\_2
* distinctive\_name\_3
* distinctive\_name\_4

<table data-full-width="true"><thead><tr><th width="343">Feature types</th><th width="197">Zoom levels: 0 to 8</th><th width="71">9</th><th width="72">10</th><th width="72">11</th><th width="73">12</th><th width="65">13</th><th>14</th></tr></thead><tbody><tr><td>Allotments Or Community Growing Spaces</td><td>N</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td></tr><tr><td>Bowling Green</td><td>N</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td></tr><tr><td>Cemetery</td><td>N</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td></tr><tr><td>Golf Course</td><td>N</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td></tr><tr><td>Other Sports Facility</td><td>N</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td></tr><tr><td>Play Space</td><td>N</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td></tr><tr><td>Playing Field</td><td>N</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td></tr><tr><td>Public Park Or Garden</td><td>N</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td></tr><tr><td>Religious Grounds</td><td>N</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td></tr><tr><td>Tennis Court</td><td>N</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td></tr></tbody></table>

### Access Point

#### Attributes:

* id
* access\_type

<table data-full-width="true"><thead><tr><th width="179">Feature types</th><th width="185">Zoom levels: 0 to 8</th><th width="59">9</th><th width="57">10</th><th width="52">11</th><th width="53">12</th><th width="63">13</th><th>14</th></tr></thead><tbody><tr><td>Motor Vehicle</td><td>N</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td></tr><tr><td>Motor Vehicle and Pedestrian</td><td>N</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td></tr><tr><td>Pedestrian</td><td>N</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td><td>Y</td></tr></tbody></table>


---

# 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/land-and-terrain-portfolio/os-open-greenspace/os-open-greenspace-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.