5.1 Esri Data Formats & Feature Storage

5.1 Esri Data Formats & Feature Storage

Modern GIS workflows in ArcGIS Pro require selecting appropriate vector feature storage formats based on dataset scale, access requirements, performance needs, and structural capabilities. ArcGIS Pro natively supports a wide spectrum of spatial data storage architectures, ranging from legacy file-based structures to modern relational database management systems and web-native formats. Understanding the technical specifications, file architectures, scaling boundaries, and editing restrictions of each format is critical for exam success and efficient data administration.

File Geodatabases (.gdb)

The File Geodatabase (.gdb) is the standard, recommended desktop storage format for Esri vector and raster datasets. Structurally, a File Geodatabase is not a single file, but a system directory (folder) containing binary files that hold spatial, attribute, and schema definition data. On disk, these folders bear the .gdb extension and appear in operating system file browsers as directories containing numerous encrypted or structured binary files (e.g., a00000001.gdbtable, a00000001.freelist).

Key Technical Specifications & Capabilities

• Cross-Platform Compatibility: File Geodatabases are fully cross-platform and can be accessed across Windows, Linux, and macOS environments without requiring data translation.
• Storage Limits: By default, each dataset or table within a File Geodatabase can hold up to 1 Terabyte (1 TB) of data. For extremely large datasets (such as high-density point clouds or national raster grids), administrators can configure keyword parameters during creation to expand individual table size limits up to 256 TB.
• Concurrency & Locking: File Geodatabases support a multi-user read / single-user edit locking model. Multiple users can concurrently view, query, and render layers stored within the same File Geodatabase. However, as soon as an editor initiates an edit session on a feature class within the geodatabase, ArcGIS Pro applies a schema/dataset lock (.sr.lock and .ed.lock files), preventing other users from editing any table or feature class in that geodatabase until the edit session is saved and closed.
• Rich Behavioral Support: File Geodatabases natively support advanced geodatabase functionality, including attribute domains, subtypes, feature topology, relationship classes, geometric networks, utility networks, and raster datasets.

Mobile Geodatabases (.geodatabase)

Introduced to streamline mobile and cross-platform workflows, the Mobile Geodatabase (.geodatabase) is a single-file vector storage container built on an SQLite database engine. Unlike File Geodatabases, a Mobile Geodatabase is stored as a single file on disk with the .geodatabase extension, making it extremely portable and easy to move via email, cloud storage, or direct file transfer.

Primary Use Cases & Operating Parameters

• Lightweight Footprint: Mobile Geodatabases leverage SQLite’s efficient, serverless database architecture, making them ideal for field data collection applications like ArcGIS Field Maps, ArcGIS Survey123, and custom runtime apps.
• Single-User Editing: Mobile Geodatabases support single-user editing workflows and basic geodatabase capabilities, such as domains, subtypes, and relationship classes.
• Cross-Platform Portability: Because SQLite is natively supported across mobile operating systems (iOS, Android) and desktop platforms, Mobile Geodatabases eliminate format translation overhead when synchronizing offline field edits back to desktop GIS applications.

Enterprise Geodatabases (RDBMS Backend)

For multi-user organizational environments requiring simultaneous multi-user editing, granular security controls, and enterprise transaction management, Esri provides the Enterprise Geodatabase architecture (formerly known as ArcSDE). An Enterprise Geodatabase is hosted within a commercial or open-source Relational Database Management System (RDBMS), such as Microsoft SQL Server, PostgreSQL, Oracle, SAP HANA, or IBM Db2.

Advanced Capabilities & Transaction Management

• Concurrent Multi-User Editing: Hundreds of users can concurrently query and edit datasets within the same database instance without encountering dataset-level file locks.
• Versioning Workflows: Enterprise Geodatabases enable sophisticated versioning mechanisms. Traditional Versioning supports long-transaction workflows, allowing users to isolate edits in named child versions before reconciling and posting back to the DEFAULT version. Branch Versioning provides web-GIS-native versioning designed for services-based editing across ArcGIS Online and ArcGIS Enterprise portals.
• Database Administration: Access privileges, spatial indexing, automated backups, and user authentication are managed directly through the underlying RDBMS engine and database administrator tools.

Legacy Shapefiles (.shp)

Developed by Esri in the early 1990s, the Shapefile remains a widely encountered vector data exchange format. A shapefile is not a single file but a collection of mandatory and optional component files sharing a common base file name in the same file directory.

Mandatory Component Files

1. .shp — Main file storing feature spatial geometry (coordinates).
2. .dbf — dBase IV table storing attribute data.
3. .shx — Index file storing feature geometry positional offsets.

Common optional files include .prj (coordinate system projection definition), .xml (metadata), and .cpg (character code page encoding).

Critical Limitations for EAPF_2025

• 2 GB Storage Boundary: Individual shapefile components (.shp or .dbf) cannot exceed 2 Gigabytes (2 GB) in file size. Reaching this limit corrupts the dataset.
• 10-Character Field Name Limit: Attribute field names in .dbf tables are strictly limited to 10 characters. Names exceeding 10 characters are truncated automatically upon conversion.
• NULL Value Handling: The dBase IV attribute format cannot store true NULL values for numeric fields. Unentered or missing numeric values are automatically converted to 0, which introduces serious data integrity risks in statistical analysis.
• Lack of Advanced Behavior: Shapefiles do not support domains, subtypes, relationship classes, feature datasets, topology rules, or raster storage.

GeoJSON and CAD Integration

GeoJSON (.geojson / .json)

GeoJSON is an open-standard, human-readable text format based on JSON (JavaScript Object Notation) designed for encoding spatial data structures (Points, LineStrings, Polygons, MultiPolygons). Widely used in web GIS and REST API integrations, GeoJSON files are easily parsed by web browsers. However, GeoJSON lacks native spatial indexing, making large GeoJSON datasets inefficient for desktop spatial analysis compared to File Geodatabases.

CAD Datasets (.dwg, .dgn)

ArcGIS Pro directly reads Computer-Aided Design (CAD) files created in AutoCAD (.dwg) and Bentley MicroStation (.dgn). When added to a map, ArcGIS Pro exposes CAD drawings as virtual feature datasets comprising five feature classes: Point, Polyline, Polygon, MultiPatch, and Annotation. CAD datasets are read-only in ArcGIS Pro until converted into geodatabase feature classes using the CAD To Geodatabase or Feature Class To Feature Class geoprocessing tools.