Scribd
Upload
11 views

Design a Geodatabase

Uploaded by

khaled.r.nafea
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
11 views

Design a Geodatabase

Uploaded by

khaled.r.nafea
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 23

Design a Geodatabase

Rasu Muthurakku, Enterprise Solutions Architect / Consultant


Agenda
Design a Geodatabase

• Overview
• Key Factors
• Geodatabase Design
• Recommendations

Key Considerations, Best Practices, Recommendations and Lessons Learned!


Overview
What is a Geodatabase (GDB)?

• Collection of Geographic Datasets of Various Types Stored in:


- Common File System Folder
- Microsoft Access Database

- Multiuser RDBMS * / ArcSDE


- Oracle
- Microsoft SQL Server
- PostgreSQL
- IBM DB2, Informix
- SAP Hana 2.0 SPS02 New

• Native Data Structure for ArcGIS


• Primary Data Format Used for Editing and Data Management
• Comprehensive Approach to Modeling and Managing Spatial Data

* RDBMS – Relational Database Management System


Types of Geodatabases

Utility Network

Mosaic Datasets

Choose per Workflow and Limitations!

Design a Geodatabase
Key Factors
Why?
Expensive Rework
A Stitch in Time Saves Nine!

• Data Model Designs


- Change in XY Resolution / Tolerance
- Multiple Projections
- Objectid as Primary Key for Relationship Classes
- etc.
• Data Conversion Specifications
- Extra Vertices
- Insufficient QA/QC
- Large Feature Extent
- Possibly by Data Conversion / Testing
- Loading Static Raster Data Into GDB
- etc.
Avoid Pitfalls!
Degraded Performance and Scalability
Risks

• Workflow
- Number of Outstanding Versions
- Versioning Levels
- Archiving
- etc.
• Maintenance
- Compact and Compress FGDB (File Geodatabase)
- Total Delta Table Records
- GDB Maintenance
- etc.

Separate Myths / Emotions from Evidence Based Facts!


Requirements and Workflows
Drives the Selection and Number of GDBs!

• Number of Users and Types of Users


• Workflows
- Multi User Editing - Enterprise / Workgroup GDBs
- Single User Editing – FGDB
- Replication - EGDB  FGDB / EGDB
- Read Only / Publication – FGDB / EGDB
- etc.

• Generally more than one Geodatabase is required!

Avoid Limitations!
Geodatabase Design
Geodatabase Design – Data Modeling
Conceptual
• Conceptual Design Model
- Identify Business Requirements
- Identify Thematic Layers Physical
- Identify Required Applications Model Logical
- Leverage Data Model Templates Model
- Document

• Logical Design
- Define Tabular Database Structure • Physical Design
- Define Relationships - Create and Implement Model Design
- Determine Spatial Properties - Generate Physical Schema in the RDBMS / FGDB
- Document - Testing and Validation
- Document
Geodatabase Design – Process

• Tools
- X-Ray Add-In
- Geodatabase Diagrammer
- Sparx Systems' Enterprise Architect
- Geometric Network Configuration Manager

• 11 Technical Steps!
Geodatabase Design – ArcGIS Data Models

Leverage the Existing Data Models!


Recommendations
Geodatabase Design – Key Considerations
Poor Design = Slow Performance and Bugs

• Empty Feature Classes / Columns


• Missing / In-Correct Domains and Aliases for Fields
• Column / Domain Names and Field Lengths
- >10 Characters in Field Names
- Length of Text/NCLOB – 256 or 1,073,741,822
- Choice of Field Type
- Selection of Precision and Scale
- Define Not Null Fields
Geodatabase Design – Best Practices
Poor Design = Slow Performance and Bugs

• No Attributed Relationship Classes for Empty Tables!


• Use Many to Many Relationship Classes Only When Necessary
• Don’t Use Objectid as Primary Key for Relationship Classes
- Unexpected Replication Behavior
- Additional Processing During Synchronization
Geodatabase Design – Best Practices
Prevention is Better Than Cure!

• Leverage the Existing ArcGIS Data Models


- Drop Redundant Feature Datasets / Classes, Columns, etc.
- Stand Alone Feature Classes are Fine!
- Possibly Split the Feature Classes Per Scale Levels
- Less Complex and Attributed Relationship Classes
- Test, Refine and Tune the Data Models
• Integrate Related Feature Classes using Topology
• Deploy Necessary Information Models
- Geometric Network Vs Utility Network (New!)

Justify Every Single Geodatabase Element!


Geodatabase Design – Best Practices
Prevention is Better Than Cure!

• Select Single Coordinate System


- On the Fly Projection is Expensive
- Geometric Network Editing Does Not Support “On the Fly Projection”
• Create Feature Datasets or Databases for Each LOB (Line of Businesses)
- Depends on Size, Access, Usage and Maintenance
- E.g. Landbase, Gas, Electric, Water GDBs, etc.
QA / QC - Recommendations
Data Integrity and Validation!

• Design and Implement QA / QC Workflows


- Data Requirements for Software Functions
- Accurate Data for Business
- Maintain Data Integrity
• Tools
- Domains, Subtypes, Topology, etc.
- Attribute Assistant Add-In
- ArcGIS Data Reviewer
- ArcGIS Workflow Manager
- Business Partner Products
- Customization

Prevention is Better Than Cure!


Capture, Load and Maintain Data Accurately!
Questions and Answers

Contact Info:
Rasu Muthurakku
[email protected]

Design a Geodatabase
Please Take Our Survey on the App
Download the Esri Events Select the session Scroll down to find the Complete answers
app and find your event you attended feedback section and select “Submit”

Design a Geodatabase
See Us Here
WORKSHOP LOCATION TIME FRAME

• Esri Best Practices: • SDCC - Room 17 B • Wednesday 7/11/2018


Implementing an Enterprise 08:30 AM - 09:30 AM
Geodatabase

• Esri Best Practices: • SDCC - Room 05 B • Thursday 7/12/2018


Implementing an Enterprise 10:00 AM - 11:00 AM
Geodatabase

Design a Geodatabase
Thanks!

Design a Geodatabase

You might also like