> 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-routing-and-asset-management-information/os-mastermap-highways-network-routing-and-asset-management-information-technical-specification/routing-and-asset-management-feature-information.md).

# Routing and Asset Management feature information

The RAMI product contains the base road network and RAMI features, which reference back to the network. The base road network features are detailed in the Roads Technical Specification. The current specification focuses on RAMI.

RAMI has been categorised into the following themes:

* **Rights and Restrictions:** Defines properties that restrict, regulate or prohibit the use of the network by traffic such as turn restrictions, or access and use restrictions which may affect the allowable route for users.
* **Advisory Information:** These provide additional information that may affect a driver’s preferred choice of route or highlight potential hazards such as the presence of a toll, ford, or level crossing.
* **Asset Management:** Provides additional information to support the management of Highways Assets by Highways and Roads Authorities such as detailed physical characteristics relating to the asset (reinstatement), road maintenance responsibility, and whether it has any special designations

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2FTObpV2Si8Q0QszMp6E49%2F5.jpeg?alt=media" alt="Diagram of overview of routing and asset management information" width="563"><figcaption><p>Overview of Routing and Asset Management Information</p></figcaption></figure>

## Network referencing <a href="#id-3.1-network-referencing" id="id-3.1-network-referencing"></a>

RAMI is related back to features in the OS MasterMap Highways Network – Roads product using Network Referencing, through the networkRef attribute. All RAMI features extend the INSPIRE NetworkProperty class. This allows several types of Network Referencing to relate the RAMI to the relevant feature:

* **Network Reference:** This is used to relate the information to a *Street.*
* **Node Reference:** This is used to relate the information to a *RoadNode*.
* **Link Reference:** This is used to relate the information to a complete *RoadLink*.
* **Multiple Link Reference:** This is used to relate the information to more than one complete *RoadLink*.
* **Point Reference:** This is used when the information is related to a specific point along a *RoadLink*.
* **Linear Reference:** This is used to relate the information to a specific section of a *RoadLink*. This type of referencing is not used in the RAMI specification.

The different types of Network Referencing all extend the INSPIRE Network Reference data type.

In the INSPIRE specification, the networkRef is a voidable field. For all features in the RAMI specification, the networkRef will never be voided.

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2F77pL0gj01j1UeMclJtHw%2F6.jpeg?alt=media" alt="Diagram of INSPIRE network referencing model" width="563"><figcaption><p>INSPIRE Network Referencing Model</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 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-routing-and-asset-management-information/os-mastermap-highways-network-routing-and-asset-management-information-technical-specification/routing-and-asset-management-feature-information.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.