I’m tightening up our data governance and need solid, reusable templates for lifecycle documentation (ingest → QA/QC → publish → archive) across ArcGIS Pro 3.2 and PostGIS 15… If you’ve got SOPs or examples for versioning, naming, and metadata (ISO 19115/STAC) that scale to about 2 TB with quarterly releases, I’d appreciate pointers.
(ISO 19115/STAC) that scale to about 2 TB with quarterly releases, I’d appreciate We keep a dataset.yml as the source of truth and a publish script that spits ArcGIS Pro XML and STAC JSON (pystac), tag each drop 2025Q1 with semver only for schema changes, and run PostGIS DDL via Flyway so the SOP is migrate → Pro QA Task → publish… Minor gotcha: Pro 3.2 sometimes drops ISO extents on export, so we regenerate from YAML; Flyway’s here: https://flywaydb.org.
I’ve run into this too — one small tweak that paid off was writing the expected outcome before touching the settings.