> For the complete documentation index, see [llms.txt](https://docs.os.uk/more-than-maps/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/more-than-maps/data-demonstrators/topography-demonstrators/os-mastermap-r-demonstrators/os-mastermap-topography-layer.md).

# OS MasterMap Topography Layer

A Lightning Talk

## OS MasterMap Topography Overview

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2F8wgO7b344hAJ8gBxn8mX%2FOSMMTopo_Overview_1.png?alt=media&amp;token=b6b985b3-6159-45c8-b219-879ea62b9b52" alt="Image of OS MasterMap Topography Layer representing part of Exeter"><figcaption><p>OS MasterMap Topography Layer</p></figcaption></figure>

OS MasterMap Topography Layer is a digital data product made up of real world fixed features such as fields, roads and buildings, as one continuous dataset. With OS MasterMap Topography Layer, each feature is a record, which has information about the feature’s position and shape on Earth – its geometry – as well as details about it - ‘attributes’ - which provide metadata describing the feature, such as it's make e.g. man-made or natural, and it's description e.g. building or road. OS MasterMap Topography Layer provides an accurate visual context to help interpret addresses, routes and imagery provided by the other OS MasterMap layers.

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FY2sEcPuh5z3lLE2w73ej%2FOSMMTopo_ProductTree.png?alt=media&amp;token=fecf093b-d7d8-46f4-99d0-0b61387b8262" alt="Diagram showing the OS MasterMap Topography Layer in the context of the OS MasterMap family of products. It shows the product family including Topography Layer, Water Network, Sites Layer, Greenspace Layer and Highways Network."><figcaption><p>OS MasterMap family of products structure</p></figcaption></figure>

The product's primary purpose is to provide the most detailed topographic data available of the physical environment of Great Britain. OS MasterMap Topography Layer is published every 6 weeks to a consistently high standard, regularly updated by ground and aerial survey.

### Key Characteristics

The key characteristics and benefits of OS MasterMap Topography Layer are:

* Each uniquely referenced feature has attribution that provides information about the real-world object it represents and metadata that tracks changes to the feature’s lifecycle. (Metadata is data that provides information about the data). This means you can track a feature over time. As well as being able to see what has changed, you can understand more about features, such as when it was last changed, the reason for change, its description and make - whether it is a manmade or a natural feature.
* OS MasterMap is presented seamlessly with 500 million real world objects – all uniquely identified.
* The product employs a scale of data capture appropriate to the density of features – the higher the number of features within an area, the larger the scale used to survey them – ensuring the detail of individual features can be shown. Coordinates are delivered in British National Grid (with the exception of Vector Tiles format, which is supplied in Web Mercator projection – EPSG:3857).
* OS MasterMap Topography Layer can be used as part of a data modelling or a predictive modelling tool (predicting future events or patterns). An example of predictive modelling is mapping crime; analysing the type of areas crime is occurring in and then using the results to find similar areas where crime could occur.
* In addition, OS MasterMap Topography Layer is also used by organisations looking for areas where specific physical conditions exist. A retailer, for example, may use OS MasterMap Topography Layer to help them find a site for a new store by using the attribution to find land parcels of a certain size and distance. Emergency planners may use OS MasterMap Topography Layer to assist in planning and preparing for emergencies by identifying the areas most likely to be affected. The product can be used to map or model the sequence of events in any given type of emergency, so that emergency services' own resources and command centres are unlikely to be cut off or taken out of action by the emergency itself.

Individual real-world topographic features in the OS MasterMap Topography Layer are represented by polygons (closed objects), lines, and points , each with their own unique reference, called a topographic identifier (TOID).

Each feature has one of these three geometrical structures – polygon, lines and points. Polygon features fit seamlessly with each other topologically within structuring layers.

{% tabs %}
{% tab title="Polygons" %}

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2Ff8ZXLS9rgl7b6kK0eTH4%2FOSMMTopo_Overview_2.png?alt=media&amp;token=f281cfdd-30d0-4901-8244-6ecc97d0b0d0" alt="Image of OS MasterMap Topography Layer representing part of Exeter, showing only polygon features."><figcaption><p>Polygon features in OS MasterMap Topography Layer</p></figcaption></figure>

This view shows polygon features; buildings, road casings, land (both manmade and natural).
{% endtab %}

{% tab title="Lines" %}

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2F6BzbFxIJepEd7j4dLAqa%2FOSMMTopo_Overview_3.png?alt=media&amp;token=e9e73a89-a305-48fc-aa99-e548ea5ec522" alt="Image of OS MasterMap Topography Layer representing part of Exeter, showing line features as grey lines on a white background."><figcaption><p>Line features in OS MasterMap Topography Layer</p></figcaption></figure>

This view shows lines, depicting the outlines of buildings, the edges of roads, junctions, pavement and paths.
{% endtab %}

{% tab title="Points" %}

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FCUKHtbE4xgpbEMKS2Tyh%2FOSMMTopo_Overview_4.png?alt=media&amp;token=086b0139-d3a2-4527-99f0-ffa55e503ce9" alt="Image of OS MasterMap Topography Layer representing part of Exeter, showing point features as grey points on a white background."><figcaption><p>Point features in OS MasterMap Topography Layer</p></figcaption></figure>

This view shows points such as spot heights, position of individual trees, posts, heritage features and masts.
{% endtab %}

{% tab title="Cartographic Text" %}

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FbvdT42VmQ2lzjZZfSWEu%2FOSMMTopo_Overview_5.png?alt=media&amp;token=6f92e9d0-c3e3-4942-a1cf-727bd9783011" alt="Image of OS MasterMap Topography Layer representing part of Exeter, showing grey cartographic text features on a white background."><figcaption><p>Cartographic Text features in OS MasterMap Topography Layer</p></figcaption></figure>

This view shows cartographic text in OS MasterMap Topography Layer. This text adds information to the data when displayed as a map including road and place names.
{% endtab %}

{% tab title="Combined View" %}

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FjGCAKE9zu0d3LqDGavsd%2FOSMMTopo_Overview_6.png?alt=media&amp;token=a4a9ad37-561b-4f98-8e71-f34510d58ab5" alt="Image of OS MasterMap Topography Layer representing part of Exeter"><figcaption><p>OS MasterMap Topography Layer</p></figcaption></figure>

The final view is of all the different feature types combined for the centre of Exeter, as cartographic representation of the real world.
{% endtab %}
{% endtabs %}

### Area features represent real world objects

OS MasterMap Topography Layer shows real world features on the ground such as buildings, roads, and paths. The term 'real-world object' is used to describe a geographic entity that can be captured and represented in the data (e.g. anything fixed on the ground that you can trip over or walk into). The data is captured by Ordnance Survey surveyors using GPS surveys on the ground and by aerial imagery.

For cartographic representation, OS MasterMap Topography Layer is captured and designed for display at 1:1250 Urban, 1:2500 Rural and 1:10 000 Mountain and Moorland scales for urban, rural and mountain and moorland areas respectively.

In Geographical Information Systems (GIS), OS MasterMap Topography Layer can be viewed over a range of scales. The most scale-sensitive feature types, such as cartographic text and symbol features, are fixed in size and rapidly become less clear at smaller display scales (that is, when zoomed further out to see a larger geographic area).

OS MasterMap Topography Layer is also suitable for use in non–cartographic applications where the concept of scale is less applicable.

### Polygon Closing Links / Inferred Links <a href="#r_k" id="r_k"></a>

OS MasterMap Topography Layer includes both closing and inferred links. These are line features which are created in the data to show actual boundaries for features on the ground which are not visible in the real world. They are lines that Ordnance Survey has introduced into the data to make some types of polygons into more manageable units. There are three main types.

{% tabs %}
{% tab title="Network Closing Links" %}

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FrrZQNTQX5vHpJUe2linG%2FOSMMTopo_Links_2.png?alt=media&amp;token=087fd813-8b2e-491a-b957-35b9a3b46c93" alt="Network closing links as shown in OS MasterMap Topography Layer. The links appear as dashed red lines on a pale basemap."><figcaption><p>Example of network closing links in OS MasterMap Topography Layer</p></figcaption></figure>

The first type are network closing links. These are frequently found where roads meet at junctions. They are described as Polygon Closing Link under Descriptive Term.
{% endtab %}

{% tab title="Inferred Property Closing Links" %}

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FonLQO6rgFYwf0GzTdaz5%2FOSMMTopo_Links_3.png?alt=media&amp;token=2f755a3c-793b-4c76-9506-85f2106139fe" alt="Inferred property closing links as shown in OS MasterMap Topography Layer. The links appear as dashed red lines on a pale basemap."><figcaption><p>Example of inferred property closing links in OS MasterMap Topography Layer</p></figcaption></figure>

Another example is the creation of a link to separate an open-plan garden around a pair of semi-detached houses into two distinct entities, reflecting that there are two properties there in the real world. They are described as Inferred Property Closing Link under Descriptive Term.
{% endtab %}

{% tab title="Divisions" %}

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FUOT1i69VUAV4QYLjQJun%2FOSMMTopo_Links_4.png?alt=media&amp;token=051cf3ad-923b-48f9-a86c-34bd1ca90447" alt=""><figcaption><p>Example of division features in OS MasterMap Topography Layer</p></figcaption></figure>

The third type are closing links between properties such as semi-detached. They do not constitute the legal boundary of any property any more than a physical line feature does. These links are clearly identified in the ‘descriptive group’ attribution and if a customer wishes to not show these features that is possible. They are described as Division under Descriptive Term.
{% endtab %}
{% endtabs %}

## Themes within OS MasterMap Topography Layer <a href="#r_r" id="r_r"></a>

A *Theme* is a set of features that have been grouped together and provide a means of dividing the data in a logical and user-friendly fashion. A feature can be a member of any number of themes but must belong to at least one theme as a minimum requirement.

The themes are:

* Administrative Boundaries
* Buildings
* Heritage and Antiquities
* Land
* Rail
* Roads Tracks, and Paths
* Structures
* Terrain and Height
* Water

### Administrative Boundaries

Administrative boundaries are defined as showing the limits of responsibility and representation for electoral and administrative purposes. Boundary alignments are shown within the Administrative Boundaries theme. As well as the boundary’s relationship to real-world objects, its boundary descriptions, where needed for clarification, are also supplied.

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FP9zzduc5T8f3WoFYnUGX%2FOSMMTopo_AdminBoundaries_2.png?alt=media&amp;token=f1bbc7e5-aa50-41be-8637-6d142ef55f87" alt="Boundary theme features in OS MasterMap Topography Layer. The features appear as purple dashed lines on a pale basemap"><figcaption><p>Administrative boundaries theme features with OS Maps API for background context.</p></figcaption></figure>

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FaZy2SfAEuuLDusOwOdqC%2FScreenshot%202026-09-24%20144208.png?alt=media&amp;token=c1340753-bb72-4152-af2c-7c2119eb6717" alt="Boundary theme features in OS MasterMap Topography Layer with an inset box showing attribution. The features appear as purple dashed lines on a pale basemap"><figcaption><p>Attributes for an individual feature in the administrative boundaries theme.</p></figcaption></figure>

### Buildings

Buildings are defined as permanent roofed constructions, usually with walls. This includes permanent roofed constructions that exceed 8.0m² in area (12.0m² in private gardens).

Exceptions are made to this area rule for smaller buildings that, due to their detached position, form relatively important topographic features; these are shown at minimum size, as stated above.

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FJsTAho7oVMdxZhhed2qI%2FOSMMTopo_Buildings_2.png?alt=media&amp;token=0a810e04-1ad2-43c5-86c7-aa465c4766be" alt="Building theme features in OS MasterMap Topography Layer. The features appear as brown polygons with black text labels on a pale basemap."><figcaption><p>Buildings theme features with the OS Maps API as a backdrop giving context.</p></figcaption></figure>

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FYXjQOX4CW1bfIt0499wc%2FScreenshot%202026-09-24%20144303.png?alt=media&amp;token=57203255-0f91-44f4-b2a3-7f6990fbfd33" alt="Building theme features in OS MasterMap Topography Layer with an inset box showing attribution. The highlighted building feature appears as a red polygon."><figcaption><p>Attributes for an individual feature in the buildings theme.</p></figcaption></figure>

### Heritage and Antiquities

Heritage and Antiquities are defined as existing artificial features of a date not later than AD 1714 (the date of the accession of George I). This can refer to individual points or objects in the data. These antiquities are captured along with very important battlefield sites and natural features connected with important historic events.

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FAGoqqak5S54P3mlSXz71%2FOSMMTopo_Herit%26Antiq_2.png?alt=media&amp;token=19c47269-c4ec-40ab-9ded-17488471650a" alt="Heritage and Antiquities theme features in OS MasterMap Topography Layer. The features appear as grey line and point features with grey cartographic text on a pale basemap."><figcaption><p>Heritage and antiquities features with the OS Maps API as a backdrop giving context.</p></figcaption></figure>

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FlOr2zpmU0KD1ctFXfKF0%2FScreenshot%202026-09-24%20144416.png?alt=media&amp;token=f45cd493-0544-425b-9fb7-0ed6576d4f44" alt="Heritage and Antiquities features in OS MasterMap Topography Layer with an inset box showing attribution. The highlighted feature appears as a red polygon."><figcaption><p>Attributes for an individual feature in the heritage and antiquities theme.</p></figcaption></figure>

### Land

A land feature is defined as either a man-made or a natural polygon feature that describes the surface cover and area to which it is applied. This includes both natural and man-made slopes and cliffs. All general features are also placed in the Land theme. There are some exceptions to this, such as routes of communication and buildings.

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2Fq0Ra4rWGbx28HkkGKnB0%2FOSMMTopo_Land_2.png?alt=media&amp;token=f9c54ac7-241f-4888-9c5a-d685c21a12e4" alt="Land theme features in OS MasterMap Topography Layer. The features appear as green polygons with black text labels on a pale basemap."><figcaption><p>Land features with the OS Maps API as a backdrop giving context.</p></figcaption></figure>

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FonhCTjfWKqNuUiGAX31a%2Fimage.png?alt=media&amp;token=b9a4dddc-a8c4-4fa8-9743-fc33f0da251a" alt="Land theme features in OS MasterMap Topography Layer with an inset box showing attribution. The highlighted land feature appears as a red polygon."><figcaption><p>Attributes for an individual feature in the land theme.</p></figcaption></figure>

### Rail

Rail features are defined as features related to travel by railway or tramway. The exception to this is railway tunnels, which are currently in the Structures theme.&#x20;

OS MasterMap Topography Layer contains information relating to permanent railways that form the network between two points. Examples include the track from railway station to railway station, or the track from an industrial building to a private quarry.

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FtbROes41K3QfKCFSzr31%2FOSMMTopo_Rail_2.png?alt=media&amp;token=3a038fbf-fdb5-477d-9469-2a13ff40684c" alt="Rail theme features in OS MasterMap Topography Layer. The features appear as grey polygons on a pale basemap."><figcaption><p>Rail features with the OS Maps API as a backdrop giving context.</p></figcaption></figure>

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FdVKPKGUmRafWjE40A3yg%2FScreenshot%202026-09-24%20145628.png?alt=media&amp;token=1fdc72f7-0fd7-4f61-abf8-67afb5ba4e06" alt="Rail theme features in OS MasterMap Topography Layer with an inset box showing attribution. The highlighted rail feature appears as a red polygon."><figcaption><p>Attributes for an individual feature in the rail theme.</p></figcaption></figure>

### Roads, Tracks, and Paths

Road: A road is defined as a metalled way for vehicles. Roads that form part of the public network and driveways to private properties that are over 100m in length are normally included within OS MasterMap Topography Layer

Track: A track is defined as an unmetalled way that is clearly marked, permanent and used by vehicles. Tracks are only normally recorded in private gardens if they are 100m or more in length. They need not be ‘all weather’.

Paths: A path is defined as any established way other than a road or track. They can be considered as either ‘made’ or ‘unmade’.

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FlgMB4vGyltMRHICgkhMW%2FOSMMTopo_RTP_2.png?alt=media&amp;token=b0b84d7a-3926-42b6-93fa-44c1981ce7ba" alt="Roads tracks and paths theme features in OS MasterMap Topography Layer. The features appear as grey polygons on a pale basemap."><figcaption><p>Roads, tracks and paths features with the OS Maps API as a backdrop giving context.</p></figcaption></figure>

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FCbBCfC9vbMVRidBmENjV%2FScreenshot%202026-09-24%20150043.png?alt=media&amp;token=50ffa474-5585-476c-8062-90fbe62fefa0" alt="Roads tracks and paths theme features in OS MasterMap Topography Layer with an inset box showing attribution. The highlighted road feature appears as a red polygon."><figcaption><p>Attributes for an individual feature in the roads, tracks and path theme.</p></figcaption></figure>

### Structures

Structures are defined as features that are man-made constructions but do not qualify as buildings, for example, Band Stands and Clock Towers. These features may or may not obstruct passage at ground level.&#x20;

OS MasterMap Topography Layer contains information relating to all permanent structures that are considered large enough to be included (minimum area of 4m squared) - if they are not captured they might be shown by text. Structures include stand-alone monuments, fountains, covered reservoirs, pylons, weirs and sluices, gas holders, pontoons, and uncovered tanks.

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2F3YjrMS18FD0TnUjUuoSw%2FOSMMTopo_Struc_2.png?alt=media&amp;token=7bed7763-31a6-4aa9-900d-603f9359d134" alt="Structures theme features in OS MasterMap Topography Layer. The features appear as grey polygons on a pale basemap."><figcaption><p>Structures features with the OS Maps API as a backdrop giving context.</p></figcaption></figure>

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FRzKOaDYTqcLrXvv2QKIN%2FOSMMTopo_Struc_3.png?alt=media&amp;token=d297ab5c-2208-4161-adae-4391c9a68771" alt="Structures theme features in OS MasterMap Topography Layer with an inset box showing attribution. The highlighted structure feature appears as a red polygon."><figcaption><p>Attributes for an individual feature in the structures theme.</p></figcaption></figure>

### Terrain and Height

These features denote the ground level at any given point. OS MasterMap Topography Layer does not contain height contours; instead it contains height information point features of known height.

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FpmiEnNNM8mfKEYMCjsDr%2FScreenshot%202026-09-24%20150831.png?alt=media&amp;token=fb790aa2-4d7d-4dff-94d8-d4418611868d" alt="Terrain and height theme features in OS MasterMap Topography Layer. The features appear as grey crosses with grey text denoting a height on a pale basemap."><figcaption><p>Terrain and height features with the OS Maps API as a backdrop giving context.</p></figcaption></figure>

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2Fui9BMCgfLeJUIsXgeud9%2FScreenshot%202026-09-24%20151016.png?alt=media&amp;token=0510a01f-e019-4cf8-99fd-cfbbee5f8c02" alt="Terrain and height theme features in OS MasterMap Topography Layer with an inset box showing attribution. The highlighted spot height feature appears as a red point."><figcaption><p>Attributes for an individual feature in the terrain and height theme.</p></figcaption></figure>

### Water

Water features are defined as features that contain, delimit, or relate to real-world objects containing water. Examples include streams, lakes, rivers, tide lines and canals.

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2F251MGhEGWoNtCC8buld5%2FOSMMTopo_Water_2.png?alt=media&amp;token=4d2161c3-fa8b-47b8-b1e5-982c5fe58b6b" alt="Water theme features in OS MasterMap Topography Layer. The features appear as blue polygons on a pale basemap."><figcaption><p>Water features with the OS Maps API as a backdrop giving context.</p></figcaption></figure>

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FM24fpCj97zPDzQ3SKP4d%2FScreenshot%202026-09-24%20151246.png?alt=media&amp;token=4fd12aa7-a8ff-4e32-8026-3038dd2a2605" alt="Water theme features in OS MasterMap Topography Layer with an inset box showing attribution. The highlighted water feature appears as a red polygon."><figcaption><p>Attributes for an individual feature in the water theme.</p></figcaption></figure>

## Example Use Case <a href="#r_14" id="r_14"></a>

A local authority could use the OS MasterMap Topography Layer to maintain a register of land and buildings in their ownership. They can attach their own attribution to that already provided with the product. When this kind of data association takes place, it can lead to efficiencies in storing and using data. It can also enable data to be shared more easily both between and within organisations.

One example use case of the data is by Transport for the West Midlands (TfWM) who have used OS MasterMap Topography Layer to build a transport network layer. This project allowed Transport for West Midlands to work more efficiently, saving them time and money, reducing site visits, and significantly improving decision making.

The project enabled Transport for West Midlands to use Ordnance Survey data products to understand the geography of their network for road space reallocation, active travel planning, and other transport planning schemes such as emergency vehicle routing.

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FBW5HFcTe8OYJC2Qt6ngm%2FOSMMTopo_Example_2.png?alt=media&amp;token=6bbf78a8-8847-49a5-84b5-b8f3ba00ae06" alt="A representation of the road network as used in the TfWM project. Roads are represented as pink line features on a pale basemap."><figcaption><p>The road network used in the project</p></figcaption></figure>

The project used the topology of the roads layer as the actual road dimensions were one of the key elements TfWM were interested in. The methodologies that they developed enabled the identification of detailed street scenes with widths at one metre internals based on the road polygons. This provided a better understanding of the road space available and differing street gradients were highlighted to show the optimal locations for mobility hubs.

The methodologies developed will be supporting future TfWM projects in numerous ways - from identifying detailed street scene widths, to understanding available the road space.

## Product Supply

The available formats for the product are:

• GeoPackage

• Vector tiles (MBTiles) (National cover full supply only)

• Geography Markup Language (GML) 2.1.2 4.2

File sizes vary greatly depending on tile size and the quantity of features present in a tile:

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2F2v56nMFpWb1BCbdHP7wk%2FOSMMTopo_ProdSupply.png?alt=media&amp;token=aaebe297-2288-4b69-ab54-d44599447a74" alt="Table describing typical file sizes for OS MasterMap Topography Layer"><figcaption></figcaption></figure>

### Ordering OS MasterMap Topography Layer

OS MasterMap Topography Layer is obtained from a web-based ordering system that allows users to order an initial data supply and set a schedule for updates as required.

The product is supplied as an online download from the [OS Data Hub](https://osdatahub.os.uk/), and is available in the following formats:

• GeoPackage (for area of interest only)

• Vector tiles (MBTiles) (National cover only)

• Geography Markup Language (GML) version 2.1.2

The GML download ZIP package contains a GZ (.gz) file, which does not require extraction and contains multiple GML (.gml) files. The GML data is supplied in 5km <sup>2</sup> tiles and features are not clipped at the tile edges, resulting in what is called “hairy” tiles.

The DataHub also has two options for ordering the data:&#x20;

* 5km downloads as either national cover or an area of interest.&#x20;
* National coverage (all of Great Britain).

### Feature Validation Dataset <a href="#r_1l" id="r_1l"></a>

The Feature Validation Dataset (FVDS) is a set of files that can optionally be supplied with either a Full Supply Change Only Update (COU) or an Area of Interest (AOI) COU of an OS MasterMap Topography Layer order in GML format only.

The FVDS allows the validation of the data holding ensuring it contains the correct set of features after loading. It does this by reporting on all the data it expects to find in the holding after the application of the supply, not just what is contained in the supply.

The FVDS is intended to be used for periodic checks on data holdings maintained by a COU regime.

It can also be used to check that an initial supply of OS MasterMap Topography Layer data has been correctly loaded.

The FVDS can be used with both geographic and non-geographic chunk file options.

The FVDS is a comma-separated value (.csv) text file format that gives the TOID, version number and version date of every feature that should exist in the current data holding, based on the polygon extent, themes, polygon format and extraction date of the current order.

### Change only update

When you order the product you can decide to receive:

* A one off supply of your area of interest.
* Or a complete resupply of the whole product to replace the data in your current holdings.
* Or an initial supply with a change only update schedule or just the changes in area (change only update). The frequency for change-only-update is six weekly.

If Geo Chunks are requested the change file will include inserts.

OS Products refresh dates can be found [here](https://docs.os.uk/os-downloads/resources/product-resources/product-refresh-dates).&#x20;

The below series of images shows the change over time in area between different data releases and how change only update can show visually change in an area overtime.

{% tabs %}
{% tab title="2010" %}

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2F3Wpu0v71x8d3FT8ye4FF%2FOSMMTopo_COU_1.png?alt=media&amp;token=1bd2cc87-5b36-4689-a28b-8d4a8abd2fcb" alt="OS MasterMap Topography Layer representation of an area of Southampton in 2010. Buildings appear as beige polygons, roads as grey polygons, water as blue polygons, and land as green and brown polygons. "><figcaption><p>OSMM Topography Layer representation of a particular area in 2010</p></figcaption></figure>
{% endtab %}

{% tab title="2015" %}

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FZWnoelk4XpwygLc3sWAm%2FOSMMTopo_COU_2.png?alt=media&amp;token=86f3d79e-a4fc-4762-9297-a4315900e591" alt="OS MasterMap Topography Layer representation of an area of Southampton in 2010. Buildings appear as beige polygons, roads as grey polygons, water as blue polygons, and land as green and brown polygons. Compared to 2010, more buildings have appeared in what was before undeveloped land"><figcaption><p>OSMM Topography Layer representation of the same area in 2015</p></figcaption></figure>
{% endtab %}

{% tab title="2023" %}

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FvYypztDR63PtHEjXczzA%2FOSMMTopo_COU_3.png?alt=media&amp;token=edfa74f4-2fd9-4acc-91ce-706077a14be8" alt="OS MasterMap Topography Layer representation of an area of Southampton in 2010. Buildings appear as beige polygons, roads as grey polygons, water as blue polygons, and land as green and brown polygons. Compared to 2015, large amounts of housing have been built in the area."><figcaption><p>OSMM Topography Layer representation of the same area in 2023</p></figcaption></figure>
{% endtab %}
{% endtabs %}

Using change only update is useful in helping to monitor change over time in an area. By comparing different versions of the data, users can analyse how landscapes and structures have evolved. The use of change only update helps with the creation of historical views. What did a particular area look like before a new development, how might this affect the local environment? What was there before a new development? Was the development built on a green field site? Where did roads go before a development?

## Styling <a href="#r_2a" id="r_2a"></a>

To optimise the cartographic representation of the data, there are four different styles available: Standard, Road, Outdoor and Light. These predefined stylesheets are available in four formats (QGIS QML files, ESRI Layer files, Style Layer Descriptor (SLD) and JSON) for interoperability with GIS and web map services. The files can be downloaded via the 'OS MasterMap Topography Layer Stylesheets page' on [GitHub](https://github.com/OrdnanceSurvey/OSMM-Topography-Layer-stylesheets). Note: Click the 'Code' drop-down button and then click 'Download ZIP' to access the styling files from GitHub.

See [here](https://docs.os.uk/more-than-maps/geographic-data-visualisation/geodataviz-assets/styling-data/how-to-download-and-use-os-stylesheets) for a guide on downloading and using OS style sheets.

The following images are examples of the four different styles for OS MasterMap Topography Layer.

{% tabs %}
{% tab title="Standard" %}

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FeijmfAA4MMsvxcBNNJNI%2FScreenshot%202026-09-24%20153459.png?alt=media&amp;token=44a08e22-bf81-4f32-b4dd-b4dd8cb6a80c" alt="OS MasterMap Topography Layer representation of an area in the standard styling. Buildings appear as beige polygons, roads as grey polygons, water as blue polygons, and land as green and brown polygons. "><figcaption><p>Standard OS MasterMap Topography Layer style</p></figcaption></figure>

This is the original style which was created when OS MasterMap was first released.
{% endtab %}

{% tab title="Road" %}

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FWg3dCIsQGRe32UWy3tPY%2FScreenshot%202026-09-24%20153645.png?alt=media&amp;token=8db809a8-f8fd-40c9-bc91-67fda8fea4e7" alt="OS MasterMap Topography Layer representation of an area in the road styling. Buildings appear as beige polygons, roads as white polygons, water as blue polygons, and land as green and brown polygons. "><figcaption><p>Road OS MasterMap Topography Layer style</p></figcaption></figure>

A familiar style with a focus on transport networks - specifically highlighting the Great British road network. High in contrast with lots of detail and colour.
{% endtab %}

{% tab title="Outdoor" %}

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FCRrHQaePrj3b20lk2SiW%2FScreenshot%202026-09-24%20153848.png?alt=media&amp;token=6ca6a5d0-d0f3-4220-a6ce-5b8c7583c1d1" alt="OS MasterMap Topography Layer representation of an area in the outdoor styling. Buildings appear as beige polygons, roads as white polygons, water as blue polygons, and land as green and brown polygons with symbols. "><figcaption><p>Outdoor OS MasterMap Topography Layer style</p></figcaption></figure>

This style focuses on terrain and land cover, it has a minimal colour palette and familiar symbology. Useful as an overview of an area and clearly shows different feature types, making it particularly useful for rural areas.
{% endtab %}

{% tab title="Light" %}

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FL1UfXxYlg0Ilfq2LbVgN%2FScreenshot%202026-09-24%20154012.png?alt=media&amp;token=8c041b57-a9c5-46fa-adcf-29ea415e3d3d" alt="OS MasterMap Topography Layer representation of an area in the light styling. Compared to other styles, the colours are muted."><figcaption><p>Light OS MasterMap Topography Layer style</p></figcaption></figure>

Designed specifically for data visualisation, this style has a subtle palette and is simple and clear. Use it to add geographic context. It is ideal for when you want to add additional layers on top of the data but still want to view the underlying features.
{% endtab %}
{% endtabs %}

## OS MasterMap Building Heights <a href="#r_2f" id="r_2f"></a>

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.

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FV1BLA1Xxhs4BKAQaIcDa%2FOSMMTopo_BuildHeight_1.png?alt=media&amp;token=2857bf90-f965-4086-a1a8-f3740aa82e50" alt="A 3D representation of a built up area where water is represented in blue, roads in white, land in brown and green, and buildings as 3D brown objects of varying heights"><figcaption><p>3D representation of buildings</p></figcaption></figure>

### Product Supply

Building Height Attribute data is supplied in an uncompressed comma-separated values (CSV) file format, which can be downloaded from the [OS Data Hub](https://osdatahub.os.uk/).

Building Height Attribute is supplied in 5km² geographic chunks. Each 5km² chunk will contain Building Height Attribute values for any building polygon that intersects that area. As such, any Building Height Attribute values that fall across tile boundaries in contiguous tiles will be duplicated. Tiles are supplied with all available data contained within them. Not all 5km² tiles will have complete coverage.

### How to use it

To use use Building Heights, join the Building Height Attribute data to the corresponding OS MasterMap Topography Layer feature by linking the Building Height attribute to the building topographic identifier (TOID) in OS MasterMap. An OS MasterMap Topography Layer licence is required to use the Building Height Attribute data and provides full national coverage.

### How OS MasterMap Height data is created

Building Height Attribute data is generated from photogrammetrically derived Digital Terrain Models (DTMs) and Digital Surface Models (DSMs). That is, information gathered from aerial surveys as part of Ordnance Survey's cyclical revision programmes. DTMs show the bare ground surface, having extruded features such as buildings, trees, etc, whereas DSMs depict the elevations of the top surfaces of buildings, trees, towers and other features elevated above the bare earth.

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2Fx9ZiE5B32ZTHfU3pDgBS%2FOSMMTopo_BuildHeight_2.png?alt=media&amp;token=ec746d99-91e6-4a4a-9634-2555465c0740" alt="Diagram showing the difference between a DTM and DSM. A DTM represents the height of the ground and a DSM additionally represents the height of objects on the ground e.g. buildings and trees. "><figcaption><p>Diagram of a DTM and DSM</p></figcaption></figure>

### Attribution

<figure><img src="https://3774974716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIfdYInJITdcxaLLMhlD%2Fuploads%2FtSnp6pf7tXuqH14Z57w9%2FOSMMTopo_Attribution.png?alt=media&amp;token=a44d5a6d-ce41-44d2-be99-7d578bd93d8d" alt="diagram showing building height attribution such as absolute height minimum against a photo of a house"><figcaption><p>Diagram showing building height attribution</p></figcaption></figure>

#### Absolute Height Minimum (AbsHMin)

The lowest point extracted from the DTM (digital terrain model) within the footprint of the building as represented in OS MasterMap Topography Layer. This aims to represent the lowest absolute height of the intersection of the external building walls and the underlying ground surface.

#### Absolute Height Maximum (AbsHMax)

This represents the highest point of the building extracted from the DSM (digital surface model) within the footprint of the building or structure represented in OS MasterMap Topography Layer. The highest point could be represented by any structure on top of the building, provided it is of sufficient size to be captured in the DSM source data. This may include industrial chimney stacks, machinery and any substantial structures that may be present on top of the building. Smaller structures like chimney stacks as found on residential buildings will be excluded from the AbsHMax measurement.

#### Absolute Height 2 (AbsH2)

AbsH2 is a calculated value which aims to represent the lowest point where the roof intersects the alignment of the external vertical walls of the principal part of the building. This is usually referred to as the building eave height. The principal part of the building is defined as the main structure, excluding elements at higher or lower elevation. In buildings with multiple heights (for example, a main two storey building with a smaller single storey extension), the eave height is calculated from the largest building extent.

#### Relative height values

The two relative building height values are generated from the differences between the absolute elevation values. The relative heights can be used in isolation to provide a third dimension to buildings, while all other features will be flat. Relative heights are denoted with the prefix ‘Rel’. These attributes are also applicable to the Tank, Glasshouse and Chimney Stack structures included in the data. The unit of measurement used for relative heights is metres.

**RelHMax:** RelHMax (Relative Height Maximum) is the derived value from the calculation of AbsHMax (the calculated absolute value for the building height), minus AbsHMin (the calculated absolute value for ground height), i.e. RelHMax = AbsHMax – AbsHMin.

**RelH2:** RelH2 (Relative Height 2) is the derived value from the calculation of AbsH2 (the calculated absolute value for the eave height), minus AbsHMin (the calculated absolute value for ground height).

### Use Cases

The data can be used for modelling air pollution, siting solar panels, visualising planning applications in the context of surrounding buildings and also for urban density. Emergency services can also use it to know when and where to deploy specialist equipment.

It can also be used to model heat loss, regulate requirements including high-rise gas safety, help with smart meter roll-out and analyse line of sight for small cell planning. It can help to manage overhead cable routing and assist in planning and maintaining water pressure to high-rise properties.

Building Heights have been used for planning applications to show how a new office building would fit into existing buildings. Existing buildings were extruded and the 3D model for the new building was added to the map to show how it would look once constructed.

Some fire and rescue organisations have created 3D models of buildings over a certain height in web mapping applications following the Grenfell Tower fire. It enables firefighters to see clearly whether there are any buildings over 18 meters in height before arriving at a incident and therefore what equipment to take.

## Supporting Documents

**Technical Specification**

* The [technical specification](https://docs.os.uk/os-downloads/products/maps-and-imagery-portfolio/os-mastermap-topography-layer/os-mastermap-topography-layer-technical-specification) provides detailed technical information about the product. It is targeted at technical users and software developers.

**Supporting documents**

* [OS MasterMap - Real-world object catalogue](https://www.ordnancesurvey.co.uk/documents/legends/os-mastermap-real-world-object-catalogue.pdf): This catalogue lists the real-world objects (RWOs) present in OS MasterMap data and the features and attributes associated with them.
* [Getting started with styling guide](https://docs.os.uk/os-downloads/products/maps-and-imagery-portfolio/os-mastermap-topography-layer/os-mastermap-topography-layer-getting-started-with-styling-guide): This document provides information on how to style the OS MasterMap Topography Layer product. For related styling information, please refer to the Standard Styling Specification.
* [Standard styling specification](https://docs.os.uk/os-downloads/products/maps-and-imagery-portfolio/os-mastermap-topography-layer/os-mastermap-topography-layer-standard-styling-specification): This document provides information on the Standard Styling Specification for the OS MasterMap Topography Layer product.
* [Additional information on OS MasterMap Building Height Attribute.](https://beta.ordnancesurvey.co.uk/products/os-mastermap-building-height-attribute)
* [OS products refresh dates](https://docs.os.uk/os-downloads/resources/product-refresh-dates).

***

Links that may be useful:

{% embed url="<https://osngd.gitbook.io/osngd/>" %}

{% embed url="<https://osdatahub.os.uk/>" %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.os.uk/more-than-maps/data-demonstrators/topography-demonstrators/os-mastermap-r-demonstrators/os-mastermap-topography-layer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
