> 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/maps-and-imagery-portfolio/1-50-000-scale-colour-raster/1-50-000-scale-colour-raster-overview/features-depicted-in-the-product.md).

# Features depicted in the product

The following features are depicted in 1:50 000 Scale Colour Raster:

## Man-made structures <a href="#id-2.6.1-man-made-structures" id="id-2.6.1-man-made-structures"></a>

Buildings are generalised and shown with colour tint and cartographically placed text to indicate settlement name and extent.

Structures are indicated by lines, buildings or symbols and are supplemented with a text description for all distinctive named features. Important buildings are displayed independently from other generic building features.

## Transport <a href="#id-2.6.2-transport" id="id-2.6.2-transport"></a>

Transport features depicted include tracks, public rights of way, cycle networks, paths, roads, railway lines (single and multiple track), railway stations, airports and airstrips, ferry routes and ports, cycle routes, and bus and coach stations.

## Natural landscape features <a href="#id-2.6.3-natural-landscape-features" id="id-2.6.3-natural-landscape-features"></a>

Different types of natural features and vegetation are shown by symbols or colour tint, including woods, rock, scree, boulders, sand, shingle, mud and slope. There is also information relating to the extents of Forestry Commission access land and National Trust land.

## Water features <a href="#id-2.6.4-water-features" id="id-2.6.4-water-features"></a>

Water features are shown in blue with associated text. A distinction is made between natural (blue) and man-made (black) water features, with the exception of canals (which are shown in blue).

## Height <a href="#id-2.6.5-height" id="id-2.6.5-height"></a>

Ground contours, survey heights and air survey heights are depicted.

Surface heights are to the nearest metre above mean sea level. Heights shown close to a triangulation pillar refer to the ground level height at the pillar and not necessarily to the height at the summit.

## Heritage and archaeological sites <a href="#id-2.6.6-heritage-and-archaeological-sites" id="id-2.6.6-heritage-and-archaeological-sites"></a>

Depiction includes information supplied by English Heritage, the Royal Commission on the Ancient and Historical Monuments of Scotland, and the Royal Commission on the Ancient and Historical Monuments of Wales.

## Administrative boundaries <a href="#id-2.6.7-administrative-boundaries" id="id-2.6.7-administrative-boundaries"></a>

National, county, district, unitary authority, civil parish and constituency boundaries are all depicted.

## Annotation <a href="#id-2.6.8-annotation" id="id-2.6.8-annotation"></a>

Descriptive and distinctive names are depicted as text:

* Tourist Information Centres
* Camping / caravan sites
* Gardens
* Golf courses
* Nature reserves
* Car parks
* Picnic sites
* Viewpoints
* Youth hostels


---

# 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/os-downloads/products/maps-and-imagery-portfolio/1-50-000-scale-colour-raster/1-50-000-scale-colour-raster-overview/features-depicted-in-the-product.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.
