Geodatabase Design with ArcGIS Pro Training Course

Participants can convert stakeholder needs into documented spatial data and workflow requirements.

• Stakeholder interviews identify decisions, outputs, data owners and service-level expectations
• Use cases document create, read, update and delete data transactions
• Data requirements matrix links business fields to source and stewardship
• Functional requirements separate editing, analysis, reporting and publication needs
• Nonfunctional requirements define availability, response times, security and retention
• Acceptance criteria establish measurable tests for the proposed geodatabase design

Participants can create logical entity-relationship models for spatial business processes.

• Entity-relationship diagrams represent entities, attributes, cardinality and optionality
• Identify spatial entities from assets, events, boundaries and observation records
• Primary keys, foreign keys and surrogate identifiers support stable relationships
• Normalisation reduces repeated attributes while preserving required operational history
• Denormalisation decisions address reporting speed, editing simplicity and service requirements
• Logical model review tests business rules against representative workflow scenarios

Participants can define spatial reference and feature dataset structures appropriate to intended use.

• Coordinate system selection considers accuracy, area, distance and interoperability requirements
• Horizontal and vertical datums documented using authoritative transformation parameters
• Feature datasets group classes requiring shared coordinate systems and topology
• XY resolution and tolerance settings influence coordinate storage and validation
• Z and M values configured for elevation, routes and linear referencing
• Spatial reference documentation records source systems, transformations and precision decisions

Participants can build efficient feature class and table schemas from approved logical models.

• Feature class geometry types selected for points, lines, polygons and multipatches
• Field data types match identifiers, measurements, dates, codes and descriptive values
• Field naming conventions support readable services, exports and database administration
• Nullable fields, defaults and required values reflect documented business rules
• Global IDs enable attachments, replication and stable cross-system references
• Attribute schema review detects ambiguous fields, duplicates and inappropriate free text

Participants can configure controlled attribute values that match operational classifications and rules.

• Coded value domains standardise asset classes, status codes and inspection outcomes
• Range domains constrain measurements such as pressure, depth and capacity
• Subtypes assign default values and behaviour for related feature categories
• Contingent values restrict valid field combinations within defined asset types
• Domain ownership and change control prevent uncontrolled classification drift
• Data dictionaries document definitions, permissible values, units and custodians

Participants can model related records and attachments without duplicating operational information.

• Relationship classes connect assets, inspections, work orders and observations
• One-to-one, one-to-many and many-to-many cardinalities model business records
• Composite relationships define parent-child behaviour during feature deletion
• Attachment tables store photographs, documents and field evidence against records
• Attributed relationships capture dates, roles and quantities between entities
• Relationship validation tests referential integrity under editing and deletion scenarios

Participants can design topology rules that detect unacceptable spatial relationships and geometry errors.

• Topology rule selection reflects connectivity, coverage and boundary management requirements
• Must Not Overlap rules identify duplicate polygons and conflicting asset extents
• Must Not Have Gaps controls parcel, service area and land-cover coverage
• Point Must Be Covered By Line validates inspection and network observations
• Topology ranks assign correction priority where feature classes share boundaries
• Error exceptions documented with rationale, ownership and periodic review dates

Participants can implement ArcGIS attribute rules to calculate, constrain and validate data edits.

• Calculation rules populate identifiers, timestamps and derived operational attributes
• Constraint rules block edits that violate defined business conditions
• Validation rules identify records requiring review after batch updates
• Arcade expressions reference attributes, geometry and related record conditions
• Rule evaluation order prevents conflicting calculations and misleading error messages
• Validation status workflows assign review responsibility and closure evidence

Participants can specify controlled editing workflows and quality checks for shared geodatabase content.

• Editing templates standardise geometry capture, attributes and default asset classifications
• Snapping settings support precise connectivity and coincident boundary maintenance
• Quality assurance plans define checks, sampling rates, thresholds and escalation
• Data Reviewer checks target geometry, attributes, duplicates and spatial relationships
• Error management records issue type, severity, assignee and corrective action
• Editorial procedures separate data capture, verification, approval and publication roles

Participants can plan enterprise geodatabase deployment with appropriate database and storage choices.

• Enterprise geodatabases connect ArcGIS Pro with managed relational database systems
• Database platform selection compares SQL Server, PostgreSQL and Oracle capabilities
• Schema ownership separates database administration from GIS data stewardship duties
• Storage configuration considers tablespaces, filegroups, backups and transaction logs
• Connection files manage authenticated access without distributing administrative credentials
• Deployment checklist verifies software compatibility, privileges and database prerequisites

Participants can select and configure multiuser editing workflows for concurrent data maintenance.

• Traditional and branch versioning compared for editing and service workflows
• Named versions isolate planned edits, quality review and approval stages
• Reconcile and post operations integrate reviewed changes into authoritative data
• Conflict detection settings determine attribute, row and geometry resolution behaviour
• Version access permissions restrict editors, reviewers and data administrators appropriately
• Editing workflow diagrams define handoffs, review gates and rollback procedures

Participants can establish geodatabase governance controls for access, ownership, metadata and change management.

• Role-based access control assigns least-privilege database and GIS permissions
• Data stewardship matrix identifies owners, custodians, editors and approval authorities
• ISO 19115 metadata elements document purpose, lineage, quality and constraints
• Naming standards cover datasets, fields, domains, versions and published services
• Change requests assess schema impacts, migration steps and stakeholder approvals
• Retention schedules define archival, disposal and preservation requirements for records

Participants can diagnose geodatabase performance issues and define routine maintenance actions.

• Spatial indexes accelerate map display, selection and spatial query operations
• Attribute indexes support frequent joins, filters and relationship class queries
• Query plans reveal inefficient predicates, missing indexes and excessive table scans
• Analyze datasets updates database statistics after significant data changes
• Compress operations reduce versioned edit states under approved maintenance procedures
• Maintenance calendars schedule backups, index rebuilding, validation and monitoring

Participants can plan controlled migration and publication of authoritative geodatabase content.

• Extract-transform-load mapping aligns source fields with target schema definitions
• Data profiling identifies nulls, duplicates, invalid codes and geometry defects
• Field mapping documents conversion rules, defaults and rejected-record treatment
• Append and Load Data tools support controlled population of target classes
• Feature services expose authoritative layers with editing and query capabilities
• Publication plans define ownership, refresh frequency, service limits and audiences

Participants can build, review and present a complete geodatabase architecture package for a realistic operational scenario.

• Scenario requirements translated into conceptual, logical and physical data models
• ArcGIS Pro schema built with domains, subtypes, relationships and topology
• Attribute rules and quality controls configured against stated business requirements
• Enterprise editing model specifies versions, roles, approvals and conflict handling
• Implementation plan addresses migration, metadata, testing, deployment and maintenance
• Peer design review evaluates traceability, integrity, performance and governance decisions