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:

You can extend these by creating your own custom objects with custom behaviors. The following sections describe geodatabase specific types/behaviors described below.

Point Features

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.

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

Line Features

Lines are built from three kinds of segments:

Line features can have custom drawing behavior that generalizes the line depending on the map scale or that controls the placement of annotation along the line.

Network edge features features are Line features that play a topological role in a network. They can be used for tracing and flow analysis.

Polygon Features

Polygon features represent areas. The are formed from the line features described above. They must be closed shapes, but may have discontinuous parts such as separate islands. Polygons can also contain "islands" or "lakes".

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

GeoDatabases (last edited 2009-05-24 20:47:30 by 24-183-238-75)