About Spatial Workflow

Spatial Workflow is written and maintained by a small team under the Spatial Workflow name. We build the guides, run their code, draw their figures and maps, and fix them when a library or a data source changes underneath them. Guides are signed by the team rather than by one person, because each one passes through several hands and checks before it is published.

What the site is for

Most GIS questions in Python are small and specific: why a spatial join returns nothing, which CRS to measure an area in, how to read a raster that will not fit in memory. The answers are usually scattered across library documentation, old forum threads and examples that run on toy data. Each of our 1,421 guides answers one such question — a concept, a task or an error — with code you can copy, run on real open data, and compare against the output on the page.

The guides are organised by topic, so a concept, the tasks that use it and the errors it causes sit together, and by learning path for reading in order.

How we work

Guides are drafted with an AI model and then run, checked against their own output and re-verified as libraries and sources change; nothing the draft claims is published without a run behind it. The full process, including what is checked automatically and how corrections are handled, is on how guides are made and checked. When a guide changes in a way a returning reader should know about, the change is listed under it with a date.

Get in touch

Mistakes, broken examples, data sources that have moved and suggestions all go to info@spatialworkflow.io; the contact page says what helps us act on them quickly.