|Introduction | Sustainability Factors | Content Categories | Format Descriptions | Contact|
|Full name||ESRI Geodatabase (File-based)|
|Description||The GeoDB, ESRI Geodatabase (File-based) or GeoDB_File is a subtype of the GeoDB. The GeoDB is the primary data storage model for ArcGIS. It is a container of spatial and attribute data and enables the user to store many different types of GIS data within its structure. Its structure is implemented either in an RDBMS or as a collection of files in a file system. As an implementation of the GeoDB data model, the GeoDB_File is designed to:
As a subtype of the geodatabase data model, the GeoDB_File is implemented as a collection of binary files in a native file system. It is designed as a single-user geodatabase. The GeoDB_File has no size capacity limit, although by default, within the geodatabase each table can store up to 1 terabyte of data. The table size limitation can be changed so that a table can store up to 256 terabytes, if desired. Each GeoDB_File can hold many datasets. Within each dataset, each feature class can scale up to hundreds of millions of vector features.The GeoDB_File does not support versioning or geodatabase archiving. It supports limited geodatabase replication if used as a child geodatabase in either one-way or checkout/check-in geodatabase replication. Security and permissions associated with the GeoDB_File are those provided by the operating file system as is any database administration.
The GeoDB_File is best used for personal or locally (file system) stored GIS projects rather than the GeoDB, ESRI Geodatabase (Personal) or GeoDB_Personal format that is implemented in Microsoft Access because it offers more functionality and better performance. The GeoDB_File can be converted, using migration tools included in the ArcGIS software suite, to the GeoDB_SDE implementation of the GeoDB data model when multi-user editing, more complexity in description, or more capacity for spatial analysis is desired. See Migrating your existing data into the Geodatabase and Migrating Coverages to Geodatabases for more information on converting other ESRI formats to the GeoDB_File format.
|Production phase||Full life cycle format alternative to the other single-user ESRI Geodatabase, the GeoDB_Personal format.|
|Relationship to other formats|
|Affinity to||ArcInfo Coverage, ESRI ArcInfo Coverage . The ArcGIS coverage format is a legacy format superseded by the ESRI Arc Geodatabase data model that is expressed in single and multi-user geodatabases. Coverages cannot be edited in ArcGIS 8.3 and subsequent versions.|
|Subtype of||GeoDB, ESRI Arc Geodatabase. The data model that serves as the framework for all Arc geodatabases, whether single user or multi-user. This data model has superseded the ESRI ArcInfo Coverage format which cannot be edited in ArcGIS 8.3 and subsequent versions.|
|Affinity to||GeoDB_Personal, GeoDB, ESRI Geodatabase (Personal). An option for data storage for a single-user ESRI Geodatabase that is implemented as a single Microsoft Access file. As of 2011, ESRI recommends GeoDB_File file-based geodatabases over Microsoft Access Personal Geodatabases, because they offer more functionality and better performance. The Personal Geodatabase format is not described at this time on this website.|
|Affinity to||GeoDB_SDE, GeoDB, ESRI Geodatabase ArcSDE. The spatial database engine is the multi-user option for data storage for an ESRI Geodatabase.|
|Affinity to||GeoDB_XML, ESRI Geodatabase (XML). Used by ArcGIS to import and export all items and data in a geodatabase such as domains, rules, feature datasets, and topologies.|
|LC experience or existing holdings|
|Disclosure||A proprietary database structure used in ESRI GIS products.|
|Documentation||ESRI does not provide a complete specification of the database structure employed in ArcGIS. The different types of geodatabases are described in Types of geodatabases, ArcGIS 9.2 Desktop Help, January 14, 2008 and in April 2014 at Types of geodatabases, in ArcGIS for Desktop Help.|
|Adoption||The geodatabase data model was introduced by ESRI in the late 1990s with the release of version ArcGIS 8.0. The release of the ArcGIS suite constituted a major change in ESRI's software offerings, aligning all their client and server products under one software architecture known as ArcGIS, developed using Microsoft Windows COM standards. While the ESRI shapefile is still quite prevalent in the industry, at least for sharing and transferring datasets among different systems, the geodatabase is becoming the mechanism of choice for data sharing and data interoperability among organizations, and departments within a single organization. While older ESRI (non-ArcGIS) products are still available, most of the GIS software market share that ESRI holds (approximately 36 percent worldwide as of 2002) is taken by ArcGIS products. See ArcGIS from Wikipedia and COTS GIS: The Value of a Commercial Geographic Information System for more information.|
|Transparency||The data in a GeoDB_File database is in an undocumented binary form and usually compressed. Until June 2011, there was no way to understand the contents except through ArcGIS procedures. In June 2011, ESRI published a limited API (in C++) that provides some capabilities for exploring and extracting data directly.|
|External dependencies||Software dependencies: File (single user) geodatabases are freely available to all purchasers of ArcGIS desktop software, i.e., ArcView, ArcEditor, and ArcInfo. There is a varying level of functionality between ArcView, ArcEditor, and ArcInfo. ArcView allows the user to create and edit single user geodatabases. The user cannot, however, create or manage geometric networks and relationships. Basic functionality such as defining attribute domains is included. For a more robust geodatabase environment, ArcEditor or ArcInfo are recommended as they provide full functionality of the geodatabase data model. Both single user and and multiuser geodatabases can be created and edited. Features such as geometric networks, relationships, feature-lined annotation, multiuser editing, custom data models, and image storage are all incorporated within ArcEditor and ArcInfo. A comparison of functionality among ArcView, ArcEditor, and ArcInfo can be found on Page 9 of Working with the Geodatabase: Powerful Multiuser Editing and Sophisticated Data Integrity.|
|Technical protection considerations||No concerns.|
|GIS images and datasets|
|Normal functionality||The GeoDB is designed to have a comprehensive GIS data model, geospatial modeling capabilities, and a scalable architecture. Thus, as a GeoDB, (and like the GeoDB_SDE, a multi-user subtype of the GeoDB), the GeoDB_File is designed to be able to create topologies, raster catalogs, network datasets, terrain datasets, address locators, and other means for providing GIS functionality for managing, manipulating and analyzing data. The single-user geodatabase formats and related software do not provide support for versioning, geodatabase replication, geodatabase archiving or long term (time) transaction management.|
|Support for GIS metadata||There are no special provisions for containing GIS metadata in the GeoDB_File format.|
||The .gdb file is a container to hold the feature datasets, feature classes, and associated tables that are related to each other. When the .gdb file is opened using ArcGIS software, various file types can usually be found within .gdb file including attribute tables, topologies and feature classes such as polygons. Associated data important for the use of the data in the .gdb such as shapefiles and .xml files containing metadata need to be kept with the .gdb, usually in the same file directory in order to retain the associations.|
File-based datasets do not support joint editing, except by means of operational procedures. When more than one user needs data access, files are either copied or mounted across a network. It is possible to have more than one editor in the GeoDB_File at the same time, provided they are editing in different tables, feature classes or feature datasets. Generally, an RDBMS-backed geodatabase is used in preference to a file-based geodatabase when group editing is required.
In late 2011, the Geospatial Multistate Archive and Preservation Project (GeoMAPP) produced a report comparing the archival challenges presented by the GeoDB_File and GeoDB_Personal formats.