1. Data Migration From Personal Geodatabaseto ArcServer

2. Dathen Strine Huntington County GIS Coordinator Ben Bond City of Huntington GIS Coordinator

3. In the beginning ESRI Licensing setup • 1 Advanced Concurrent • 1 Basic Concurrent • 13 Basic Single Use • 2 VBA • 2 ArcPad

4. In the beginning ESRI Licensing setup • Personal Geodatabases • 10 Offices with multiple databases

5. In the beginningScript World • Scripts for making copies • Scripts for deleting • Scripts for copies or copies • Script Errors

6. In the beginningScript World

7. In the beginningScript World

8. Meeting our needs • Eliminating Script Errors • Ending Department Locks • Better Control of Licensing • Better Connections to 3rd Party Software Vendors

9. Meeting our needs • ArcGIS Server Standard Enterprise • ArcGIS Standard Licenses • SQL Database Server

10. How our goal is reached • ArcGIS Server Standard Enterprise • Traded in Workgroup Server • 1 Advanced Concurrent Desktop • 5 Standard Concurrent Desktop • Traded in 4 Basic License • 5 Basic Concurrent Desktop • 3 Basic Single Use Desktop

11. How our goal is reached • Server Installation • The Schneider Corporation • Microsoft SQL Server Management Setup • Creating Users • Designing and Setting up SDE • Creating Privileges • Registering and Unregistering Versions

12. How Do we achieve? • Department Heads Support • ESRI Users Supporting upgrades • Quarterly GIS Meetings • Project Funded • New 911 Software requirements • FREP and Multi-Hazardous Plan • Community Data Usage • Daily Data Being Viewed by the Public from Beacon Website • County Commissioners, Councilman and Mayor Support

13. Project Management • Initiation complete • Planning and Definition • Inventory and inspection of all feature classes in the GeoDatabase • Execution • Tools to merge feature classes and ensure all records accounted for • Long term control • Scripts for automatic update of broken links

14. Inventory • First steps – identify current state • High level • Current database structure • Identify feature classes • Relationships • Lower level • Features and domains • Check for data normalization

15. Scripts • High level • feature class and feature data set identification • In depth feature class assessment • Number of records • Fields • Domain check • All domains used with feature classes

16. Database overview

17. Feature Classes

18. Domain Utilization

19. Bonus: domain ID

20. Inventory results • City • 161 Total Feature Classes • 12 Feature Datasets • 65,905 Total Records • County • 363 Total Feature Classes • 30 Feature Datasets • 2,680,513 Total Records • Also have multiple databases per department

21. Normalization • Many duplicate classes by type • Duplicate feature classes • Missing key or foreign key acting as primary key • Redundant records

22. Normalization - Manholes • Manhole store pipe information as well as manhole • Large number of missing attributes • Wasted space • Not Flexible for all solutions

23. Solution • Utilize Related tables • Parse through records and grab associated pipe data • Verify and check manhole pipe against pipe data • Remain with manhole info linked to pipes

24. Database Design

25. Blood, sweat & tears

26. Execution and transfer • Some copy and paste • Mostly hand merging and checking data • FC to FC tool • Left old version running while SDE was built • Duplicate edits

27. Long Term Control • Dealing with numerous .mxd documents • Breaking links • Merged feature classes

29. Future • Utilizing ArcGIS Online • Field Crews • Fire Departments • Smaller Government Data Development • Public Story Maps • School Education • Better Database Connections for Parcel Data • Parcel Fabric

30. Questions?