A – Experienced: L5 + GeoHarness Tiers 1, 2 and 3
ACADEMIC ADDENDUM | READ WITH THE ORIGINAL SYLLABUS
Curriculum route / L5+GH
38 modules · 254 topics
Programme focus
Academic addendum | Read with the original syllabus
Programme snapshot
Start with the essentials.
Everything you need to decide whether this is the right course to begin with.
- Duration
- 6 months (26 weeks)
- Proposed delivery matrix
- 624 hours
- Entry
- Entry assessment
The programme
Overview
Academic addendum | Read with the original syllabus
Learning domains
Focus areas
01
Program details
- The source L5 program requires advanced GIS/development competence. L2 alone does not satisfy its software-engineering prerequisites. Applicants receive an entry assessment; the integrated pathway uses a structured coding/API bridge and may require preparatory work for students who do not meet the required standard.
02
Integrated Pathways: Curriculum-Preservation Statement
- New optional six-month delivery design. All source course descriptions, teaching topics and specialist offerings are retained in the original pages.
- No replacement or shortening of the published syllabuses. This supplement packages existing L2, L5 and GeoHarness instruction into two integrated six-month routes. The existing standalone three-tier GeoHarness designation is kept; the final tier is integrated with L5 rather than deleted.
- L2 Professional GIS Analysis · Where to find full content: Original detailed brochure pp. 5–7 · Preservation rule: 10 existing modules; 120 source hours
- L5 Full-Stack GIS & GeoAI Developer · Where to find full content: Original detailed brochure pp. 22–25 · Preservation rule: 16 existing modules; no exclusions
- GeoHarness AI Agentic GIS · Where to find full content: Original detailed brochure pp. 26–29 · Preservation rule: Original g00a/g00b and g01–g20; three tiers
03
Experienced A: Six-Month Hour Allocation
- L5 + GeoHarness AI. The L2 block is replaced by a deeper supervised project studio; L2 content is not represented as included.
- 1 · L5: 52 · GeoHarness: - · Bridge: 12 · Integration studio: 40 · Assess.: - · Total: 104
- 2 · L5: 64 · GeoHarness: - · Bridge: 12 · Integration studio: 28 · Assess.: - · Total: 104
- 3 · L5: 80 · GeoHarness: - · Bridge: - · Integration studio: 16 · Assess.: 8 · Total: 104
- 4 · L5: 52 · GeoHarness: 30 · Bridge: - · Integration studio: 22 · Assess.: - · Total: 104
- 5 · L5: 26 · GeoHarness: 50 · Bridge: - · Integration studio: 28 · Assess.: - · Total: 104
- 6 · L5: 6 · GeoHarness: 65 · Bridge: - · Integration studio: 26 · Assess.: 7 · Total: 104
- Total · L5: 280 · GeoHarness: 145 · Bridge: 24 · Integration studio: 160 · Assess.: 15 · Total: 624
- Month-4 milestone for A: 196/280 planned L5 hours (70%) have been scheduled in Months 1–3; Tier 1 GeoHarness begins in Month 4. The 160-hour studio is applied practice, not 160 hours of additional, newly named syllabus modules.
04
Additional development and portfolio studios
- Reinforce existing L5 skills through API integration, database performance checks, web-map usability and practical GeoAI integration.
- Give experienced learners more time to implement and validate GeoHarness tool interfaces, edge cases, access controls and project handoffs.
- Build a reviewable portfolio and the final integrated system using the unchanged L5 and g00–g20 topics; no substitute certificate replaces the required module assessments.
05
Curriculum Crosswalk: Original L5
- Original module titles are preserved below. Month groupings are scheduling decisions, not changes to the module learning outcomes.
- Scheduling order is adjusted for agent readiness; the detailed learning outcomes within the original L2/L5 modules are unchanged. Some modules intentionally run across months rather than being shortened.
06
Curriculum Crosswalk: All GeoHarness Lessons
- The original three GeoHarness tiers and every Version 3 lesson remain included; the 65-hour Tier 3 extends full-stack learning into the GIS MCP and system capstone.
- Source Tier 1 uses g00a OR g00b as the fast-track entry. Both alternatives remain provided, but a learner normally takes the appropriate one. The original detailed source places g11 before the Tier 2 heading; this supplement retains that placement rather than silently renumbering.
- Stage 3 practical scope: The original Tier 3 is 60–80 hours, not merely two classroom demonstrations. The planned 65 hours include MCP server design, g19 tool exposure, g20 full-system integration, validation, capstone implementation, testing and handover within the existing full-stack L5 environment.
07
Learning milestones and assessment gates
- Recommended implementation controls for the new integrated package; these are additive delivery and evaluation arrangements.
- Entry · Requirement: GIS and software competence diagnostic; select Pathway A or B, and prescribe prerequisite bridge where necessary.
- M3 · Requirement: Working geospatial Python tools + spatial database/API demonstration. Confirm L5 readiness and ~70% scheduled hours.
- M4 · Requirement: Tier 1 certified builder exercise: spatial prompts, tool dispatcher, permissions, planning, memory and recovery.
- M5 · Requirement: Tier 2 engineering exercise: reliable task queues, asynchronous processing, monitoring, agent teams and spatial isolation.
- M6 · Requirement: Tier 3/MCP and integrated full-system capstone; separate L2 (where applicable), L5 and GeoHarness reviews.
08
Illustrative integrated capstone – crop-monitoring decision support
- Ingest prepared EO data, sensor observations or GIS features; document CRS, provenance and quality assumptions.
- Use existing L2 methods and L5 software tooling to develop indices/analyses, database services, APIs and a reviewable WebGIS output.
- Implement approved GeoHarness tool schemas, guards, execution traces, planning, specialist handoffs, monitoring and MCP exposure.
- Create a final system demonstration with reproducible runs, error-handling tests, assessment rubric and documented human approval points.
- Governance: Autonomous systems proposed in student work should be limited to authorised data and tools. High-impact operational decisions require human review; spatial anomalies are not treated as confirmed ground truth without validation.
09
Commercial and operational notes
- Six months means the approved 26-week cohort schedule; 624 hours is a planned maximum scheduled capacity, including labs, portfolio studio and assessment.
- Standalone L2, L5 and the original three-tier GeoHarness offerings stay available and keep their existing contents.
- Certification reflects completed work and assessment results; internships or jobs are not automatically guaranteed.
The complete syllabus
Curriculum
Search the syllabus, choose a module, and review its topics without losing your place.
Modules
38
Topics
254
Module 01
L5 · 01 Python for Geospatial Software Development [M1]
- Advanced Python01
- OOP02
- Virtual environments03
- Package management04
- GeoPandas, Shapely, Rasterio, GDAL05
- PyProj, PySAL06
- Spatial algorithms07
- Error handling and logging08
- Reusable packages09
- Git/version control10
Module 02
L5 · 02 Remote Sensing & Cloud Geospatial Processing [M1]
- Satellite-data APIs01
- GEE architecture02
- ImageCollections03
- Cloud masking04
- Composites05
- Spectral indices06
- Classification07
- Change detection08
- Time series09
- Automated EO pipelines10
Module 03
L5 · 03 Advanced GEE Python Development [M2]
- Earth Engine Python API01
- geemap02
- Automated AOI processing03
- Batch analysis04
- Multi-location processing05
- Time-series extraction06
- Automated exports07
- GEE to PostGIS08
- GEE to WebGIS09
Module 04
L5 · 04 GeoAI & Spatial Machine Learning [M2]
- GeoAI architecture01
- Spatial ML02
- Feature engineering03
- Classification, regression, clustering04
- Object detection05
- Semantic segmentation06
- Change detection07
- Spatial prediction08
- Training/validation09
- Inference pipelines10
- AI results to GIS layers11
- GeoAI service integration12
Module 05
L5 · 05 WebGIS Foundations [M2]
- WebGIS architecture01
- Client-server02
- HTTP/HTTPS03
- REST04
- JSON/GeoJSON05
- HTML, CSS, JavaScript06
- Leaflet07
- Mapbox08
- Interactive maps09
- Basemaps10
- Layers11
- Pop-ups12
- User interaction13
Module 06
L5 · 06 Advanced PostGIS & Spatial Database Engineering [M1–M2]
- PostgreSQL architecture01
- PostGIS02
- Advanced Spatial SQL03
- Geometry management04
- Spatial indexing05
- Query optimization06
- Normalization07
- Views/materialized views08
- Triggers and functions09
- Multi-user databases10
- Time-series spatial data11
- TimescaleDB12
Module 07
L5 · 07 GeoServer & Geospatial Middleware [M3]
- GeoServer architecture01
- PostGIS publishing02
- WMS/WFS/WMTS03
- REST configuration04
- SLD05
- Dynamic styling06
- Tile caching07
- Authentication and permissions08
- Secured services09
- Optimization10
Module 08
L5 · 08 Backend Development & GIS APIs [M3]
- Backend architecture01
- REST APIs02
- FastAPI03
- Django and GeoDjango04
- Spatial API design05
- GeoJSON endpoints06
- CRUD07
- Authentication and API security08
- PostGIS integration09
- GeoServer integration10
- File upload/processing11
- Asynchronous geospatial jobs12
Module 09
L5 · 09 Full-Stack WebGIS Application Development [M3–M4]
- Frontend/backend integration01
- Interactive maps02
- Layer controls03
- Spatial search04
- Attribute queries05
- Drawing/editing06
- Map-based forms07
- Filtering08
- Charts/dashboards09
- Authentication10
- Role-based access11
- Database-driven WebGIS12
- Deployment-ready applications13
Module 10
L5 · 10 3D WebGIS & Geospatial Visualization [M4]
- 3D GIS01
- CesiumJS02
- 3D Tiles03
- Terrain04
- 3D buildings05
- Point clouds06
- Potree07
- LiDAR web visualization08
- BIM visualization09
- Revit/BIM integration10
- Large-scale 3D data11
Module 11
L5 · 11 Digital Twin for Geospatial Systems [M4]
- Digital Twin concepts01
- Physical-to-digital assets02
- GIS spatial foundation03
- Asset IDs/relationships04
- IoT, sensors, MQTT05
- Real-time ingestion06
- Time-series databases07
- PostGIS + TimescaleDB08
- Real-time dashboards09
- Event monitoring10
- Alerts11
- Historical/live-state analysis12
- Simulation concepts13
Module 12
L5 · 12 IoT + Real-Time Geospatial Analytics [M5]
- IoT architecture01
- Sensor-to-server communication02
- GPS streams03
- Environmental sensors04
- Asset telemetry05
- Streaming data06
- Spatial-event processing07
- Geofencing08
- Threshold alerts09
- Location events10
- Real-time maps11
- Time-series visualization12
Module 13
L5 · 13 Mobile GIS Application Development [M4–M5]
- React Native01
- Expo02
- Mobile architecture03
- Map components04
- GPS and device location05
- Field survey forms06
- Camera07
- Geotagged photos08
- Offline collection09
- Local storage10
- API synchronization11
- PostGIS backend12
- Field-to-cloud GIS13
Module 14
L5 · 14 Cloud Deployment & DevOps for GIS [M3–M5]
- Cloud GIS architecture01
- Linux02
- Docker03
- Containerized PostGIS and GeoServer04
- Backend deployment05
- Environment configuration06
- Reverse proxy07
- SSL/HTTPS08
- GitHub09
- CI/CD10
- Logging11
- Backup12
- Scalability13
- Production deployment14
Module 15
L5 · 15 Enterprise GeoAI Integration [M5]
- AI inference APIs01
- Automated imagery processing02
- Model to WebGIS03
- GeoAI + PostGIS04
- GeoAI + GeoServer05
- GeoAI + Digital Twin06
- Scheduled inference07
- Alerts08
- Human validation09
- Updating spatial databases from AI10
Module 16
L5 · 16 Full-Stack Geospatial System Architecture [M5–M6]
- Requirement analysis01
- Database architecture02
- Backend architecture03
- Frontend architecture04
- API architecture05
- GIS server architecture06
- AI-service architecture07
- Mobile architecture08
- Security09
- Scalability10
- System integration11
- Production workflow design12
Module 17
GH · g00a: AI Fast Track [M4]
- Needs basic Python and familiarity with QGIS or ArcGIS01
- no prior agent experience02
- the first spatial agent loop, where the model reasons while the harness executes tools03
- You can build: a minimal tool-calling spatial agent04
Module 18
GH · g00b: GIS Fast Track [M4]
- Needs comfort with Python and Pandas/JSON01
- no GIS background02
- vector, raster, CRS, GeoJSON and core GIS operations03
- You can build: tool-ready Python GIS functions for agent use04
Module 19
GH · g01: Spatial Loop [M4]
- Needs the first entry point (g00a or g00b)01
- a spatial system prompt and a persistent tool-call loop02
- You can build: a project-aware GIS assistant03
Module 20
GH · g02: Spatial Tools [M4]
- Needs g0101
- typed tool schemas and a dispatcher instead of free-form code execution02
- You can build: a reliable tool catalogue of GeoPandas functions03
Module 21
GH · g03: Spatial Permissions [M4]
- Needs g0201
- permission guards, coordinate validation and CRS enforcement before execution02
- You can build: protected GIS tooling that rejects unsafe requests03
Module 22
GH · g04: Spatial Hooks [M4]
- Needs g0301
- pre- and post-tool hooks for validation, logging and cost tracking02
- You can build: a traceable, auditable GIS execution layer03
Module 23
GH · g05: Spatial Planning [M4]
- Needs g0401
- plan-first execution with explicit step tracking02
- You can build: a multi-step analysis pipeline with state tracking03
Module 24
GH · g06: Spatial Subagent [M4]
- Needs g0501
- orchestrator and subagent roles with structured GeoJSON handoff02
- You can build: a two-level architecture for spatial data acquisition03
Module 25
GH · g07: GIS Skills Library [M4]
- Needs g0601
- domain knowledge loaded on demand from markdown skill files02
- You can build: a reusable skills library for agent tasks03
Module 26
GH · g08: Spatial Context Management [M4]
- Needs g0701
- summaries of large raster and vector datasets so they fit in context02
- You can build: context-aware analysis for large geospatial datasets03
Module 27
GH · g09: Spatial Memory [M4]
- Needs g0801
- persistent memory so the agent reuses context across sessions02
- You can build: a follow-up-aware GIS assistant03
Module 28
GH · g10: Spatial System Prompt [M4]
- Needs g0901
- a system prompt built dynamically from memory and live WMS capabilities02
- You can build: a spatial assistant that updates with project state03
Module 29
GH · g11: Spatial Error Recovery [M4]
- Needs g1001
- topology errors, data-source fallback and graceful degradation02
- You can build: resilient spatial pipelines with fallback logic03
Module 30
GH · g12: Spatial Task System [M5]
- Needs g1101
- a dependency-aware task queue for multi-step spatial workflows02
- You can build: a task-based spatial processing engine03
Module 31
GH · g13: Background Spatial Tasks [M5]
- Needs g1201
- long spatial work run asynchronously with notifications and queues02
- You can build: a background pipeline for remote sensing or large analysis03
Module 32
GH · g14: Spatial Monitoring [M5]
- Needs g1301
- threshold-based monitoring, alerts and structured reports over time02
- You can build: event-driven monitoring and alerting for live geospatial conditions03
Module 33
GH · g15: Spatial Agent Teams [M5]
- Needs g1401
- analysis split across data, analysis and visualization agents with typed handoffs02
- You can build: a team-based spatial analytics workflow03
Module 34
GH · g16: Spatial Protocols [M5]
- Needs g1501
- GeoJSON validation at every boundary using protocol rules and decorators02
- You can build: contract-validated agent pipelines03
Module 35
GH · g17: Autonomous Spatial Agents [M5]
- Needs g1601
- a file-based queue and atomic task claiming for parallel workers02
- You can build: a distributed batch-processing system across many sites03
Module 36
GH · g18: Spatial Isolation [M5]
- Needs g1701
- each agent isolated in its own CRS workspace to prevent cross-contamination02
- You can build: sandboxed, CRS-aware execution environments03
Module 37
GH · g19: GIS MCP Plugin [M6]
- Needs g1801
- WFS data wrapped as MCP tools so Claude Code can discover and use them automatically02
- You can build: a reusable GIS tool server for Claude Code or other MCP clients03
Module 38
GH · g20: Full GeoAI System [M6]
- Needs all prior lessons, g00 to g1901
- a capstone that combines planning, memory, monitoring, protocols, teams and MCP02
- You can build: a production-style autonomous spatial AI system03