> 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/transport-network-portfolio/os-mastermap-highways-network-fundamentals/os-mastermap-highways-network-overview/feature-types/access-restrictions-present-in-rami-product.md).

# Access Restrictions (present in RAMI product)

An Access Restriction is a feature where access to a road or area by vehicles can be legally prohibited. Prohibited access restrictions are indicated by regulatory signs with a red circle or a no entry sign. In addition, access could be limited for use by particular classes of vehicle; these are indicated by regulatory signs with a blue circle. Access restrictions may also include exemptions to the restriction. The Access Restriction Feature Type comprises these types of restrictions.

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FrY5JGkjv6Se4s66N6Tky%2F8.png?alt=media" alt="Four examples of regulatory signs for prohibited access restrictions: No motor vehicles; No motor vehicles except solo motorcycles; No solo motorcycles, and No towed caravans."><figcaption><p>Examples of prohibited access restrictions which will be included in OS MasterMap Highways Network.</p></figcaption></figure>

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FLYz13KTMDWxOeyB5Dfgw%2F9.png?alt=media" alt="Two examples of regulatory signs for access limited for use by particular classes of vehicle: Buses and cycles only, and Trams only."><figcaption><p>Examples of 'access limited to' access restrictions which will be included in OS MasterMap Highways Network.</p></figcaption></figure>


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.os.uk/os-downloads/products/transport-network-portfolio/os-mastermap-highways-network-fundamentals/os-mastermap-highways-network-overview/feature-types/access-restrictions-present-in-rami-product.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 `build a script that syncs our docs to a CMS` 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.