> For the complete documentation index, see [llms.txt](https://docs.racemap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.racemap.com/data-export-from-racemap/self-hosted-elevation-service.md).
# Hosted elevation service
Use our open elevation data API with highest vertical precision of 1 m
The [Google elevation API](https://developers.google.com/maps/documentation/elevation/start?hl=de) provides a vertical accuracy of 30 m and there is no other open elevation service providing more accurate data available. During the development of [Predictive Tracking](/prediction.md) we noticed, that this cartographic data is not precise enough and we developed a self-hosted elevation service (vertical accuracy of 1 m), you can use for your own projects under MIT license. You either host this service yourself or just use our API.
* Mapzen terrain data:
* GitHub documentation and source code:
* hosted elevation service:
#### Working with the elevation data API
You can download portions of the data. The data is organized by latitude/longitude where each chunk is 1x1 degree. Eg. for downloading the UK data you need to know the lat/lng extent of the UK and download all the necessary files. Example:
```
aws s3 cp --no-sign-request s3://elevation-tiles-prod/skadi/N51/N51E000.hgt.gz /path/to/data/folder/N51
```
Make sure to reproduce the file structure when downloading, e.g. `./N51/N51E001.hgt.gz`. The whole dataset is just \~200GB, so maybe it is even feasible to download the whole thing.
Regarding the licensing, please check for yourself: &
---
# 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.racemap.com/data-export-from-racemap/self-hosted-elevation-service.md?ask=&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.