Geodatabase Management with ArcGIS Pro Training Course

Participants can assign, assess and transform coordinate reference systems correctly.

• Geographic and projected coordinate systems distinguished through measurement requirements
• Datum transformations selected using source accuracy and geographic extent
• Inspecting spatial reference properties in ArcGIS Pro catalog views
• Defining projections only when source coordinates lack valid metadata
• Projecting feature classes with appropriate geographic transformation parameters
• Vertical coordinate systems and elevation data management considerations

Participants can translate business requirements into a conceptual spatial data model.

• Entity-relationship modelling for spatial assets, events and reference features
• Identifying entities, attributes, identifiers and business ownership rules
• Cardinality and optionality expressed through relationship model notation
• Separating observation data from managed asset inventory records
• Business process mapping used to identify editing and validation needs
• Conceptual models reviewed against reporting, analysis and field workflows

Participants can create feature datasets and feature classes suited to operational use.

• Feature datasets created for common spatial reference and topology requirements
• Geometry types selected for assets, boundaries, events and observations
• Feature class naming conventions supporting discovery and administration
• Object identifiers, global identifiers and business keys distinguished
• M values and Z values configured for route and elevation data
• Resolution and tolerance settings assessed for positional accuracy requirements

Participants can standardise attribute values and classify feature behaviour using geodatabase controls.

• Field types selected for identifiers, measurements, dates and coded values
• Coded value domains created for controlled attribute classification
• Range domains applied to measured values and permitted thresholds
• Subtypes configured to represent feature categories with distinct defaults
• Default values established for consistent feature creation workflows
• Null values, unknown values and absent values treated distinctly

Participants can model related records and enforce referential integrity within a geodatabase.

• Relationship classes created for one-to-many and many-to-many records
• Simple and composite relationships compared through deletion behaviour
• Primary keys and foreign keys mapped between related tables
• Attachments configured for inspection images, permits and supporting documents
• Attributed relationship classes used for inspection and association history
• Integrity rules documented for parent records and dependent records

Participants can load source data into controlled schemas while preserving documented transformations.

• Source data profiled for geometry, attributes, duplicates and missing values
• Field mapping applied during import and feature class conversion
• Append tool used with schema testing and controlled field matching
• Data Interoperability principles applied to external format transformation workflows
• Staging geodatabases used before loading production spatial datasets
• Load logs recorded with source, date, transformations and exceptions

Participants can configure topology rules and correct spatial relationship errors.

• Topology rules selected for boundaries, networks and coverage datasets
• Must Not Overlap rules applied to mutually exclusive polygons
• Must Not Have Gaps rules applied to complete administrative coverages
• Point Must Be Covered By Line rules configured
• Topology validation performed after editing and bulk data loading
• Error exceptions documented where valid business conditions require them

Participants can use attribute rules to enforce business rules during editing.

• Calculation rules populate derived fields during feature creation
• Constraint rules prevent invalid values and prohibited edits
• Validation rules identify records requiring batch evaluation and correction
• Arcade expressions written for field logic and conditional checks
• Rule evaluation order considered when configuring dependent calculations
• Error layers reviewed to prioritise corrections by business impact

Participants can configure controlled editing workflows for shared spatial datasets.

• Editing templates configured with default attributes and feature construction tools
• Snapping settings applied to maintain network connectivity and boundary alignment
• Editor tracking records creator, editor and modification timestamps automatically
• Edit operations organised through documented create, update and retire procedures
• Quality assurance checks scheduled before approval and publication stages
• Change requests linked to data corrections and schema amendments

Participants can manage traditional versioned workflows, reconciliation and posting decisions.

• Traditional versioning architecture explained through parent and child versions
• Versions created for projects, editors and controlled change packages
• Reconciling edits identifies conflicts against target version changes
• Conflict detection policies compared using row and column methods
• Posting approved edits transfers reconciled changes to target versions
• Compress operations planned after posting and version deletion activities

Participants can prepare branch-versioned data for web-based multiuser editing.

• Branch versioning requirements assessed for feature service editing workflows
• Global IDs, editor tracking and archiving enabled before registration
• Feature services published with appropriate editing capability settings
• Named versions created for isolated project and review work
• Reconcile and post workflows applied through service-based version management
• Web editing implications assessed for field collection and approval processes

Participants can define access controls for enterprise geodatabase users and roles.

• Database authentication and operating system authentication compared for access control
• Data owner, editor, viewer and administrator responsibilities defined
• Database roles assigned according to least-privilege access principles
• Privileges granted for tables, feature classes and related datasets
• Connection files managed without exposing credentials in shared projects
• Access reviews scheduled following staff changes and contractor departures

Participants can document datasets so users can assess suitability, origin and constraints.

• ISO 19115 metadata elements applied to managed spatial datasets
• Item descriptions completed in ArcGIS Pro catalog views
• Data dictionaries document fields, domains, units and permitted values
• Lineage records capture source systems, transformations and update history
• Positional accuracy, completeness and currency documented for data users
• Usage constraints recorded for licensing, privacy and security controls

Participants can identify common geodatabase performance issues and select appropriate remedies.

• Spatial indexes support geographic queries and map display performance
• Attribute indexes created for frequent selection and join fields
• Query filters reduced through selective fields and spatial extent
• Database statistics updated after substantial loading and editing activity
• Feature class size, geometry complexity and attachments assessed
• Performance baselines recorded before tuning data storage configurations

Participants can prepare recoverable geodatabase maintenance procedures and retention controls.

• Recovery point objectives and recovery time objectives defined
• Database backups scheduled according to change frequency and criticality
• Restore procedures tested using documented recovery scenarios
• Archiving preserves historical records of edits and attribute changes
• Retention schedules distinguish operational copies from long-term records
• Maintenance calendars assign ownership for backups, checks and restores

Participants can establish governance procedures for schema changes, quality ownership and release control.

• Data stewardship roles assigned for ownership, approval and maintenance
• Schema change requests assessed for dependencies and migration impacts
• Release management controls separate development, test and production data
• Data quality indicators defined for completeness, validity and timeliness
• Issue registers track defects, corrective actions and accountable owners
• Governance meetings review standards compliance and priority improvements

Participants can prepare governed geodatabase content for controlled sharing through GIS services.

• Feature layers published from approved enterprise geodatabase datasets
• Service definitions reviewed for capabilities, scale ranges and permissions
• Read-only views created for reporting and public information products
• Hosted layers and referenced layers compared for governance implications
• Web maps configured to present authoritative layers and controlled symbology
• Distribution schedules defined for extracts, services and partner datasets

Participants can diagnose common geodatabase operational issues using structured checks and logs.

• Connection failures investigated through credentials, permissions and network checks
• Schema locks identified before maintenance, loading and structural changes
• Invalid geometry detected using Check Geometry and Repair Geometry
• Orphaned relationships investigated through key fields and integrity checks
• Version conflicts reviewed against editing responsibilities and approval rules
• Administration logs compiled for incidents, actions and follow-up decisions

Participants can build, review and present a complete governed geodatabase design for an operational GIS scenario.

• Requirements translated into a documented conceptual and logical data model
• Feature classes, domains, subtypes and relationships configured in ArcGIS Pro
• Topology and attribute rules applied to defined data-quality risks
• Editing, versioning and access workflows specified for user roles
• Metadata, backup procedures and governance controls assembled into documentation
• Peer review tests schema fitness against operational reporting requirements
• Implementation pack presented with decisions, risks and phased actions