Crossing the Stack: Python for Spatial Data and the Geospatial Web

This course is designed for a very specific learner: someone who already thinks in components and endpoints, who has fought with npm dependency hell and won, and who now needs Python to become a first-class tool in their spatial toolkit. Rather than teaching programming from scratch, every concept is framed as a translation — from JavaScript idioms to Pythonic patterns, from Express middleware to FastAPI dependencies, from Supabase queries to PostGIS spatial SQL. The course arc tells a story of building outward from the language itself to a complete spatial data stack, culminating in a full-stack application where a Python API serves geospatial data to a React or Remix frontend. Pedagogically, this course is built on five pillars of learning science. Spacing ensures that early concepts like CRS handling and Shapely geometry don't appear once and vanish — they resurface with increasing sophistication in every subsequent chapter. Interleaving means that a chapter on FastAPI doesn't just cover API design; it forces you to recall GeoPandas serialization, PostGIS query patterns, and CRS transformation simultaneously. Retrieval practice is baked into every chapter through prediction exercises where you guess the Python equivalent of familiar JavaScript patterns before seeing the answer. Concrete examples are drawn from real GIS workflows — watershed analysis, parcel data management, transit routing, wildfire perimeter tracking — never abstract foo-bar nonsense. And dual coding ensures that every spatial concept is both described in prose and visualized through interactive widgets that let you manipulate geometries, explore projections, and trace request flows. The course acknowledges platform reality head-on: GDAL installation is different on Windows and Mac, arcpy is only available on Windows with ArcGIS Pro, and the open-source stack runs everywhere. Where tools diverge, both paths are shown. Where arcpy offers a familiar alternative to an open-source tool, it gets a focused comparison. The goal is not to pick a side in the proprietary-vs-open-source debate, but to make you fluent enough in Python's spatial ecosystem that you can move between both worlds with confidence.

10 Chapters · 80 Sources

Crossing the Stack: Python for Spatial Data and the Geospatial Web

Classes

Sources

Materials