Sharing Data Maintenance Responsibilities With Multiple Agencies Using Web Services

1. Sharing Data MaintenanceResponsibilities With MultipleAgencies Using Web Services Forrest S. Smith Canyon County Sheriff’s Office Caldwell, Idaho

2. Canyon County’s Road Centerlines Project • Centerline File Contains Relative Data for Emergency Services • All Data Critical to Dispatching Calls • Canyon County Sheriff’s Office, Idaho • City of Nampa, Idaho • City of Caldwell, Idaho • Nampa Highway District #1 • Sharing Geocoded Road Centerlines • CAD (Computer Aided Dispatch) • Web Services Multi-Editor Solution • ArcGIS Server Geodatabase Replication • Versioned SDE SQL Server Geodatabases • Canyon County Assessor’s Office

3. Canyon County, ID Stats • 10 Incorporated Municipalities • Square Miles – 590 • Population 2006 – 173,302 • Population Change 2000 to 2006 – 32% Increase • Road Centerlines – 16,000 • Nampa – 7800 • Caldwell – 5200 • Other – 3000 • Subdivisions – 510 • Canyon County – 301 • Nampa – 170 • Caldwell - 39 • Attributes – 50+ • Required Fields for CAD • Others

4. The Problem Statement The project participants must be able to simultaneously edit an ArcGIS Road Centerlines geodataset, reconcile the edits from each of the other participants and synchronize these changes with an ArcSDE GeoDB hosted on a Canyon County server. The solution must increase the efficiency of sharing the Road Centerline dataset with the participants, reduce the cost of administering the dataset, reduce the potential for errors in the data and provide a means for sharing other geographic datasets in the future.

5. Sharing Road Centerlines - BEFORE • Editor Makes Changes • Only in Their Areas • Editor Prepares Shapefiles • Export Data • Zip Files • Editor Sends Changes to Administrator • Email Shapefiles, Communicate Changes • Administrator Manually Compiles Changes • Different Projections, Schemas • Load Data, Delete Existing, Connectivity, Attributes • Administrator Redistributes Changed Dataset • Create the Distribution Dataset • Email Shapefiles, Communicate Changes • Follow-up and/or Redeliver

6. The Solution • GeoData Server • ArcSDE Enterprise • SQL Server 2005 • Web Server • ArcGIS Server 9.2 Enterprise Standard • .NET Web ADF • Microsoft IIS 5.0 • Content Authors • ArcGIS Server Basic Workgroup • ArcGIS Desktop • Personal ArcSDE • SQL Server Express 2005

7. The Road Centerlines Geodataset And Map Service

8. Bringing Everyone Together

9. The Architecture

10. Sharing Road Centerlines – AFTER • Editor Makes Changes • Edge matches with Adjacent Jurisdictions • Editor Synchronizes Changes • With the Parent Replica • With their Child Replicas • Administration • Review & QA • Reconcile Changes to Default GeoDB • Track Versions • Database

11. Web Server .mxd

12. Return On Investment Lower Cost Higher Quality Data More Efficient Operation More Scalable System

13. Cost • Work and Time • Administrator’s Time • Turnaround Time Decreased • More Than One Set of Eyes • Increased Sharing of Work • Intra-Departmental, • Inter-Jurisdictional • Editors Not Restricted • Data Security • Versioning, Reconciliation, Transactions • Permissions, Filtered Views, Authentication • Data Quality • System Stability • Work Done Once

14. Quality • Increase in Quality • Distributed Focus on Quality • Edge matching by Many • Automated Reconciliation Process • Different Jurisdictions, Different Needs • City -vs.- County Requirements • Frequency of Update • Lessened Error Introduction Potential • Duplication of Work • Topology • Communication Errors • Data Organization

15. Efficiency • Reduced Work for the Administrator • Synchronous –vs.– Asynchronous Process • Updates Submitted Asynchronously • Lessened Dependence Upon Editors • Synchronization and Reconciliation Options • Pull, Push or Exchange Geodatabase Changes • Manual or Automatic Reconciliation • Automated Data Distribution • Real-Time Synchronization via Replication • Reduced Communication Requirements • Reduced Resources

16. Scalability • Additional Layers • City Limits • Hydrants • Fire and Law Zones • Hydrography • Additional Authors or Publishers • Other Departments • Other Jurisdictions • Additional Users • Viewers • Public

17. Challenges • Money • Must have GIS Server technology • $20,000 for software only • All Editors must have at least ArcEditor License • ~$6,000 /license • Hiring Technology Firm to Advise • $35,000 • Justifying the investment to Commissioners, mayors, City Mangers, etc… • Priceless

18. Challenges • RFP/RFB Process • Idaho Law requires that governments solicit a minimum of 3 Bids for any project over $25,000 • Comment Periods • Ensure All Editors can Be Trusted • GIS Professionals Only • Schema • Agreement on Fields • Threw everything in

19. Challenges • Security • IT • Ports to outside domain

20. Terms and Definitions • Version • Each version represents a unique, seamless view of the database, distinguished from other versions by a particular set of edits made to that version since it was created. The schema of each versioned database object is identical across all the versions. ex: adding a new field to a table—will appear in all versions of the geodatabase. Source: http://downloads.esri.com/support/whitepapers/ao_/Versioning_2.pdf

21. Terms and Definitions • Replica • ArcGIS 9.2 allows A “Child” copy of the parent geodatabase to be made which is edited and synchronized with the parent. Each editor may have many replicas. • Desktop • Laptop

22. SQL Express Creation

23. SQL Express New GDB

24. New SQL Geodatabase

25. Creating the Replica - ArcMap

26. Creating the Replica - ArcMap

27. Replica Advanced Options

28. ArcCatalog – SQL Express

29. View Activity Logs - ArcCatalog

30. Admin View

31. Questions? Forrest S Smith GIS Specialist Canyon County Sheriff’s Office Caldwell, ID Email: fsmith@canyonco.org Phone: (208)455-5976