1 / 20

Compiling and Developing Emergency Data for Use in Drought Response

Compiling and Developing Emergency Data for Use in Drought Response. Aaron Cuthbertson and Christina Boggs. Overview. Background/Intro Process Services Next Steps. Background/Intro. Deciding we need a path. Enterprise GIS at DWR. We have infrastructure, we don’t have workflows.

brandi
Download Presentation

Compiling and Developing Emergency Data for Use in Drought Response

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Compiling and Developing Emergency Data for Use in Drought Response Aaron Cuthbertson and Christina Boggs

  2. Overview • Background/Intro • Process • Services • Next Steps

  3. Background/Intro Deciding we need a path

  4. Enterprise GIS at DWR We have infrastructure, we don’t have workflows. "Lost in the forest, again" by Des D. Mona Some Rights Reserved - Link

  5. From Foraging to Forging (a path) • Historically, obtaining spatial data at DWR = foraging • Infrastructure now in place for Enterprise GIS data stores • Workflows are theoretical; need to be put into practice

  6. From Foraging to Forging (a path) • REMOVE the ‘A’! Foraging -> Forging • There is no ‘A’ in Enterprise GIS! • (Unless you spell out ‘Geographic Information System’, in which case my metaphor breaks down, so don’t)

  7. Drought Emergency Drives Need "Drought" by Ewan Bellamy Some Rights Reserved - Link

  8. Dataset Background • Locations of water ‘agencies’ needed to understand drought impacts • What do we mean by water agency? • There are a variety of sources • CDPH • USBR (many) • Program-specific (many) • No single data source has everything.

  9. Process Where should the path go?

  10. Design Decision: Better to have stripped down spatial data and robust tabular data.

  11. Process: Tabular WARNING: OVERSIMPLIFICATION AHEAD! • Compiled 9 datasets • Normalized Agency Names

  12. Process: Spatial • Problem: One agency, many polygons • Factors to consider • Solution: Prioritization

  13. Process: Metadata • This was rough. • ArcGIS Desktop / ArcGIS Catalog Metadata Editor • ArcGIS GeoPortal for Server • XML Editing • ArcGIS GeoPortal for Server • ArcGIS Desktop / ArcGIS Catalog Metadata Editor • Built a VBA tool

  14. Services Cutting the path

  15. Services • Mid-stream we’re switching from Oracle to SQL Server. • Internal Enterprise Geodatabase • Drought mandates data sharing • Useful sharing • Spatial + Tabular

  16. Next Steps Walking the path

  17. Next Steps • Keep editing • Eat the dog food • Make other deliverables, stay current. • Urban WaterManagement Plans • Agricultural Water Management Plans • Drought Declarations

More Related