> 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-terrain-50/os-terrain-50-overview/pre-requisites.md).

# Pre-requisites

## Computer hardware <a href="#id-1.6.1-computer-hardware" id="id-1.6.1-computer-hardware"></a>

This product may be used on a wide range of hardware platforms (provided sufficient memory and storage facilities are available), varying from tablets or computers using GIS or CAD to mainframe computers with specialised translators and applications. Please see [Coverage and file size data on the product supply page](/os-downloads/products/land-and-terrain-portfolio/os-terrain-50/os-terrain-50-overview/product-supply.md) for more information. Your system supplier will be able to advise on your requirements.

## Computer software <a href="#id-1.6.2-computer-software" id="id-1.6.2-computer-software"></a>

OS Terrain 50 is supplied as inert data in a variety of formats and does not include software for data manipulation.

GML is an open standard format, and the data may need to be translated into the appropriate format for use within a GIS application. A wide range of GIS software can read the GML contour data without translation.


---

# 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-terrain-50/os-terrain-50-overview/pre-requisites.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.