Geodatabases organize geographic data into a hierarchy of data objects. The geodatabase schema includes definitions, integrity rules, and behavior for each geographic dataset.
GIS application logic is used to implement integrity rules and GIS behavior on the simple relational structure.
Some of the structural elements of a geodatabase, listed below, are used to develop a rich, geographic information system.
A specialized feature class that stores text or graphics that provide information about features or general areas of a map. An annotation feature class may be linked to another feature class so that edits to the features are reflected in the corresponding annotation (i.e., feature-linked annotation).
A special type of geodatabase annotation that shows specific lengths or distances on a map. A dimension feature may indicate the length of a side of a building or land parcel, or it may indicate the distance between two features such as a fire hydrant and the corner of a building.
A collection of geographic features with the same geometry type (i.e., point, line, or polygon), the same attributes, and the same spatial reference. They allow homogeneous features to be grouped into a single unit for data storage purposes; for example, a feature class of city streets.
A collection of feature classes stored together that share the same spatial reference. Feature classes in a feature dataset share a coordinate system, and their features fall within a common geographic area. Feature datasets are used to help model spatial relationships between feature classes.
Edge and junction features that represent a directed-flow system network, such as a utility or hydrologic system, in which the connectivity of features is based on their geometric coincidence.
A collection of topologically connected network elements (e.g., edges, junctions, and turns) that are derived from network sources, typically used to represent an undirected-flow system network such as a road or subway system.
A collection of raster datasets defined in a table of any format, in which the records define the individual raster datasets that are included in the catalog. Raster catalogs can be used to display adjacent or overlapping raster datasets without having to mosaic them together in one large file.
Any valid raster format organized into one or more bands. Each band consists of an array of pixels (cells), and each pixel has a value (e.g., a Landsat satellite image).
A class similar to relationships that exist within an RDBMS. Relationship classes manage the associations between objects in one class (e.g., table or feature class) and objects in another. Objects at either end of the relationship can be features with geometry or records in a table.
A set of data elements arranged in rows and columns. Each row represents a single record. Each column represents a field of the record. Tables typically store stand-alone attribute information or information associated with a spatial location such as addresses.
The arrangement that constrains how point, line, and polygon features share geometry within a geodatabase. For example, street centerlines and census blocks share geometry, and adjacent soil polygons share geometry. Topology defines and enforces data integrity rules, topological relationship queries and navigation, and sophisticated editing tools. It also allows feature construction from unstructured geometry.