Study guide
14.2 Geodatabase Schema Architecture: Feature Datasets, Subtypes & Attribute Domains
GISP Geospatial Core Technical Knowledge Exam Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: GISP Exam Structure, Policies & Preparation Strategy
1.1 GISP Certification Framework, Pearson VUE Delivery & Passing Standard 1.2 The 10 Official GISCI Knowledge Categories & Diagnostic Study Planning 1.3 Question Reasoning, Vendor-Neutral Concepts & Test-Taking Tactics
2 Chapter 2: Geodesy, Datums & Earth Geometry
2.1 Earth Geometry: Geoid, Reference Ellipsoids, and Heights 2.2 Horizontal & Vertical Datums: NAD27, NAD83, WGS84, NAVD88, and Modernized NSRS 2.3 Geomatics Disciplines, Geodetic Control Networks, and Monumentation
3 Chapter 3: Coordinate Systems & Map Projections
3.1 Geographic (GCS) vs. Projected (PCS) Coordinate Systems & Angles 3.2 Projection Families & Distortion Properties 3.3 Standard Projected Systems: State Plane (SPCS), UTM, and Web Mercator
4 Chapter 4: Vector & Raster Spatial Data Models
4.1 Vector Data Architecture: Points, Lines, Polygons, Multipart Features & Curves 4.2 Raster Architecture: Grid Structures, Pixel Dimensions & Multi-Dimensional Resolutions 4.3 Modeling Geographic Phenomena: Discrete Objects vs. Continuous Fields 4.4 Elevation and Surface Representations: DEMs, DSMs, DTMs, TINs, and Point Clouds
5 Chapter 5: Topology, Data Quality & Geospatial Standards
5.1 Spatial Topology: Planar Enforcement, Adjacency, Connectivity & DE-9IM 5.2 Data Quality Dimensions and Positional Accuracy Standards (ISO 19157-1, NSSDA, RMSE) 5.3 Geospatial Metadata Standards: FGDC CSDGM and the ISO 19115 Family 5.4 Open Standards and Interoperability: OGC Web Services & Open Formats
6 Chapter 6: Cartographic Design & Visual Variables
6.1 Visual Variables (Bertin's Semiology of Graphics) and Map Symbology 6.2 Map Design Hierarchy, Common Elements, Layout Balance & Typography 6.3 Color Theory, Palette Types & Accessible Cartographic Design
7 Chapter 7: Thematic Mapping & Data Classification
7.1 Thematic Map Types: Choropleth, Proportional/Graduated Symbol, Dot Density, Isarithmic & Cartograms 7.2 Data Classification Methods: Natural Breaks, Quantile, Equal Interval, Geometric Interval & Standard Deviation 7.3 Terrain Representation & 3D Visualization: Shaded Relief, Slope, Aspect, Curvature & Oblique Views
8 Chapter 8: Field Data Acquisition & GNSS
8.1 GNSS Constellations, Signal Structures, Error Budgets & Differential Correction (DGPS, RTK, PPP) 8.2 Heads-Up & Tablet Digitizing, Snapping Tolerances, Stream Mode & Boundary Capture 8.3 Mobile Field GIS Workflows, Disconnected Editing, GNSS Integration & Crowdsourced/VGI Data
9 Chapter 9: Remote Sensing & Imagery
9.1 The Electromagnetic Spectrum, Atmospheric Windows, Spectral Signatures & Sensor Types 9.2 Aerial Photogrammetry: Relief Displacement, Parallax, Orthorectification & Ground Control 9.3 Active Remote Sensing: LiDAR, RADAR, Synthetic Aperture Radar (SAR) & UAS/Drone Mapping
10 Chapter 10: Georeferencing, Transformations & Resampling
10.1 Georeferencing: Control Points, Root Mean Square Error & Transformation Models (Affine, Similarity, Projective, Spline) 10.2 Raster Resampling Techniques: Nearest Neighbor, Bilinear Interpolation & Cubic Convolution 10.3 Datum Transformations: 3-Parameter, 7-Parameter Helmert, and Grid-Based Shifts (NADCON, HARN)
11 Chapter 11: Data Integration & Spatial Generalization
11.1 Geospatial ETL: Format Conversion, Schema Mapping & Coordinate Translation 11.2 Spatial Generalization: Selection, Simplification, Smoothing, Aggregation, Collapse & Displacement 11.3 Conflation, Edge-Matching, Rubber-Sheeting & Data Harmonization
12 Chapter 12: Vector Analysis & Overlay Operations
12.1 Attribute and Spatial Query Languages: SQL WHERE Clauses and Spatial Predicates 12.2 Vector Geometric Overlay: Intersect, Union, Identity, Erase, Symmetrical Difference & Update 12.3 Proximity Analysis: Euclidean Distance, Fixed & Variable Buffers, Voronoi/Thiessen Polygons
13 Chapter 13: Raster Analysis, Surfaces & Spatial Statistics
13.1 Map Algebra & Raster Overlay: Local, Focal, Zonal & Global Operations 13.2 Surface Analysis & Spatial Interpolation: IDW, Kriging, Spline & Viewshed Analysis 13.3 Network Analysis: Geometric Networks, Utility Networks & Routing 13.4 Spatial Statistics & Pattern Analysis: Spatial Autocorrelation, Hot Spots & Regression
14 Chapter 14: Geospatial Database Design & Multiuser Architecture
14.1 Relational Database Foundations & Geospatial Extensions (SQL, PostGIS, SpatiaLite) 14.2 Geodatabase Schema Architecture: Feature Datasets, Subtypes & Attribute Domains 14.3 Spatial Indexing & Storage Structures: R-Tree, Quadtree, Geohash & Vector Tiles 14.4 Multiuser Geodatabase Architecture: Traditional Versioning, Branch Versioning & Archiving
15 Chapter 15: GIS Programming, Automation & Web Services
15.1 Python for GIS Automation: Scripting, Spatial DataFrames & Geospatial Libraries 15.2 Visual Programming, Workflow Modeling & Script Tools 15.3 Web GIS Architecture: REST APIs, Feature Services, Vector Tiles & Cloud Platforms
16 Chapter 16: Enterprise Architecture, Systems Security & Cloud Platforms
16.1 Enterprise GIS Architecture, Server Tiers, Sizing & Capacity Planning 16.2 Cloud GIS, Virtualization, Containers & High Availability (HA) 16.3 Enterprise GIS Security, Authentication, Authorization & System Auditing
17 Chapter 17: GIS Ethics, Legal Frameworks & Professional Practice
17.1 GISCI Code of Ethics & Rules of Conduct: Obligations to Society, Employers, Colleagues & Individuals 17.2 Legal Frameworks: Copyright, Intellectual Property, Licensing & Liability 17.3 Location Privacy, Geoprivacy & Spatial Data Confidentiality 17.4 GIS Project Management, Governance, Data Custodianship & Professional Practice
14.2 Geodatabase Schema Architecture: Feature Datasets, Subtypes & Attribute Domains
Key Takeaways Explain This Topic AI
File Geodatabases (.gdb) store spatial layers in folder-based binary tables with a 1 TB per-table capacity, supporting single-user editing locks, whereas Enterprise Geodatabases leverage an RDBMS engine for multi-user editing, transaction versioning, and fine-grained security.
A Feature Dataset is a thematic geodatabase container that strictly enforces a shared spatial reference system (coordinate system, datum, XY tolerance, and resolution) across all contained feature classes.
Feature Datasets are structurally mandatory for building advanced topological and network models, including Geodatabase Topologies, Utility Networks, Geometric Networks, Parcel Fabrics, and Terrain Datasets.
Attribute Domains enforce tabular and attribute integrity at the database schema level via Coded Value Domains (discrete dropdown enumerations) and Range Domains (minimum and maximum numeric boundaries), governed by split and merge policies.
Subtypes partition a single feature class into logical subsets based on an integer attribute field, allowing features to share a physical table while supporting customized default values, unique domain assignments, and distinct connectivity rules.
Last updated: September 2026
Geodatabase Schema Architecture: Feature Datasets, Subtypes & Attribute Domains
Quick Summary: In modern GIS systems, the geodatabase provides a comprehensive object-relational model for spatial data management. Beyond storing simple geometries, geodatabases enforce advanced organizational and behavioral rules. Feature datasets enforce a shared spatial reference for contained classes, attribute domains constrain permitted values, and subtypes partition a feature class into logical groups with distinct defaults and business rules. These controls improve integrity but do not replace validation and governance.
Enterprise vs. File Geodatabase Architecture
The geodatabase architecture provides two distinct deployment models designed for different institutional scales: File Geodatabases (FGDB) and Enterprise Geodatabases (EGDB) . +-----------------------------------------------------------------------------------+
- | FILE GEODATABASE (.gdb) | ENTERPRISE GEODATABASE (RDBMS) |
- +---------------------------------------+-------------------------------------------+
- | • Stored in a file system directory | • Stored within an RDBMS (PostgreSQL, |
- | • Binary proprietary tables (.gdbtable| Oracle, SQL Server, SAP HANA) |
- | • 1 TB default capacity per table | • Unlimited capacity (governed by DBMS) |
- | • Single-user editing per table | • Concurrent multi-user editing |
- | • File system read/write locks | • Traditional and Branch Versioning |
- | • No native user permissions | • DBMS roles, privileges, row-level security|
- | • Standalone desktop workstations | • Enterprise client-server & web services |
- +---------------------------------------+-------------------------------------------+
- File Geodatabase Architecture
A File Geodatabase is stored as a folder in the file system with the .gdb extension, containing binary files that store schema definitions, vector geometries, attribute tables, indexes ( .spx , .atx ), and transaction locks ( .lock ).
Storage Capacity: Each table or feature class has a default capacity of 1 TB , which can be expanded to 256 TB using custom configuration keywords.
Concurrency & Locking: Supports unlimited concurrent readers, but only one active editor per feature class or table at any given time. Editing places a shared lock on the geodatabase and an exclusive write lock on the target table, preventing other users from editing that specific dataset simultaneously.
Portability: Highly portable across operating systems (Windows, Linux, macOS) without requiring database server software or client licensing.
Enterprise Geodatabase Architecture
An Enterprise Geodatabase (historically referred to as ArcSDE) stores spatial datasets inside a commercial or open-source relational database management system (such as PostgreSQL, Microsoft SQL Server, Oracle, or SAP HANA). Rather than operating as standalone files, the geodatabase logic is integrated directly into the database engine via system repository tables and dynamic link libraries.
Client Direct Connect: Modern GIS applications connect directly to the underlying RDBMS using native database client drivers, eliminating the legacy ArcSDE application server middleware.
System Metadata Tables: System catalog tables (prefixed with sde_ or gdb_ , such as sde_layers , sde_table_registry , sde_spatial_references , and sde_versions ) maintain schema relationships, coordinate reference metadata, and versioning states.
Enterprise Capabilities: Supports high-concurrency multi-user editing, long-running transactional versioning, point-in-time database recovery, automated archival tracking, and fine-grained role-based permissions.
Detailed Comparison: File vs. Enterprise Geodatabase
Architectural Parameter File Geodatabase (FGDB) Enterprise Geodatabase (EGDB)
Underlying Storage File system folder of binary files ( .gdbtable ) Relational database tables within an enterprise RDBMS
Storage Scalability 1 TB to 256 TB per feature class Governed only by enterprise disk storage and RDBMS limits
Concurrent Editing Single editor per feature class (file locking) Hundreds of simultaneous editors via versioning
Access Security Operating system file/folder permissions RDBMS user authentication, roles, schemas, and table grants
Advanced Workflows Standalone topologies, local networks Branch versioning, utility networks, historical archiving
Administration Managed directly via GIS desktop client Managed jointly by GIS Administrator and Database Administrator (DBA)
Feature Datasets: Purpose, Rules, and Structural Enforcements
A Feature Dataset is an organizational and behavioral container within a geodatabase designed to group spatially related feature classes. It is fundamentally different from a standard file system folder because it imposes strict spatial and structural constraints. +-----------------------------------------------------------------------------------+
- | FEATURE DATASET: Water_Distribution_Network |
- | Coordinate System: NAD 1983 State Plane Texas Central FIPS 4203 (US Feet) |
- | XY Tolerance: 0.00328 ft | XY Resolution: 0.000328 ft | Z & M Domains: Enabled |
- +-----------------------------------------------------------------------------------+
- | CONTAINED FEATURE CLASSES (Inherit Exact Spatial Reference & Tolerances): |
- | • Water_Mains (Polyline) |
- | • Water_Valves (Point) |
- | • System_Hydrants (Point) |
- | • Storage_Tanks (Polygon) |
- +-----------------------------------------------------------------------------------+
- | CONTAINED SPATIAL INTEGRITY RULES & ADVANCED MODELS: |
- | • Geodatabase Topology: "Water_Mains Must Not Self-Intersect" |
- | • Geodatabase Topology: "Water_Valves Must Be Covered By Boundary Of Water_Mains"|
- | • Geometric Network / Utility Network Connectivity Rules |
- +-----------------------------------------------------------------------------------+
- The Spatial Reference Mandate
The defining rule of a Feature Dataset is that every feature class within it must share the identical spatial reference system . This encompasses:
Horizontal Coordinate System: Identical projection, datum, spheroid, and central meridian.
Vertical Coordinate System: Identical vertical datum (if Z-values are enabled).
XY, Z, and M Tolerances: The spatial clustering threshold within which coordinates are considered geometrically coincident during topological validation.
XY, Z, and M Resolutions: The grid interval representing the minimum numerical precision of stored vertices.
Important
Once a Feature Dataset is created, its spatial reference and tolerance parameters are permanently locked . If an existing feature class was created in a different coordinate system, it cannot be imported or moved into the feature dataset without undergoing coordinate reprojection.
Advanced Models Dependent on Feature Datasets
Feature Datasets are not merely organizational; they are structural prerequisites for several advanced geospatial models that require strict coordinate coincidence:
Geodatabase Topologies: Topological validation rules (e.g., "Parcels Must Not Overlap", "County Boundaries Must Not Have Gaps") can only be established across feature classes that reside within the same Feature Dataset.
Utility Networks & Geometric Networks: Network connectivity models governing flow, valves, pipes, and electrical distribution lines must be modeled within a single Feature Dataset.
Parcel Fabrics: Cadastral parcel modeling systems require shared boundaries and control point networks constrained to a Feature Dataset.
Terrain Datasets: Multiresolution TIN-based elevation models built from mass points, breaklines, and clip polygons require unified tolerance structures within a Feature Dataset.
Standalone Feature Classes
A Standalone Feature Class resides directly at the root level of the geodatabase, outside of any Feature Dataset. Standalone feature classes:
Maintain their own independent spatial reference and tolerance settings.
Cannot participate in geodatabase topologies, geometric networks, or parcel fabrics.
Introduce lower system overhead and are preferred for independent thematic layers (e.g., satellite footprints, base imagery grids, standalone demographic census tables).
Attribute Domains: Enforcing Schema-Level Tabular Integrity
Attribute Domains are geodatabase-level rules that define the legal values allowed in attribute fields. Domains are defined at the geodatabase level and can be applied across multiple feature classes, subtypes, and tables. ATTRIBUTE DOMAINS IN THE GEODATABASE
- +-------------------------------------------------------+
- | GEODATABASE DOMAIN REPOSITORY |
- +---------------------------+---------------------------+
- |
- +-----------------------+-----------------------+
- | |
- v v
- [CODED VALUE DOMAIN] [RANGE DOMAIN]
- Discrete enumerated list • Continuous numeric bounds
- Stores Code, displays Description • Defines Min and Max thresholds
- Example: Pipe_Material • Example: Operating_Pressure
- Code: 1 -> "Ductile Iron" Min: 20.0 psi
- Code: 2 -> "PVC" Max: 120.0 psi
- Code: 3 -> "Cast Iron" Type: Float / Double / Integer
- Coded Value Domains vs. Range Domains
Characteristic Coded Value Domain Range Domain
Value Structure Discrete, qualitative list of explicit code-description pairs. Continuous, quantitative interval bounded by minimum and maximum values.
Valid Data Types Text, Short Integer, Long Integer, Float, Double, Date. Short Integer, Long Integer, Float, Double, Date (numeric only).
Storage Efficiency Stores compact code (e.g., integer 1 ) in the table while presenting human-readable text ( "Ductile Iron" ) in GIS applications. Directly stores the entered numeric value, rejecting any entry outside the [ Min , Max ] [\text{Min}, \text{Max}] [ Min , Max ] interval.
User Interface Dropdown selection list preventing typographical errors. Numeric input box validated on commit or via explicit validation tool.
Example Use Case Pipeline material, zoning classification, inspection condition rating. Pipe diameter ( 0.5 0.5 0.5 to 96.0 96.0 96.0 inches), water pressure ( 15.0 15.0 15.0 to 150.0 150.0 150.0 psi), asset age.
Split and Merge Policies
When spatial features are edited in GIS desktop clients, geometries are frequently split or merged. Domain policies dictate what happens to attribute values during these geometric operations:
Split Policies
Default Value: Attributes on both resulting features revert to the predefined default value for that field.
Duplicate: The original attribute value is copied identically to both resulting features (standard for categorical codes like material type or county name).
Geometry Ratio: The attribute value is divided proportionally based on the geometric ratio of the split features. For example, if a 10-acre parcel with an estimated yield of 100 bushels is split into 7-acre and 3-acre parcels, the yield is divided into 70 and 30 bushels.
Merge Policies
Default Value: The attribute of the newly merged feature reverts to the field default.
Sum: The numeric attribute values of the merged features are added together (useful for population counts or square footages).
Weighted Average: The resulting attribute is calculated as the average of the merged features' values, weighted by their respective lengths or areas.
Subtypes: Partitioning Feature Classes for Performance and Flexibility
Subtypes are subsets of features within a single feature class that are partitioned based on an integer attribute field (Short Integer or Long Integer). Subtypes allow features that share the same geometry type and general schema to behave differently without requiring separate tables. +-----------------------------------------------------------------------------------+
- | FEATURE CLASS: water_distribution_mains (Line Feature Class) |
- | Subtype Field: asset_subtype (Long Integer) |
- +-----------------------------------------------------------------------------------+
- | SUBTYPE 1: Transmission Mains |
- | • Default Diameter: 24.0 inches |
- | • Diameter Domain: Range_Transmission_Diameter (16.0 to 72.0 inches) |
- | • Material Domain: Coded_Steel_Concrete_Only |
- | • Topology Rule: Must Not Cross Other Transmission Mains |
- +-----------------------------------------------------------------------------------+
- | SUBTYPE 2: Distribution Mains |
- | • Default Diameter: 8.0 inches |
- | • Diameter Domain: Range_Distribution_Diameter (4.0 to 12.0 inches) |
- | • Material Domain: Coded_Ductile_PVC_HDPE |
- | • Topology Rule: Must Connect to Valves or Fittings at Dead Ends |
- +-----------------------------------------------------------------------------------+
- | SUBTYPE 3: Service Laterals |
- | • Default Diameter: 1.0 inch |
- | • Diameter Domain: Range_Service_Diameter (0.75 to 2.0 inches) |
- | • Material Domain: Coded_Copper_PEX_Only |
- | • Topology Rule: Must Connect to Distribution Main and Water Meter |
- +-----------------------------------------------------------------------------------+
Why Use Subtypes Instead of Separate Feature Classes?
Creating separate feature classes for every asset variation (e.g., transmission_mains , distribution_mains , service_laterals ) introduces severe database overhead:
Table Proliferation: Triples or quadruples the number of database tables, spatial indexes, and layers that must be maintained.
Slow Query Performance: Running queries or spatial overlays across the entire pipeline network requires complex UNION operations across multiple tables.
Cluttered Map Documents: Each feature class must be added, symbolized, and labeled independently.
Using Subtypes consolidates all features into a single physical database table , maximizing spatial index efficiency and query performance, while preserving tailored behaviors:
Each subtype can have its own default values for each attribute column.
Each subtype can bind to different attribute domains for the same field (as shown above, where diameter domains differ across subtypes).
Each subtype can enforce unique topological and connectivity rules .
Subtype Field Requirements
Caution
The subtype field MUST be an integer data type (either Short Integer or Long Integer). Text (string), floating-point, or date fields cannot be configured as subtype fields. Each subtype is formally identified by a unique integer code (e.g., 1 , 2 , 3 ) paired with a descriptive label.
Summary of Common Exam Traps
Caution
Exam Trap 14.2.1: The Misconception That Feature Datasets Are Simple Folders. Never treat a Feature Dataset as a simple folder or catalog group. It is an active spatial constraint. Every feature class inside it MUST share the exact same spatial reference, XY tolerance, and resolution. You cannot place a WGS84 feature class and a State Plane feature class into the same Feature Dataset.
Caution
Exam Trap 14.2.2: Invalid Data Types for Subtype Fields. Exam questions often present scenarios where an analyst attempts to create subtypes based on a text field like asset_category containing strings ( "Residential" , "Commercial" ). This operation will fail. A subtype field must be defined as a Short or Long Integer.
Caution
Exam Trap 14.2.3: Applying Duplicate Split Policy to Extensive Attributes. If an extensive quantitative attribute (such as parcel acreage, construction cost, or total building square footage) is assigned a Duplicate split policy, cutting a feature in half will assign the entire original value to both resulting pieces, artificially doubling the total reported asset value. Extensive attributes must be assigned a Geometry Ratio split policy.