The geodatabase is the native data structure for managing and editing a collection of datasets in ArcGIS Pro. There are three primary dataset types—tables, feature classes, and raster datasets.
In ArcGIS Pro, you can enhance these primary dataset types to model spatial relationships, add advanced behaviors, and improve data integrity. By building on these fundamental datasets in the geodatabase, you can extend their capabilities as needed.
Dataset types in a geodatabase
The following sections list each type of dataset that can be added or created in a geodatabase and provides a link to its corresponding help page or geoprocessing tool.
3D object
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.
The associated tables stored with 3D objects support multiple formats with their own assets for a lossless conversion and support high-level PBR materials, which give surfaces like glass or metal shading properties such as reflection, shadowing, normal mapping, and roughness. Collectively, this information and properties help make 3D objects look more realistic. 3D object feature layers can be stored in a file, enterprise, or mobile geodatabase.
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 the 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.
Dimension
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 a 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.
Mosaic datasets are designed to manage, display, query, and analyze collections of imagery or raster data, such as satellite imagery, aerial photographs, and digital elevation models. They can efficiently handle large volumes of raster data and allow for dynamic mosaicking and on-the-fly processing of images through stored raster functions.
Note:
Mosaic datasets are not supported in a mobile geodatabase.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.
License:
A network dataset requires the ArcGIS Network Analyst extension.
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.
Note:
Oriented imagery datasets are not supported in a mobile geodatabase.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.
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. See a list of all raster file formats, satellite sensors, aerial cameras, and product formats ArcGIS Pro supports.
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.
Tables can store descriptive attributes as well as spatial attributes. Tables that contain spatial attributes are called feature classes. The information displayed in a table comes directly from the attribute information stored in the data source. The geodatabase uses tables to store and manage the attributes and properties of geographic objects.
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.
License:
A terrain dataset requires the ArcGIS 3D Analyst extension.
Note:
Terrain datasets are not supported in a mobile geodatabase.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. For a list of available topology rules, see geodatabase topology rules and topology error fixes for points, lines, and polygons.
For example, the rule Must not overlap is used to manage the integrity of features in the same feature class.
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.
The trace network's trace functionality is an analytics task that ensures optimal paths exist for resources to travel.
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. The data is collected as sequential points along the sensor's path and stored in netCDF and HDF formats using a trajectory data structure. Each file contains sensor properties, such as start time, end time, and the location of each measurement from many sensors, such as Sentinel-3 (SRAL), Sentinel-6, ICESat-2, CryoSat-2, and more for a single track or pass over the Earth's surface.
Note:
Trajectory datasets are not supported in a mobile geodatabase.Utility network
A utility network is a geodatabase controller dataset used to model and analyze complex network systems such as those for water, gas, electric, telecom, sewer, storm water, and so on. 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.
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.
Views can provide subsets of rows or columns in a predefined way. This reduces the volume of data transferred from the database to the client, which can improve performance. You can also control what data users see by limiting the columns or rows present in the view. For example, employees concerned with assessing inventory and ordering products do not need to see the names of the people who purchased products or the sales price. Rather than give those employees access to the entire table where that information is stored, you can create a view that does not include those columns and grant the inventory employees select privilege on the view.
A view can be defined on tables in your database.