> 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-mastermap-greenspace-layer/os-mastermap-greenspace-layer-getting-started-guide/loading-the-data.md).

# Loading the data

## Loading the data (GeoPackage format)

For general guidance on using the product in GeoPackage format, please see the [Getting started with GeoPackage guide](/os-downloads/resources/product-resources/getting-started-with-geopackage-and-vector-tiles-guides/getting-started-with-geopackage.md).

## Loading the data (vector tiles format)

For guidance on using the product in vector tiles format, please see the [Getting Started with Vector Tiles guide](/os-downloads/resources/product-resources/getting-started-with-geopackage-and-vector-tiles-guides/getting-started-with-vector-tiles.md).

## Styling the data

Predefined stylesheets for OS MasterMap Greenspace Layer are available to download from the Ordnance Survey GitHub page below:

{% embed url="<https://github.com/OrdnanceSurvey/OS-MasterMap-Greenspace-stylesheets>" %}

{% hint style="info" %}
*Click the 'Code' drop-down button and then click 'Download ZIP'.*
{% 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/land-and-terrain-portfolio/os-mastermap-greenspace-layer/os-mastermap-greenspace-layer-getting-started-guide/loading-the-data.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.