> 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/cycle-lanes.md).

# Cycle lanes

Advice on how you can make the most of the data provided by the Cycle Lane Feature Type.

## Introduction

**Cycle Lane Feature Type definition**: A linear feature that describes a cycle lane or cycle track and its relationship to the road or path network.

A cycle lane is defined as a section of road or path that is designated for cyclists, either segregated by a physical feature, identified by painted or other signage, or identified by a different colour of tarmac or surface type.

{% hint style="info" %}
Please note, the [Cycle Lane Feature Type](/osngd/data-structure/transport/transport-network/cycle-lane.md) represents designated cycling infrastructure, **not cycle routes**; therefore, routes that are part of the National Cycle Network are not captured as Cycle Lane features unless designated infrastructure is present that meets the criteria above.
{% endhint %}

<figure><img src="https://170091638-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0pZjHxkAvY7Mn6TqFBMD%2Fuploads%2FKPRxsmsbDMForIiTx4NQ%2FCycleLanes_Circle-01%20(1).png?alt=media&amp;token=0abd77be-ce40-4f20-b618-39ad58252260" alt="Example map showing Cycle Lane features. Background map included for context." width="563"><figcaption><p>Example map showing Cycle Lane features. Background map included for context.</p></figcaption></figure>

## Use cases and applications

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

* Planning cycle routes for active travel
* Asset management of cycle infrastructure
* Monitoring Cycle Network length and connectivity and conducting gap analysis
* Supporting road safety analysis
* Assessing the availability of safe cycling routes to access public services

## Data provision

Cycle lane data are provided in two ways:

* The [Cycle Lane Feature Type](/osngd/data-structure/transport/transport-network/cycle-lane.md) in the OS Transport Network Collection
* Attribution on the [Road Link](/osngd/data-structure/transport/transport-network/road-link.md) and [Path Link](/osngd/data-structure/transport/transport-network/path-link.md) Feature Types 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:

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