Impervious Surface Update & Recovery

A Python and ArcGIS workflow for updating enterprise and hosted impervious-surface datasets, with verified backups, staged validation, controlled updates, and recovery reporting.

Why it matters

Updating shared GIS data can fail partway through. Backups and checks help determine what changed and what needs recovery.

My contribution

I built a workflow to back up existing data, check replacement data, update the enterprise geodatabase and hosted layer, and report each outcome.

Result: Reports whether each destination updated, recovered, or needs inspection.

Tools

  • Python
  • ArcPy
  • ArcGIS Pro
  • Enterprise Geodatabases
  • ArcGIS Online
  • PowerShell
  • Automated Testing

The latest recovery and incremental SDE changes still need controlled live testing.

Workflow and validation

The workflow backs up and validates data, updates the enterprise geodatabase and hosted layer independently, then checks each result. Unexpected enterprise changes after a save are left for inspection to preserve other edits. Hosted failures can trigger backup restoration, which must pass verification.

263 offline tests passed using simulated GIS services. The latest recovery safeguards and incremental SDE updates still require controlled live integration testing.

Technical details

GIS dataset updates and recovery

Failed updates and concurrent edits can leave shared GIS datasets incomplete or inconsistent.

  • Check fields, record counts, and geometry before updating. Recheck the destination for changes before writing.
  • Verify attributes after updating. Enterprise geometry is compared by shape; hosted geometry checks use counts and total area, not individual shape equality.
  • Keep backups and recovery reports. Hosted reloads can briefly expose an empty or partially loaded layer.

Image viewer

100%