Encinitas Enterprise Geodatabase Steps Taken and Lessons Learned Prepared by the Encinitas GISIT Div

1
Encinitas Enterprise Geodatabase(Steps Taken
and Lessons Learned)Prepared by the Encinitas
GIS/IT Divisionin the City Managers
DepartmentPrepared for the SDRGC Geodatabase
Subcommittee
2
Encinitas Master Tech Plan

• Encinitas had a Master Technology Plan developed
  in 2000-01. The Plan outlined 5 major technology
  initiatives
• Enterprise GIS
• Asset Management
• A New Permit and Plan Check Processing System
• Document Management
• EGOV

3
Enterprise GIS Goals

• GIS MISSION STATEMENT To develop an enterprise
  GIS program that will allow Encinitas to create a
  more efficient and effective operating
  government.
• GIS Program Purpose
• Create a better way to maintain, manage, and
  share
• geographic information throughout the City.
• Improve coordination between departments.
• Improve services to citizens.

4
STEPS TAKEN

• Transferred Shapefiles and Coverages to SDE
• First cut of naming conventions
• Create a data cross-walk spreadsheet to aid in
  re-sourcing data in broken MXDs
• Started Data Modeling Effort
• Start with pared-down ESRI model
• Stormwater
• Land Records
• Sewer
• Water
• Implemented with limited relationship classes, no
  topolgy, no feature-linked anno, and no
  dimensioning
• Started Data Capture/Conversion Effort
• Need intern-level staff to populate data
  structures. Requires consistent planning,
  set-up, management, and direction by higher-level
  staff.

5
NEXT STEPS

• One more Data Model pass for
• Stormwater
• Sewer
• Start Data Modeling Effort for
• Parks Recreation
• Transportation
• Finish the models
• Define topologies, feature-linked annotation, and
  dimensions on complete models and existing
  production data.

6
Recommendations Tips

• Decide and do as much up-front design as you
  can!!
• Use single SDE approach (available at 9.0)
• Create one user that can create feature classes
  and feature datasets
• (i.e. username GIS )
• Use VISIO for data model diagrams
• Adopt Naming Conventions and Database Standards
  as a first step
• Adopt a standard for mapping AS-IS and TO-BE
  business processes to help with business process
  re-engineering (We recommend SWIMLANE diagrams)
• Meet with users several times during Data
  Modeling efforts after all, it is really their
  data. Do DEMOs with ArcMap.
• If youre interested in creating a Land Records
  data model we recommend purchasing the book
  Land Records from ESRI Press.
• Network your line features and enable M values.

7
Lessons Learned / Daily Frustrations

• Feature Classes and Business Tables
  Inconsistency with Mixed Case
• Spatial Extent If this is not identical for all
  your feature classes, youll get errors when
  trying to create feature datasets
• Domains Copy and paste of feature classes and
  feature datasets will duplicate domains
• Relationship Classes Data entry issues,
  business tables, and workarounds
• Feature-linked Annotation If you rename a field
  in a feature class that has related
  feature-linked anno, the field in the annotation
  table will not be renamed, which causes editing
  to break
• Networks/Topologies Must drop these to make
  changes to the schema, then re-add

8
The End