geospatial-engineering

Geospatial / GIS engineering team — 2 agents for the engineering of location data. The geospatial-data-engineer owns spatial data modeling and storage (PostGIS, GiST/SP-GiST indexes, SRID and projection hygiene — EPSG:4326 vs 3857, geometry vs geography), spatial SQL and analysis (ST_ functions, spatial joins, nearest-neighbor, buffers), and geospatial pipelines (GDAL/OGR, geocoding, routing engines like OSRM/Valhalla). The mapping-visualization-engineer owns the serving and visualization layer (vector tiles/MVT, pg_tileserv/Martin/Tegola, MapLibre/Mapbox GL styling, the GeoJSON-vs-vector-tile tradeoff). 4 skills, a projection decision tree, a dated 2026 stack reference, 2 templates, 3 best-practice rules, and 1 advisory hook that flags geometry-without-SRID and degree-distance smells. Seams: warehouse/ELT → data-platform; OLTP schema → database-engineering; map UI → frontend-engineering. Always store an SRID; index geometry with GiST; vector tiles over GeoJSON at scale. Requires ravenclaude-core@>=0.7.0.