> For the complete documentation index, see [llms.txt](https://docs.os.uk/osngd/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/osngd/using-os-ngd-data/os-ngd-transport/bus-lanes.md).

# Bus lanes

## Introduction

**Bus Lane Feature Type definition**: A linear feature that describes a bus lane and its relationship to the road network.

A bus lane is defined as a section of road that is segregated by a physical feature or painted section of road that indicates primary usage for buses; this can include Guided Busways and Bus Gates.

{% hint style="info" %}
Please note, the [Bus Lane Feature Type](/osngd/data-structure/transport/transport-network/bus-lane.md) represents designated bus lane infrastructure and not bus routes.
{% endhint %}

<figure><img src="/files/teYf5MuJ7QZR6wRULfl8" alt="Example map showing Bus Lane (red solid lines) and Road Link (blue dashed lines) features. Background map included for context." width="563"><figcaption><p>Example map showing Bus Lane and Road Link features. Background map included for context.</p></figcaption></figure>

## Use cases and applications

Bus lane data support a variety of use cases and applications:

* Planning and managing the impact of street works
* Asset management of bus lane infrastructure
* Supporting transport planning and improving bus services to help citizens access public services
* Supporting understanding of where bus lanes can extend the provision of cycling routes for active travel

## Data provision

Bus lane data are provided in two ways:

* The [Bus Lane Feature Type](/osngd/data-structure/transport/transport-network/bus-lane.md) in the OS Transport Network Collection
* Attribution on the [Road Link Feature Type](/osngd/data-structure/transport/transport-network/road-link.md) in the OS Transport Network Collection

## What you'll find in this sub-section

The following sub-pages give more detailed information about the above representations and how they can be used to allow you to decide which one best suits your use case:

* [Bus Lane Feature Type](/osngd/using-os-ngd-data/os-ngd-transport/bus-lanes/bus-lane-feature-type.md)
* [Road Link attribution](/osngd/using-os-ngd-data/os-ngd-transport/bus-lanes/road-link-attribution.md)
* [How bus lane data are created](/osngd/using-os-ngd-data/os-ngd-transport/bus-lanes/how-bus-lane-data-are-created.md)
* [Known limitations](/osngd/using-os-ngd-data/os-ngd-transport/bus-lanes/known-limitations.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 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/osngd/using-os-ngd-data/os-ngd-transport/bus-lanes.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.
