GeoDatabases

GeoDatabases implement an object-based GIS data model (the geodatabase data model). Each feature is stored in a row in a table that contains common features (lines, polygons, etc.). The vector shape of the feature is stored in the tables's shape field with feature attributes in other fields. this is probably what we want to use for our Archaeology project!

In addition, GeoDatabases can store raster images, data tables, and references to other tables. GeoDatabases can hold all your data in one location! They are like adding coverages, shapefiles and raster images into a DBMS.

Geodatabases can have build-in behavior; geodatabase features are completely stored in a single database; and large geodatabase feature classes can be stored seamlessly, not tiled.

Basic objects are:

• points
• lines
• areas
• multi-[point|line|area]

You can extend these by creating your own custom objects with custom behaviors. In addition you have geodatabase specific types/behaviors described below.

Network Junction Features are points that play a topological role in a network (somewhat like nodes in coverages) and come in two flavors: Simple and Complex.

• Simple junction features might be used to represent a fitting that connects two pipes. It could have validation behavior that would ensure that connected pipes are of the correct diameter and materials.
• Complex junction features plays a more complex role in a network and may for instance represent an electric switch that in position (a) connects A-B and in position (b) connects A-C

       B
       |
       |
 A --------- C

Geodatabase objects are files that contain Personal Geodatabase FeatureDatasets. FeatureDatasets contain related objects