open-gis
Installation
SKILL.md
Open GIS Toolkit
Production-grade geospatial workflows with an open-first stack and pragmatic hosted/SaaS choices when global scale, latency, SLA, or data quality makes local processing a poor fit. Cloud-native by default: STAC for discovery, GeoParquet + COG + PMTiles for storage, DuckDB and PostGIS for compute, MapLibre and Martin for delivery.
Modules — read the relevant reference(s) before starting work
| If the task involves... | Read |
|---|---|
| Finding or sourcing data (OSM, Overture, Sentinel, Landsat, building footprints, regional portals, STAC catalogs, MCP-based discovery) | references/data-sources.md |
| Choosing local processing vs online/hosted/SaaS services for global or continental scale; basemaps, elevation, routing, geocoding, place search, postcode lookup APIs | references/services-and-scale.md |
| Choosing a format, converting between formats, or any CRS / projection / EPSG question | references/formats-and-crs.md |
| Running GDAL/OGR, GeoPandas, xarray, DuckDB, PostGIS, or PDAL — the actual processing | references/processing.md |
| Vector analytics, raster analytics, terrain/hydrology, network analysis, point cloud workflows | references/analytics.md |
| Tile generation (PMTiles, MVT), tile servers (Martin, TiTiler), web map rendering (MapLibre, deck.gl) | references/web-delivery.md |
| QGIS desktop, QGIS plugin ecosystem, QGIS MCP, PyQGIS scripting, Processing toolbox | references/qgis.md |
| Reproducibility, validation, license attribution, tile smoke tests, deployment checks | references/validation-and-ops.md |
For simple one-shot questions (single CRS conversion, one ogr2ogr invocation), the relevant reference alone is usually enough. For multi-stage pipelines, read data-sources.md and processing.md together; for end-to-end "from raw data to web map" tasks, also read web-delivery.md.