> For the complete documentation index, see [llms.txt](https://docs.os.uk/more-than-maps/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/more-than-maps/routing.md). # Routing This page contains a series of step through tutorials and articles relating to routing using OS data in GIS Software More information about using GIS software can be found [on the main OS website](https://www.ordnancesurvey.co.uk/business-government/tools-support/gis).

	Cover image
Basic Routing with OS Open Data and QGIS	routing_cover.png	Basic routing with OS Open Data and QGIS
Walktime analysis using OS Multi-modal Routing Network and QGIS	mrn-routing-qgis-output.png	Walktime analysis using OS Multi-modal Routing Network and QGIS
Routing with pgRouting	osmm-highways-network-place1.jpg	Routing with pgRouting
Safe Routes to Schools	safe-routes-schools-rag-green.png	Safe Routes to Schools
Visualising a road gradient using a Digital Terrain Model	gradient_DTM_13.png	Visualising a road gradient using a Digital Terrain Model
Visualising a road gradient using OSMM Highways	Road_Profile_1.png	Visualising a road gradient using OSMM Highways
Guide to routing for the Public Sector	Highways_and_paths.png	Guide to routing for the Public Sector

--- # 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/more-than-maps/routing.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.