Lessons Learned Implementing and Using ArcSDE Baltimore County, Maryland

1
Lessons Learned Implementing and Using
ArcSDEBaltimore County, Maryland

• Presented by Robert M. Livermore and Douglas M.
  Adams
• Central Maryland ArcGIS Users Group Meeting
• September 2005

2
Database Migration

• Existing Formats
• ArcStorm
• Shapefiles
• Personal Geodatabases
• Coverages
• Oracle Tables

3
Geodatabases

• In-Production
• Cadastral
• Zoning
• Utilities
• Facilities
• Administrative (Census)

• In The Wings
• Survey
• Plan/Topo
• Master Plans
• Hydro

4
Geodatabase Design Iterations

• Requirements Based
• Involved Subject Matter Experts
• New Way of Visualizing
• Can Always Modify
• Faster Development Process

5
Facilities Small Diagram
6
Data Organization

• ISO Schema
• Features Based on Schema
• Tablespaces by Schema
• Overhead to Create
• Consistent Naming Structure
• Ability to Perform Maintenance

7
Terminology

• Change Control
• Base Tables
• Add/Deletes Tables
• Versions
• States
• Compress Log

8
Versioning

• Parent/Child
• Owner/Editor
• Reconciliation
• Editor reconciles to parent
• Owner reconciles to parent
• Owner reconciles to sde.default
• SdeAdmin reconciles/posts to default

9
Versioning Structure

10
Versioning

• Validate (Clean)
• Removal of large ROW/Island polygons
• Generate new split feature
• Between Layers (Topology)
• Connectivity - Network Tools
• Cluster Tolerance
• Setting Precision
• Dont Accept Default

11
Dirty Areas
12
Conflict Resolution

• Both spatial entities and attributes
• Owner
• Aware of what is being changed
• Responsibility of Owner
• Cant accept both edits
• Accept most complicated edits

13
Compress

• Assumes
• Reconciliation and Posting Complete
• SDE.DEFAULT is only version in database
• Downtime for Editing and Access
• Pre-Compress
• Analyze SDE and Owner Schemas
• Ensure No ArcSDE Connections
• Perform Compression
• Verify Results
• SDE.Compress_Log table

14
Scheduling

• Based on Workflow, Edits and Change Control
• Off Hours
• Notifications to Users
• Sets User Expectations

15
Schema Changes

• Unversioned State
• Domain Values not Automatically Being Used
• Must be Compressed No Versions
• Document in Metadata and Other Documentation (Log
  File)

16
Production/Development Environment
17
Advantages Production vs. Development

• Production
• Unversioned
• Faster
• Minimal Downtime for Updates
• No Editing
• Backups Less Frequent (Static Data)
• Provides Stable Data for ArcIMS, ArcGIS

• Development
• Versioned
• Platform for Departments
• Controlled Workflow
• Can Make Mistakes
• Not Constrained by Change Control

18
Access

• Userids
• Individual Accounts
• Monitoring Users
• SDE Log Files

19
Layer Files

• Access (Creator Password)
• Uncheck Save Password
• Control Symbology
• Can be Grouped
• Pointers to Database
• Can Be Joined/Related to Tables

20
(No Transcript)
21
Views

• Anatomy
• De-normalized
• Joins Object Feature Classes
• Preferred Presentation to Casual Users

22
(No Transcript)
23
(No Transcript)
24
(No Transcript)
25
Maintenance

• Skill of Editors
• Deliberateness of Workflow
• Complexity of Model
• Model Specific
• Interaction with ArcSDE Administrator

26
Training Requirements

• Editors
• High-level ArcGIS
• Building Geodatabases
• Geodatabase Design Concepts
• Creating, Editing Managing Geodatabases
• Administration
• ArcSDE Administration for RDBMS
• Introduction of the Multi-user Geodatabase