Feature Class

What is a Feature Class?

Feature classes are homogeneous collections of common features, each having the
same spatial representation, such as points, lines, or polygons, and a common set
of attribute columns, for example, a line feature class for representing road
centerlines. The four most commonly used feature classes are points, lines,
polygons, and annotation (the geodatabase name for map text).

In the illustration below, these are used to represent four datasets for the same area: (1) manhole
cover locations as points, (2) sewer lines, (3) parcel polygons, and (4) street name annotation.

In this diagram, you might also have noted the potential requirement to model
some advanced feature properties. For example, the sewer lines and manhole
locations make up a storm sewer network, a system with which you can model
runoff and flows. Also, note how adjacent parcels share common boundaries. Most
parcel users want to maintain the integrity of shared feature boundaries in their
datasets using a topology.
As mentioned earlier, users often need to model such spatial relationships and
behaviors in their geographic datasets. In these cases, you can extend these basic

feature classes by adding a number of advanced geodatabase elements, such as

topologies, network datasets, terrains, and address locators.

Types of Feature Classes

A feature is an object that stores its geographic representation, which is typically a
point, line, or polygon, as one of its properties (or fields) in the row. In ArcGIS,
feature classes are homogeneous collections of features with a common spatial
representation and set of attributes stored in a database table, for example, a line
feature class for representing road centerlines.
When Creating a feature class, we will be asked to set the type of features to define the type
of feature class
Generally, feature classes are thematic collections of points, lines, or polygons, but
there are seven feature class types. The first three are supported in databases and
geodatabases. The last four are only supported in geodatabases.

Points: Features that are too small to represent as lines or polygons as well as point
locations (such as GPS observations).

Lines: Represent the shape and location of geographic objects, such as street centerlines
and streams, too narrow to depict as areas. Lines are also used to represent features that
have length but no area, such as contour lines and boundaries.

Polygons: A set of many-sided area features that represents the shape and location of
homogeneous feature types such as states, counties, parcels, soil types, and land-use
zones.

Annotation: Map text including properties for how the text is rendered. For example, in
addition to the text string of each annotation, other properties are included such as the
shape points for placing the text, its font and point size, and other display properties.
Annotation can also be feature linked and can contain subclasses.

Dimensions: A special kind of annotation that shows specific lengths or distances, for
example, to indicate the length of a side of a building or land parcel boundary or the
distance between two features. Dimensions are heavily used in design, engineering, and
facilities applications for GIS.

Multipoints: Features that are composed of more than one point. Multipoints are often
used to manage arrays of very large point collections, such as lidar point clusters, which
can contain literally billions of points. Using a single row for such point geometry is not
feasible. Clustering these into multipoint rows enables the geodatabase to handle massive
point sets.

Multipatches: A 3D geometry used to represent the outer surface, or shell, of features

that occupy a discrete area or volume in three-dimensional space. Multipatches comprise
planar 3D rings and triangles that are used in combination to model a three-dimensional
shell. Multipatches can be used to represent anything from simple objects, such as
spheres and cubes, to complex objects, such as iso-surfaces and buildings.

Feature class storage

Each feature class is managed in a single table. A shape column in each row is used to hold the
geometry or shape of each feature.

In the feature class table, the following are true:

Each feature class is a table.

Individual features are held as rows.

Feature attributes are recorded in columns.

The shape column holds each feature's geometry (point, line, polygon, and so forth).

The ObjectID column holds the unique identifier for each feature.

If you create a line feature class in a geodatabase, an additional field is added to

the feature class automatically to record the length of the line. If you create a
polygon feature class, two additional fields are added automatically to record the
length (perimeter) and area of each polygon feature. The units of measure for these
values depends on the spatial reference defined for the feature class. The names of
these fields vary depending on the database and spatial type you use. These are
required fields and cannot be modified.