Geospatial Ops
Geospatial Ops covers the practical work needed to keep Explorer locations, geometry joins, map overlays, and identifier decisions understandable across delivery conversations.
Active surfaces
| Surface | Notes |
|---|---|
| CSTAR entity data | Disclosure entities are mapped into the Explorer data model. |
| Overture geometry | Static data exports combine CSTAR entities with Overture geometry data for replication. |
| GERS IDs | Adoption and lookup decisions are tracked as part of the broader data-platform scope. |
| Hazard layers | The backend exposes Google Earth Engine hazard metadata and tile URLs. |
| Map experience | Frontend search, maps, and location detail pages depend on consistent geometry and layer behavior. |
Open coordination points
- Keep raw entity identifiers, geometry identifiers, and display names traceable in data handoffs.
- Document whether a map-layer change affects backend layer config, frontend display copy, or both.
- Separate confirmed data contracts from assumptions about upstream disclosure exports.
- Track any stakeholder-facing wording needed to explain map scale, jurisdiction coverage, or hazard-layer limitations.