> 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/geographic-data-visualisation/guide-to-data-visualisation.md). # Guide to data visualisation

	Cover image
Introduction to data visualisation	London_Galaxy_v2.JPG	Introduction to data visualisation
GeoDataViz design principles	principles.png	GeoDataViz design principles
Types of visualisation	Data-Cityverve-Parking-Dashboard-1-2017.png	Types of visualisation
Thematic mapping techniques	3 (9).png	Thematic mapping techniques
Data visualisation critique	Data-OS-Routes-Pink-1-2017.png	Data visualisation critique
Accessible data visualisation	OS-routes-yellow.png	Accessible data visualisation
Ethical data visualisation	Data-Blue-GB-1-2017.png	Ethical data visualisation
Software	Software developer.jpg	Software
Data	Obl3Dmesh+networks_overview.jpg	Data

--- # 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/geographic-data-visualisation/guide-to-data-visualisation.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.