> 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/buildings-and-infrastructure-portfolio/os-mastermap-topography-layer-building-height-attribute/os-mastermap-topography-layer-building-height-attribute-technical-specification.md).

# OS MasterMap Topography Layer – Building Height Attribute Technical Specification

This technical specification provides detailed technical information about OS MasterMap Topography Layer – Building Height Attribute. It is targeted at technical users and software developers

OS MasterMap Topography Layer – Building Height Attribute is a dataset containing absolute and relative height values for buildings and selected structures contained within OS MasterMap Topography Layer. It is an enhancement to, and forms part of, OS MasterMap Topography Layer.

Building Height Attribute contains height values for buildings, tanks, chimneys (industrial) and glasshouses, specifically for Topographic Area features with the theme of ‘Buildings’ within OS MasterMap Topography Layer. It is necessary to join the Building Height Attribute data to the corresponding OS MasterMap Topography Layer feature to which it belongs, identified by the building topographic identifier (TOID). As such, an OS MasterMap Topography Layer licence is required to use the Building Height Attribute data.

The Building Height Attribute data provides full national coverage.

### Index

This technical specification includes the following sections:

* [Product supply](/os-downloads/products/buildings-and-infrastructure-portfolio/os-mastermap-topography-layer-building-height-attribute/os-mastermap-topography-layer-building-height-attribute-technical-specification/product-supply.md)
* [Product structure](/os-downloads/products/buildings-and-infrastructure-portfolio/os-mastermap-topography-layer-building-height-attribute/os-mastermap-topography-layer-building-height-attribute-technical-specification/product-structure.md)
* [Feature type](/os-downloads/products/buildings-and-infrastructure-portfolio/os-mastermap-topography-layer-building-height-attribute/os-mastermap-topography-layer-building-height-attribute-technical-specification/feature-type.md)
* [Code list](/os-downloads/products/buildings-and-infrastructure-portfolio/os-mastermap-topography-layer-building-height-attribute/os-mastermap-topography-layer-building-height-attribute-technical-specification/code-list.md)
* [Example record](/os-downloads/products/buildings-and-infrastructure-portfolio/os-mastermap-topography-layer-building-height-attribute/os-mastermap-topography-layer-building-height-attribute-technical-specification/example-record.md)


---

# 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/buildings-and-infrastructure-portfolio/os-mastermap-topography-layer-building-height-attribute/os-mastermap-topography-layer-building-height-attribute-technical-specification.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.