1. Aaron Cuthbertson and Christina Boggs

2. 1.Background/Intro 2.Process 3.Services 4.Next Steps

3. Deciding we need a path

4. We have infrastructure, we don’t have workflows. "Lost in the forest, again" by Des D. Mona Some Rights ReservedSome Rights Reserved - LinkLink

5. 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. 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" by Ewan Bellamy Some Rights ReservedSome Rights Reserved - LinkLink

8. 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. Where should the path go?

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

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

13. This was rough. 1.ArcGIS Desktop / ArcGIS Catalog Metadata Editor 2.ArcGIS GeoPortal for Server 3.XML Editing 4.ArcGIS GeoPortal for Server 5.ArcGIS Desktop / ArcGIS Catalog Metadata Editor Built a VBA tool

14. Cutting the path

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

17. Walking the path

18. Keep editing Eat the dog food Make other deliverables, stay current. Urban Water Management Plans Agricultural Water Management Plans Drought Declarations