Migration to Geodatabases

1
Migration to Geodatabases

• A long winding road

2
BackgroundLand Information Sytem (LIS) Data

• Existing Land Use

• Planned Land Use

• Existing Ownership

• General Plans

• Redevelopment Infill

• Activity Centers

3
BackgroundLand Information System (LIS) Data

• LANDCORE
• Admin
• Base
• Districts
• Land
• SenLU
• Transit
• CalCovs

4
Why Migrate

• Positives
• Coverage model
• Lots of experience
• Institutional knowledge
• Well documented
• Works
• UNIX
• Negatives
• Manually intensive
• Data sharing
• Institutional knowledge
• UNIX

5
Why Migrate

• Better integration
• Allow for direct connection to GIS data
• Regional Forecast and Transportation models
• Improve update efficiency
• Data integrity
• More tools available
• Windows based application
• Software support

6
Migration Process

• Research
• Define goals
• Start using software
• Assess resources
• Assess abilities
• Create a plan

7
Migration Process

• Hire a contractor
• Conduct needs assessment / Data review
• SQL Severe / SDE configuration maintenance
• GDB schema
• Prepare data for migration
• Parcel update process
• Editing environment
• Forecast processing
• Scenarios
• Metadata
• Data publishing
• Documentation

8
Migration Process

• Conduct Needs Assessment / Data Review
• Review current data and workflow
• Interview GIS staff and data users to determine
  needs
• Breakdown and rank function priority
• Develop new workflow plan
• Outline database model
• Develop application specifications
• Prototype metadata
• Resulting in comprehensive design document

9
Migration Process

• SQL Server / SDE Configuration and Maintenance
• Configuration of server and software
• Security
• Backup procedures
• Maintenance procedures
• Automated scripts
• Documentation

10
Migration Process

• GDB Schema
• Visio UML of the database design
• Tables
• Relationships, subtypes, domains
• Spatial reference
• Load pilot data
• Create topology
• Test relationships and topology
• Fix, Update, Test
• Document

11
SDE/SQL Server, Subtypes, gt 40 domains, and over
800,000 polygon features!
12
Migration Process

• Prepare Data for Migration
• Clean up your data
• Remove unnecessary attributes and features
• Collapse and combine data
• Check data integrity
• Create or adjust associated tables
• Document
• Map data migration
• Show where data is coming from and where it is
  going

13
Migration Process

• Parcel Update Process
• Follow workflow
• Automate through models and scripts
• Test automation
• Quality control of data
• Fix, update, test, QC
• Assess the amount of manual editing
• Document

14

• Coastal Polys
• Split polys/parcels
• Existing parcels
• New Parcels
• Orphan polys

15
Migration Process

• Editing Environment
• Assess out of the box tools
• Accessibility
• Map extents
• Attribute display
• Develop custom attribute editor
• Script
• Integrate tables
• Test functionality
• Redesign and test
• Document

16
The Landcore Attribute Editor
A decision-support editing tool.
17
An Information Viewer

• Information is pulled from many tables in the
  Geodatabase, and provided to the user at once.

18
A Decision-Support Editing Tool
Provide information to help the user make
informed decisions
Change and calculate field values
19
A Data Integrity Tool
Ensure better data integrity by alerting the user
to take corrective actions before introducing an
error into the geodatabase
20
A Data Integrity Tool Cross-field validation
Checks for conflicting information across the
entire geodatabase. If field A in table 1 is X
then field B in table 2 cannot be Y
21
Migration Process

• Forecasting Process
• Develop models and scripts to combine data
• Calculate percent constrained
• Test process
• Quality control
• Fix, update, test
• Document

22
Migration Process

• Scenarios
• Requirements
• Accommodate changes to attributes
• Accommodate override tables
• Accommodate changes to geometry
• Be able to exist over a long period of time
• Be able to track different scenarios
• Research options
• Versioning
• Document

23
Migration Process

• Metadata
• Design XML style sheet
• Convert existing metadata
• Develop XML enclosures for attributes
• Associate metadata with proper features

24
Migration Process

• Data Publishing
• Users needs
• Develop models and scripts to produce user
  friendly layers
• Test
• Quality control
• Document

25
Migration Process

• Documentation
• Document throughout the whole process
• Keep track and report errors or bugs
• Compile into a user document
• Documentation should be a living document

26
Conclusion

• Take the time
• Make sure you know your users
• Make sure the data will fit the workflow and visa
  versa
• Test
• Make sure your results are correct
• Document
• Have patience