> 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/geodataviz-assets/30daymapchallenge.md). # #30DayMapChallenge The [#30DayMapChallenge](https://30daymapchallenge.com/) is the brainchild of Finnish cartographer Topi Tjukanov and is a daily cartography and data visualization challenge aimed at the spatial community.\ Every day throughout November a different theme is set and participants create a map or data visualisation based on that theme and share their results on social media using the #30DayMapChallenge hashtag. Every year staff at Ordnance Survey get involved and share our submissions via a virtual gallery.

		Cover image
#30DayMapChallenge 2021	https://labs.os.uk/public/30-day-map-challenge/2021/	2021.png
#30DayMapChallenge 2022	https://labs.os.uk/public/30-day-map-challenge/2022/	2022.png
#30DayMapChallenge 2023	https://labs.os.uk/public/30-day-map-challenge/2023/	2023 gallery.png
#30DayMapChallenge 2024	https://labs.os.uk/public/30-day-map-challenge/2024/	#30DayMapChallenge_2024 (1).png
#30DayMapChallenge 2025	https://labs.os.uk/public/30-day-map-challenge/2025/	#30daymapchallenge_2025.png

--- # 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/geodataviz-assets/30daymapchallenge.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.