Basic concepts

Attribute tables

Attribute tables store additional information on elements in a map, i.e. extra tabular data which relates to the mapping units, points, segments, or polygons in your maps.

Raster, polygon, segment and point maps that use a domain of the class or ID type can have attribute tables. The domain of the attribute table should be the same as the domain of the map to which it relates. The domain is the relational link between the map and the attribute table.

Maps of domain type Value contain purely values; they cannot have attributes.

When a map that is linked to an attribute table is displayed in a map window, and you double-click in the map, the attributes of the selected class or ID are shown and can be edited. Whether an attribute table is linked to a map can be inspected in the properties sheet of the map.

The best way to create an attribute table is:

For more information, refer to How to view and edit the properties of an object and How to create a table.

You can perform calculations on your attribute data in the attribute table with Table Calculation, and you can also derive another map from a column in an attribute table with the Attribute Map, Attribute Polygon Map, Attribute Segment Map or Attribute Point Map operations.

Example:

A map with terrain units may have the following classes: Lagoon plain, Coastal upland, Infilled valleys, Inland levees, Volcanic hills moderately steep, Volcanic hills steep, Colluvial footslopes, etc.

Attributes for these classes might be: minimum and maximum slope, slope length, drainage density, genesis, etc.