The PODS ESRI model is expressly designed for implementation as an object-relational ESRI geodatabase for use with ESRI’s ArcGIS® and ArcSDE® products. Unlike the PODS Relational Pipeline Data Model, the PODS ESRI Spatial Data Model can only be implemented with ESRI geodatabase technology.
All of the features in this model can be organized into one of three categories: 1) Abstract classes, 2) PODS classes, and 3) Optional Classes. The abstract classes define the framework of the model; all other classes in the model inherit properties, relationships and behaviors from one of the abstract classes. The abstract classes are required elements of the model. The core classes are those object, feature and relationship classes, together with associated domains, that are required to maintain PODS ESRI compliance. The core classes define the model centerline features, stationing attributes, and supporting model elements. The optional classes are defined in a separate document (ArcGIS Pipeline Data Model Version 4.0 Optional Classes). The optional classes are direct derivates from tables in the PODS relational model.
The PODS ESRI data model is built and maintained in a UML document which is managed through the CASE Tools extension in Visio Professional 2003. This interface allows the database administrator to manage data model changes in a graphical format. The graphical format is exported to an XML file which can be imported into a new geodatabase.