> 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/street-lights.md). # Street lights Advice on how you can make the most of the data provided by the Street Light Feature Type. **Street Light Feature Type definition:** A point representation of a pole mounted light which is positioned to artificially illuminate sections of a road or path. [Street Light](/osngd/data-structure/transport/transport-features/street-light.md) features are used to identify the location of pole-mounted street lights. Street Light Presence attribution is available against 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 to indicate how well-lit individual Road Link and Path Link features. {% columns %} {% column %}

Example visualisation showing Street Light features and their attribution. A background map has been included to provide context.

{% endcolumn %} {% column %}

Visualisation showing Street Light coverage on Road Links and Path Links and how well-lit they are (using the Presence of Street Light Coverage attribute).

{% endcolumn %} {% endcolumns %} There are some [known limitations for street light data](/osngd/using-os-ngd-data/os-ngd-transport/street-lights/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/street-lights.md?ask=&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.