# Known limitations There are some known limitations for cycle lane data: * **Completeness**: Cycle lanes have been captured from aerial imagery and therefore there are some limitations to completeness. Where features are not visible from aerial imagery, these will not be included unless they have been identified through other intelligence sources (for example, targeted ground surveying based on intelligence sources). In particular, the completeness of Unsegregated Shared Use Cycle Lanes will be lower as these features are typically indicated by blue signage at street level and don’t have clear designation that can be seen from aerial imagery. You can report any cycle lane omissions on the [OS Data Hub Error Reporting Tool](https://osdatahub.os.uk/apps/errors-and-omissions) for OS to investigate. * **Linking to the Road and Path Network**: The accuracy of the linking between Cycle Lane features and the Road and Path Network is dependent on the performance of an algorithm. In areas of complex network geometry (for example, at junctions or where cycle infrastructure jumps between the Road and Path Network) there are limitations to the accuracy of the linking algorithm. --- # Agent Instructions: 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: ``` GET https://docs.os.uk/osngd/using-os-ngd-data/os-ngd-transport/cycle-lanes/known-limitations.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.