What was built Five Python-based GeoAI spatial analysis pipelines — covering school accessibility, weather vulnerability, multi-hazard emergency response, healthcare access, and urban mobility — each deployable across any geography without rebuilding from scratch.
Who it was for Analysts and organizations that need consistent spatial methodology applied at scale — without restarting the process for each new city or region.
Why it mattered Accessibility analysis methodology doesn't scale when run manually. Automating the spatial pipeline in Python and Jupyter means the same rigorous analytical framework runs reproducibly across Portland, Tokyo, São Paulo, and beyond.

The Challenge

Accessibility analysis at scale has a structural problem: the methodology that works for one city has to be rebuilt manually for the next. These five systems address that directly — each one combines Python, open-source geospatial libraries, and OpenStreetMap data into a structured pipeline that performs the spatial query, processes the dataset, runs the analysis, and produces the output for any geography it's pointed at.

Five systems were built as part of the LLM Agentic GeoAI Mastery certification: School Accessibility (Portland), Weather Vulnerability (Bristol), Multi-Hazard Emergency Response (Tokyo), Healthcare Accessibility (São Paulo), and Urban Accessibility (multi-city). Each required defining the analytical framework first — what constitutes an accessibility gap, what datasets are required, what the output needs to show — before any code was written. The result: a set of scalable pipelines that enable consistent accessibility analysis across any target geography without rebuilding from scratch.

The practical challenge was real: getting Python environments, Jupyter Notebook libraries, and AI-augmented spatial pipelines to run reliably required systematic dependency management and debugging across multiple tool stacks. That configuration work is the bottleneck that separates analysts who can run these workflows from those who only read about them.

These systems extend core GIS capability — they don't replace the analytical judgment that goes into defining the spatial question, selecting appropriate methods, and validating the output. That judgment is still the job.

The Five Systems

Portland, OR
School Accessibility Analyzer
Bristol, UK
Weather-Based Vulnerability System
Tokyo, Japan
Multi-Hazard Emergency Response Command
São Paulo, Brazil
Healthcare Accessibility Intelligence
Multi-city
Urban Accessibility Gap Analyzer

Traditional GIS vs. Agentic GIS

Traditional GIS
  • Manual, linear workflow
  • Analyst loads each dataset
  • One question, one output
  • Re-run from scratch per city
  • Analysis locked to analyst's time
Agentic GIS
  • Dynamic, adaptive pipeline
  • System discovers datasets
  • Scales to any geography
  • Consistent methodology across cities
  • Analysis runs on demand

"Spatial systems that adapt to the question — not just produce a map when you manually load the data — change what's achievable when consistent methodology needs to reach multiple geographies at once."

Process

  1. 1
    Research Studied agentic GIS architecture; identified OpenStreetMap datasets and geospatial libraries appropriate for each accessibility problem type.
  2. 2
    Data Prep Configured Python environments and Jupyter dependencies; sourced OSM data for Portland, Bristol, Tokyo, São Paulo; structured spatial queries.
  3. 3
    GIS Work Built 5 agentic spatial systems — school accessibility scoring, weather vulnerability assessment, multi-hazard response coordination, healthcare accessibility, urban accessibility gap analysis.
  4. 4
    Output 5 complete systems; agentic pipelines adaptable across geographies; certified February 2026.
Principle 01
Structure before software

Even in agentic workflows — where the system does much of the execution automatically — the analytical framework has to be established first. What question is the system answering? What does a valid output look like? What failure modes need to be caught? The structure comes before any code runs.