Geodatabase terminology

The following terms are used in this documentation for the geodatabase topics in ArcGIS Pro.

Geodatabase

A geodatabase is a database or file structure used primarily to store, query, and manipulate spatial data. Geodatabases store geometry, a spatial reference system, attributes, and behavioral rules for data. Various types of geographic datasets can be collected within a geodatabase, including feature classes, attribute tables, raster datasets, network datasets, topologies, and many others. Geodatabases can be stored in relational database management systems (enterprise geodatabase), in a system of files (file geodatabase), or in a sqlite database (mobile geodatabase).

Term	Description	Related resources
File geodatabase	A file geodatabase is stored as multiple files in a folder with a .gdb extension. Each dataset is contained in a single file. By default, files can grow to 1 TB, but this can be changed to 4 or 256 TB using a configuration keyword.	File geodatabases Create a file geodatabase Compress file geodatabase data Upgrade a file geodatabase File geodatabase size and name limits
Mobile geodatabase	A mobile geodatabase is stored in an SQLite database that is entirely contained in a single file and has a .geodatabase extension.	Mobile geodatabases Create a mobile geodatabase Load ST_Geometry to a mobile geodatabase for SQL access Mobile geodatabase size and name limits
Enterprise geodatabase	An enterprise geodatabase, also known as a multiuser geodatabase, is stored in a relational database. An enterprise geodatabase can be virtually unlimited in size and number of users; the limits differ depending on the database management system (DBMS) vendor.	Geodatabase management Geodatabases in IBM Db2 Geodatabases in Oracle Geodatabases in PostgreSQL Geodatabases in SAP HANA Geodatabases in Microsoft SQL Server

Geodatabase dataset types

The following table describes the types of datasets that can be created in a geodatabase in ArcGIS Pro:

Term	Description
3D object feature layer	A 3D object feature layer is used to store and manage advanced 3D geometry-type features in a geodatabase. These 3D objects represent the outer shell and interior space of features that occupy a discrete area or volume in three-dimensional space—such as buildings, vehicles, vegetation, and more—using advanced visualization techniques like physically based rendering (PBR) and animations.
Annotation	Annotation is text or graphics that can be individually selected, positioned, and modified. An annotation may be manually entered or generated from labels. There are two kinds of annotation in a geodatabase: Standard—Is not formally associated with features in the geodatabase. An example of standard annotation is the text on a map for a mountain range. No specific feature represents the mountain range, but it is an area you want to mark. Feature linked—Is associated with a specific feature in another feature class in the geodatabase. The text in feature-linked annotation reflects the value of a field or fields from the feature to which it's linked. For example, the water transmission mains in a water network can be annotated with their names, which are stored in a field in the transmission mains' feature class.
Catalog dataset	A catalog dataset is a container for item references, which are called catalog dataset items. The item references points to various data sources—from local or network file shares, or your portal.
Dimensions	Dimensions are a special kind of geodatabase annotation for showing specific lengths or distances on a map. A dimension may indicate the length of a side of a building or land parcel, or the distance between two features, such as a fire hydrant and the corner of a building.
Feature class	A feature class is a collection of geographic features with the same geometry type (such as point, line, or polygon), the same attributes, and the same spatial reference. Feature classes allow homogeneous features to be grouped into a single unit for data storage purposes. For example, highways, primary roads, and secondary roads can be grouped into a line feature class named roads. The most commonly used types of feature classes are point feature class , line feature class , and polygon feature class . Feature classes can also store 3D objects, annotation, and dimensions.
Feature dataset	A feature dataset is a collection of thematically related feature classes that share a common coordinate system. Feature datasets are used to facilitate creation of controller datasets (sometimes also referred to as extension datasets), such as a parcel fabric, topology, or utility network.
Geoprocessing toolbox	A geoprocessing toolbox can contain a series of user-created geoprocessing tools, scripts, and models. Note: Toolboxes are not supported in a mobile geodatabase.
Mosaic dataset	A mosaic dataset is used to manage, display, analyze, serve, and share imagery and raster data. Note: Mosaic datasets are not supported in a mobile geodatabase.
Oriented imagery dataset	An oriented imagery dataset manages a collection of images in which each image has a specific direction or angle, such as those taken from camera angles aimed near the horizon (for example, oblique views, bubble, 360-degree, street-side, and inspection imagery) and from imagery taken looking straight down at the ground (for example, traditional satellite imagery). Oriented imagery datasets are useful for managing imagery from sources like street-level cameras, drones, or oblique aerial photography. They allow you to better understand the context of a given location by viewing it from multiple perspectives.
Raster dataset	A raster dataset is any valid raster format organized into one or more bands covering an extent. Each band consists of an array of pixels (cells), and each pixel has a value. It is the basic raster data storage model on which others are built, such as mosaic datasets. Note: Raster datasets are not supported in a mobile geodatabase.
Relationship class	A relationship class stores information about the relationship or association of related records between two feature classes, between a feature class and a nonspatial table, or between two nonspatial tables.
Table	A table is the basic storage object in the database. Tables are composed of columns and rows. Each row represents a single record. Each column represents a field of the record. Each field can store a specific data type, such as number, date, or text.
Trajectory dataset	A trajectory dataset manages a collection of trajectory files for working with and visualizing satellite altimetry sensors. Satellite altimetry data measures the elevation or height of the earth's surface at discrete points along the satellite's path and is especially useful in advancing our knowledge of ocean, ice sheet topography, and global climate. Note: Trajectory datasets are not supported in a mobile geodatabase.
View	A view is a stored query that selects data from the tables you specify in the view definition. Views can include a single table, multiple tables, and subqueries.

Geodatabase controller dataset types

The following table describes the types of controller datasets that can be created in a geodatabase in ArcGIS Pro:

Term	Description
Network dataset	A network dataset is used to model transportation networks. They are created from source features, which can include simple features (lines and points) and turns, and they store the connectivity of the source features. When you perform a network analysis, it is always done on a network dataset.
Parcel fabric	A parcel fabric provides a comprehensive framework for managing, editing, and sharing parcel data in both a multiuser ArcGIS Enterprise and single-user environment. Parcel fabrics support the needs of land administration and cadastral mapping, providing tools for accurately representing land ownership boundaries, easements, rights-of-way, and other land-related features.
Terrain dataset	A terrain dataset is a multiresolution, TIN-based surface built from measurements stored as features in a geodatabase. They're typically made from lidar, sonar, and photogrammetric sources. Terrains reside in the geodatabase, inside feature datasets with the features used to construct them.
Topology	A topology defines how point, line, and polygon features share coincident geometry. Topology defines and enforces data integrity rules (for example, there should be no gaps between polygons), and topological relationship queries, navigation, editing, and feature construction. For example, street centerlines and census blocks share common geometry, and adjacent soil polygons share their common boundaries.
Trace network	A trace network is the main component users work with to visualize, manage, and analyze simple connectivity models such as rail and hydro in ArcGIS Pro.
Utility network	A utility network is used to model and analyze complex network systems such as those for water, gas, electric, telecom, sewer, and stormwater. It is designed to model all of the assets that make up your system—such as wires, pipes, valves, zones, devices, and circuits—and allows you to build real-world behavior into the network features you model.

Geodatabase dataset properties

The following table describes various dataset properties that can be applied to datasets in a geodatabase in ArcGIS Pro:

Term	Description
Fields	Fields are the components that provide structure for a table. Tabular information consists of rows and columns. In ArcGIS, rows are referred to as records, and columns as fields. Each field in a table can store a specific type of data, such as a number, date, or piece of text. Fields form the attribute information for each layer in the map or stand-alone table.
ArcGIS field data types	Every feature class and table is made up of fields that are defined by their data types. A field's data type is the most important property because the data type you select determines the type of data the field can store. In ArcGIS Pro, available data types that can be applied to a field include a variety of numerical types (integers, float, double), text, date only, timestamp offset, binary large objects (BLOB), and globally unique identifiers (GUIDs). See ArcGIS data types for a complete list and additional details about each data type. Additional field properties that can be set—such as precision, scale, and length of a field—are also dependent on the data type of the field.
Attribute index	An attribute index is used to locate records that match an attribute query. Attribute indexes can speed up joins and other attribute queries on tables, feature classes, shapefiles, or attributed relationship classes. An attribute index is an alternate path used by ArcGIS to retrieve a record from a table. For most types of attribute queries, it is faster to look up a record with an index than to start at the first record and search through the entire table.
Spatial index	A spatial index is used to quickly locate features within feature classes and perform many selection and identification tasks in ArcGIS Pro. Identifying a feature, selecting features by pointing or dragging a box, and panning and zooming all require ArcGIS Pro to use the spatial index to locate features
Spatial reference	A spatial reference is the coordinate system used to store each feature class and raster dataset, as well as other coordinate properties such as the coordinate resolution for x,y coordinates and optional z- and measure(m)-coordinates. In the geodatabase, the coordinate system and other related spatial properties are defined as part of the spatial reference for each dataset.
Configuration keyword	Configuration keywords represent a setting or group of settings that is used by a file or enterprise geodatabase to identify where or in what format to store the data in each dataset. You can use configuration keywords when you create a table or feature class to specify how data is stored.

Geodatabase data design and functionality

The following table describes various data design and modeling tools that can be applied to datasets in a geodatabase in ArcGIS Pro:

Term	Description
Archiving	Archiving provides the functionality to record and access changes made to all or a subset of data in a geodatabase. Archiving is the mechanism for capturing, managing, and analyzing data change over time.
Attachments	Attachments are used to associate copies of media files, such as documents and images, with features in a feature class or rows in a stand-alone table. This allows you to add information and context, for example, by attaching a picture to a feature class that represents a particular asset in the field, or by attaching a damage assessment report for a specific building in a list of buildings.
Attribute rules	Attribute rules enhance the editing experience and improve data integrity for geodatabase datasets. They are user-defined rules that can be used to automatically populate attributes, restrict invalid edits during edit operations, and perform quality assurance checks on existing features.
Attribute rule - Calculation attribute rules	Calculation rules are used to automatically populate attribute configurations on a feature. They can be created as immediate calculation rules or batch calculation rules, depending on when the rule needs to be evaluated as follows: Immediate calculation rules—Rule evaluation occurs immediately during edit operations. Evaluation is controlled by the type of triggering event (insert, update, or delete operations). For update events, you can optionally specify a list of triggering fields. Batch calculation rules—Rule evaluation occurs at a user-specified time. You can evaluate rules using the Error Inspector view or the Evaluate Rules tool.
Attribute rule - Constraint attribute rules	Constraint rules specify permissible attribute configurations and general relationships on a feature. Unlike calculation rules, constraint rules are not used to populate attributes; they are used to ensure that specific conditions are met on a feature.
Attribute rule - Validation attribute rules	Validation rules specify permissible attribute configurations and general relationships on a feature. They are used to check features in a dataset based on a specific requirement or constraint. The rule evaluation occurs for existing features at a user-specified time, and if rules are violated, error features are created. This process allows you to perform quality assurance checks on features and review areas of concern as an iterative process.
Attribute rule - Template attribute rules	In addition to authoring a user-defined attribute rule, you can create an attribute rule using a template. There are templates available to assist you with authoring attribute rules for specific workflows. Attribute rule templates allow you to benefit from attribute rule functionality without having to author the Arcade script expression.
Contingent values	Contingent values, sometimes called contingent attribute values, are a data design feature that allows you to make values in one field dependent on values in another field.
Domains	Attribute domains are rules that describe the available values of a field type. They are used to constrain the values allowed in any particular attribute for a table or feature class. They provide a method for enforcing data integrity by limiting what can be placed on a field to a valid list or range of choices.
Editor tracking	Editor tracking provides a setting on feature classes and tables that allows you to automatically record information about any inserts and updates that are made. It maintains a record of the editor who created or modified the data and a time stamp of when the edit occurred.
Subtypes	Subtypes are a subset of features in a feature class, or objects in a table, that share the same attributes. They are used as a method to categorize data.

Geodatabase data editing

The following table describes various data editing options and mechanisms that can be applied to datasets in a geodatabase in ArcGIS Pro:

Term	Description
Branch versioning	Facilitates the Web GIS model by allowing multiuser editing scenarios and long transactions while working with web feature layers. For more information, see Branch version scenarios.
Traditional versioning	Provides the flexibility to work within versions for long transactions when accessed directly from the enterprise geodatabase and a simplified editing experience when using feature services to accommodate shorter transactions. For more information, see Traditional version scenarios.
Traditional versioning (move edits to base)	An optional form of traditional versioning that allows editors and applications to have direct access to the base data while also allowing other editors to work in their own isolated versions.
Nonversioned editing	A data management strategy that allows users to edit data without working with multiple versions. Nonversioned edits are equivalent to standard database short transactions. When editing nonversioned data in ArcGIS Pro, each transaction is automatically committed to the database, so you do not need to save the edits. The changes you make are available to all other users and applications accessing the data when your transaction is complete.
Geodatabase locks	ArcGIS Pro applies and releases locks on datasets in an enterprise geodatabase as users view and edit data. These locks are needed to maintain the consistency of the data and versions. As objects in a geodatabase are locked, access to these objects changes based on whether a shared or exclusive lock is held.

See versioning vocabulary for additional common terms encountered in the versioning documentation

Geodatabase data distribution

The following table describes various data distribution options that can be applied to datasets in a geodatabase in ArcGIS Pro:

Term	Description
Geodatabase replication	Geodatabase replication allows you to create copies of data across two or more geodatabases and allows users to edit data in each geodatabase independently so changes to the data can be synchronized.
Checkout replica	Checkout/check-in replication allows you to edit data in the child replica and synchronize these edits with the parent replica. See Geodatabase replication types for more information.
One-way replica	One-way replication allows data changes to be sent multiple times in a single direction, from parent to child replica or from child to parent replica. One-way replicas persist after synchronization, allowing you to continue sending data changes.
Two-way replica	Two-way replication allows data changes to be sent multiple times from the parent replica to the child replica and from the child replica to the parent replica. If the same row is edited in both replica geodatabases, it is detected as a conflict when the replicas are synchronized.
Synchronization	Synchronization involves one replica sending data changes and the relative replica receiving changes. Data changes include inserts, updates, and deletes made in the replica version.
Offline workflows	If your network connectivity is unreliable or slow, you can take web layer data offline in ArcGIS Pro. When you do this, you work with a local copy of the data. This allows you to make edits and complete your work without the requirement to be connected to the network. Once network availability is restored, you can upload your local edits. See Take a map offline to learn more about how to configure this workflow.
Feature service replica	Feature service replicas provide the mechanism that allows you to synchronize offline feature layers with the source data. The feature service replica receives edits made offline that are subsequently synchronized to the source feature layer. During synchronization, the feature service replica also receives the edits made in the source feature layer and makes them available to the feature layer that was taken offline.
Replica version	A replica version is automatically created each time you download and take a map offline that contains an editable feature service that is published with the Create a version for each downloaded map option enabled. If the editable feature service contains traditional versioned data and is published with the Create a version for each user option enabled, a replica version is created for each user who takes the map offline. Each replica version is associated with a feature service replica.