aaron cuthbertson and christina boggs. 1.background/intro 2.process 3.services 4.next steps
TRANSCRIPT
Compiling and Developing Emergency Data for Use in Drought ResponseAaron Cuthbertsonand Christina Boggs
Enterprise GIS at DWRWe have infrastructure, we don’t have workflows.
"Lost in the forest, again" by Des D. Mona
Some Rights Reserved - Link
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
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)
Drought Emergency Drives Need
"Drought" by Ewan BellamySome Rights Reserved - Link
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.
Process: Metadata• This was rough.
1. ArcGIS Desktop / ArcGIS Catalog Metadata Editor2. ArcGIS GeoPortal for Server3. XML Editing4. ArcGIS GeoPortal for Server5. ArcGIS Desktop / ArcGIS Catalog Metadata Editor
• Built a VBA tool
Services• Mid-stream we’re switching from Oracle to SQL
Server.• Internal Enterprise Geodatabase• Drought mandates data sharing• Useful sharing• Spatial + Tabular
Next Steps• Keep editing• Eat the dog food• Make other
deliverables, stay current.• Urban Water
Management Plans• Agricultural Water
Management Plans• Drought Declarations