gis data models explained

GULF INTERSTATE ENGINEERING COMPANY16010 BARKERS POINT LANESUITE 600HOUSTON, TEXAS 77079 USA(713) 850-3400

September 2012

GIS Data Models Explained

A look at GIS data models and their functions.

1. Purpose2. Introduction to GIS Data Models3. Hierarchy4. Database Objects5. Exercise6. Tips & Tricks

2

• Quick Database Information…– Enterprise versus Personal

• Accessibility• Storage• Structure

3

• What is the purpose of using data models?– Efficiency– Quality– Standard

4


5

• What is a data model?– A data model defines structured data for

storage in Database Management Systems (DBMS).

• Are there pipeline related data models?

6

• PODS– Key Notes

• GIS software neutral• Relational, hierarchal, GIS data model• Non-spatial / “Flat”• Uses GUIDs

7

• PODS– Pipeline Open Data Standard

8

• PODS– Support Information

• PODS was first developed in 1998.• GIS database expanded ISAT data model.• Maintained by PODS Association.

9

• PODS– Pipeline Open Data Standard

10

• APDM– Key Notes

• Expressly designed for Esri GIS software• Relational, hierarchal, GIS data model

– However, it uses Esri database types to differentiate “domains” from relationships.

• Spatially enabled• No GUIDs

11

The ArcGIS Pipeline Data Model (APDM)ConceptualClasses

AreaTypeClassAreaEventID (PK)

HighConsequenceAreaStructureEventID (FK)EventID (PK)

StructureOutline

GeographicalUtilityTransportation

Contact

DaysOfWeekEventID (PK)OccupantCountStructureStatusStructureTypeWeeksPerYearYearAdded

Structure

ResidentialBusinessCivic

Address

Owner

Company/Operator

AnomalyClusterEventID (FK)BPRCalculatedBPRPigBPRVarianceDepthEventID (PK)InspectionRangeEventID (FK)LengthMaximumDiameterMinimumDiameterOrientationOvalityRecommendedRemediationRPRCalculatedRPRPigPRPVarianceWidth

Anomaly

External CorrosionInternal CorrosionDentGouge

AnomalyTypeAveBPRCalculatedAveBPRPigAveBPRVarianceAveDepthAveLengthAveMaximumDiameterAveMinimumDiameterAveOrientationAveOvalityAveRPRCalculatedAveRPRPigAvePRPVarianceAveWidthEventID (PK)

AnomalyClusterEventID (PK)InspectionDate

InspectionRange

Smart Pig RunCleaning Pig RunGeometry Pig RunLeak SurveyClose Interval SurveyVisual SurveyAerial SurveyExcavation

Contact

DateRepairedDateReportedDepthEventID (PK)LeakCauseLeakOriginLeakStatusMethodDetectedRepairType

Leak

EventID (PK)ReadingDateReadingUnitsReadingValue

Reading

ScadaCorrosion ControlClose Interval Survey

CPRectifier

CPTestStation

PipeSegment

Meter

Valve

CompanyEventID (FK)ContactTypeEmailEventID (PK)FaxFirstNameLastNameMobilePagerPhone

ContactCompanyLabelCompanyNameCompanyTypeEventID (PK)

CompanyCityCountyCountryEventID (PK)StateProvinceStreet1Street2ZipPostalCode

AddressActivityDateActivityDescriptionActivityNameActivityParentEventID (FK)ActivityTypeEventID (PK)

Activity

<classname>EventID (PK)ActivityEventID (PK)Remarks

<classname>Activity

DocumentDescriptionDocumentTypeEventID (PK)FilePathFiletNameGeoMetaDataEventID (FK)

ExternalDocumentDPNameEventID (PK)

DocumentPointEventID (PK)SheetNameSheetNumberSheetType

AlignmentSheetAttributesBeginStationSeriesEventID (FK)BeginStationEndStationSeriesEventID (FK)EndStationEventID (PK)EventTypeProjectionIDRemovedDate

RemovedLineAttributesEventID (PK)EventTypeProjectionIDRemovedDateStationSeriesEventID (FK)Station

RemovedPoint

OBJ ECTID

Object

DateCollectedESRIProjectionIDEventID (PK)OriginalXOriginalYOriginalZPointEventID (FK)PositionSource

GeoMetaData

ExternalDocument

ControlPointAngleControlPointTypeEventID (PK)PIDirectionStationValueStationSeriesEventID (FK)SymbolRotation

ControlPoint

ContinuousEngineeringHorizontalMile PostPacesSlack ChainValveSectionUnspecified

Shape

Feature

BeginStationEndStationEventID (PK)FromSeriesEventID (FK)SeriesOrderToSeriesEventID (FK)

StationSeries

EventID (PK)LineNameLineTypeProduct

LineLoopCompanyEventID (FK)EventID (PK)LineLoopEventID (FK)OperatorPercentageOperatorType

OwnerOperatorshipEventID (PK)SubSystemNameEffectiveToEventIDEffectiveFromEventID

SubSystem

EventID (PK)ParentSubsystemEventID (FK)ChildSubsystemEventID (FK)

SubSystemHierarchyEventID (PK)ParentLineLoopEventID (FK)ChildLineLoopEventID (FK)

LineLoopHierarchyCompany

ESRI Class

APDM Core

Point Polyline (MAware)

APDM Core

CreatedByCreatedDateEffectiveFromDateEffectiveToDateGroupEventID (FK)LastModifiedModifiedByOriginEventID (FK)(EventID) (PK)RemarksOperationalStatus

Audit

OBJ ECTID

Object

Shape

Feature

APDMAbstractClass

ESRI Class

ESRI Class

BeginStationSeriesEventID (FK)BeginStation

OnlineStationSeries

APDMClasses

(EventID)

Point(EventID)

Polyline(EventID)

Polygon

USER DEFINED FEATURECLASSES

Object Tables and FeatureClasses

EventID (PK)InServiceDateManufacturerModelNumberOfNegativesNumberOfAnodesOperatingAmpsOutOperatingVoltsOutPowerSourceRatedAmpsOutRatedVoltsOutRectifierStackTypeReplacedByDate

CPRectifierAnodeSpacingBackFillMaterialCPRectifierEventID (FK)EventID (PK)InServiceDateLocationDescriptionNumberOfAnodesWaterSystem

CPGroundBedAnodeMaterialAnodeTypeAnodeWeightCPGroundBedEventID (FK)EventID (PK)InServiceDate

CPAnodeBondTypeCriticalBondEventID (PK)InServiceDate

CPBondEventID (PK)InServiceDateTestStationType

CPTestStationCableCoatingCableSizeCableTypeColorCodeEventID (PK)InServiceDateNumberOfCablesOnlineStationSeriesEventID (FK)OnlineStation

CPCable

PointCathodicProtection

Polyline

PolygonAPDM Class

Encroachments

Online PointAPDMClass

MultiPoint APDMClass

Inspections

Event Support

Online Polyline (MAware)

OBJ ECTID

Object ESRI Class

Attributes … (listed above)

Audit APDM AbstractClass

<class>

Point Polyline Polygon

The ESRI Object Class is the highest object in the conceptual object model. Object Class models a TABLE which contains rows (or features). Eachrow in an object class has a unique identifier called ObjectID which is created and maintained within ArcSDE.

OBJECTID: System applied table-level unique identifier (Long Integer)

Offline polyline features may be located on the centerline by one or more ‘online polyline’ featuresrepresenting the intersection of the polygon by the centerline. An example of which are propertyparcels that are intersected by the centerline this creating right-of-way ‘online location’ polylines.

Another example of the creation of ‘online location’ polylines are easements that are created when alinear feature intersects the centerline and provides a ‘stationed offset’ to either side of theintersection point along the centerline.

Offline point features may be located on the centerline by one or more ‘online point’ locations. Astructure within 1000ft of one or more StationSeries would record one ‘online point’ feature at theclosest point on each StationSeries feature withint 1000ft of the structure.

The APDM Audit Class is an abstract class containing attributes which are inherited by all APDMobjects. The Audit class attributes are:

CreatedBy: The ID of the user who added the row to the tableCreatedDate: The date/time stamp when the row was added to the tableEffectiveFromDate: The start date the event was placed ‘In Service’EffectiveToDate: The end date the event was ‘retired’, ‘removed’ or ‘abandoned’GroupEventID: ForeignKey used to link 2 or more features together as a single feature.LastModified: The date the row was last modifiedModifiedBy: The ID of the user who last modified the row in the tableOriginEventID: The parent ID of the feature this feature was created fromEventID: A globally unique Identifier for every 'event' or 'feature' in the systemRemarks: For general comments, tags, or descriptions.Status: Description of the current status of the object

Feature is an object class that contains geometry denotingthe class to be a FeatureClass. Geometry is stored in theShape attribute. Points, Polylines and Polygons are themost common forms of geometry in the APDM Model.Each child of the feature object will inherit the Shapeattribute and become a FeatureClass.

Shape: A BLOB containing a geometry object

Offline features are primary located by XY and NOT by linear referencing or stationed position. Thesefeatures typically include landbase data.

A Geodatabase can store both features in featureclasses and events in object classes. A feature is arow containing actual geometry. An event is a row with virtual geometry either point or polyline. The

APDM allows storage of geographic events as features and events.

Point features are drawn at a specific measure (or distance) along a route. Polyline features start at aspecified measure along a route and then follow the route to a second specified measure. Both

polyline and point events are considered ‘spatially coincident’ with the route feature. The concept ofstationed position along a station series is directly analogous to the construct of measures and routes.

An online feature (or event) is located exactly on the centerline of the pipeline system. A onlinefeature can be a point feature or a polyline feature. Point features can be placed anywhere along

the length of a station series. Linear features can begin or end at any position along a station seriesand all intervening vertices between the begin/end point of the linear feature must be geometrically

coincident with the underlying station series. Geometrically coincident means that online linearfeatures and the underlying station series share the same vertices.

To become an ‘online’ feature - the feature is located by BOTH XY location and M or ‘Stationed’position along a station series or route. Online point features are located by

'BeginStationSeriesEventID' and ‘BeginStation’ attributes. Online polyline features share the sameattributes in addition to ‘BeginStationSeriesEventID’ and ‘EndStation’ attributes.

BeginStationSeriesEventID: ID of the route that the measured or referenced event occurs on.Station: The measure or station value along the route or station series the event occurs at. (theposition along the line from the start of the line)

Note: Referenced features contain geometry and thus can also be located by the coordinate valuescontained therein. However, Events to not contain geometry and therefore can only be located viameasure along a route..

An online point feature may contain offset distance and angle attributes. These attributes are usedto locate an offline point feature via an ‘online location’. An example is a Structure (offline point) has

no reference information but has one or more ‘online point’ features (locations) that store stationposition and offset information by which the referenced location of the structure can be determined.

SubSystem (Object Class - Table)

OwnerOperatorShip (Object Class - Table)

Activity (Object Class - Table)

ActivityEvent (Object Class - Table)

Address (Object Class - Table)

Company (Object Class - Table)

Contact (Object Class - Table)

LastEvent (Object Class - Table)

ExternalDocument (Object Class - Table)

GeoMetaData (Object Class - Table)

LineLoop (Object Class - Table)

Reading (Object Class - Table)

LineLoopHierarchy (Object Class - Table)

SubSystemHierarchy (Object Class - Table)

GeoDatabaseTransmission (Featuredataset)

CPCable (Polyline Feature Class)

CPAnode (Point Feature Class)

CPBond (Point Feature Class)

CPGroundBed (Point Feature Class)

CPRectifier (Point Feature Class)

CPTestStation (Point Feature Class)

StationSeries (Polyline Feature Class - MAware)

ControlPoint (Point Feature Class)

LinearEncroachment (Polyline Feature Class)

LineCrossing (Point Feature Class)

Structure (Point Feature Class)

HighConsequenceArea (Polygon Feature Class)

StuctureOutline (Polygon Feature Class)

PipeSegment (Polyline Feature Class)

Casing (Polyline Feature Class)

Vessel (Point Feature Class)

Appurtenance (Point Feature Class)

Closure (Point Feature Class)

Coating (Polyline Feature Class)

Elbow (Point Feature Class)

Meter (Point Feature Class)

NonStationedPipe (Polyline Feature Class)

PiggingStructure (Polyline Feature Class)

PipeJoinMethod (Point Feature Class)

Reducer (Point Feature Class)

Sleeve (Polyline Feature Class)

Tap (Point Feature Class)

Tee (Point Feature Class)

Valve (Point Feature Class)

InspectionRange (Polyline Feature Class)

Leak (Point Feature Class)

Anomaly (Point Feature Class)

AnomalyCluster (MultiPoint Feature Class)

OperatingPressure (Polyline Feature Class)

SiteBoundary (Polygon Feature Class)

ElevationPoint (Point Feature Class)

FieldNote (Point Feature Class)

HCAClass (Polyline Feature Class)

Marker (Point Feature Class)

PressureTest (Polyline Feature Class)

RightOfWay (Polyline Feature Class)

RiskAnalysis (Polyline Feature Class)

DocumentPoint (Point Feature Class)

AlignmentSheet (Polygon Feature Class)

RemovedLine (Polyline Feature Class)

RemovedPoint (Point Feature Class)

Pipe_Topology (ESRI Topology)

Catalog View

ESRI TopologyPipe_Topology

FeatureClass RankStationSeries 1ControlPoint 1Pipe Segment 2

Online Referenced Line 5Online Referenced Point 5

Participating feature classes and ranks

Sample Topology RulesFeatureClass

Point Must be Covered By LineMust Not Overlap

Must Be Covered By Feature Class OfMust Be Single Part

Point Must Be Covered By LinePoint Must Be Covered By LinePoint Must Be Covered By Line

FeatureClassStationSeries

Pipe Segment

Pipe SegmentPipe SegmentPipe Segment

FeatureClassControlPointsStationSeriesStationSeriesStationSeries

TapTee

Valve

Event (Object)

Station Series form the ROUTES which are used to locate all referencedevents/features on or along the pipeline system. StationSeries are MAwarePolyline features. StationSeries have one or more subtypes each representinga alternate reference measurement (or Stationing) system.

ControlPoints represent “known points of stationing at a specific XY location”along the pipeline. Two or more ControlPoints represent the vertices of aStationSeries feature for the same subtype (Measurement System). EachControlPoint will have a single station value representing the measure value atthe vertex of the StationSeries on which the ControlPoint is located.

LineLoop represents one level of hierarchy or organization of StationSeriesfeatures in the APDM. A LineLoop typically represents a mainline or a branchand can be comprised of one or more StationSeries features.

CoatingConditionCoatingLengthCoatingLocationCoatingMaterialCoatingMillCoatingSourceEventID (PK)InServiceDateInternalCoating

CoatingEventID (PK)GradeInServiceDateNominalDiameterSleeveLengthSleeveTypeWallThickness

SleeveCasingLengthCrossingTypeEventID (PK)FilledInServiceDateInsulatorTypeOutsideDiameterSealTypeShortedVentedWallThickness

CasingAppurtenanceTypeEventID (PK)InServiceDate

AppurtenanceEventID (PK)InServiceDateManufacturerSerialNumberVesselType

Vessel

DiameterEventID (PK)InServiceDatePipeTypeWallThickness

NonStationedPipeBarrelDiameterBarrelGradeBarrelWallThicknessEventID (PK)InServiceDateManufacturerMaterialStructureLengthPressureRating

PiggingStructure

LauncherReceiver

BendRadiusDateManufacturedEventID (PK)GirthWeldGradeInletWallThicknessInServiceDateLongitudinalSeamManufacturerMaterialMillLocationMillTestPressureOutsideDiameterOutletWallThicknessPipeTypePreTestedPressureRatingSegmentLengthSpecification

PipeSegment

PipeBendTransition

DateManufacturedGradeInletConnectionTypeInletDiameterInletWallThicknessInServiceDateManufacturerMaterialPressureRatingSpecification

Fitting

EventID (PK)MeterFunctionMeterNameMeterNumberMeterTypeRemoteNetworkedSerialNumber

MeterElbowAngleElbowRadiusEventID (PK)

ElbowBranchConnectionTypeBranchDiameterBranchWallThicknessEventID (PK)ScaperBarsTeeSizeTeeType

Tee

Full On TeeTapping TeeSplit TeeWide Open Tee

OutletConnectionTypeOutletDiameterOutletWallThicknessEventID (PK)ReducerSizeReducerType

ReducerClosureTypeEventID (PK)

Closure

AutomatedEventID (PK)InletConnectionTypeInletDiameterInServiceDateManufacturerNormalPositionOperatorTypeOutletConnectionTypeOutletDiameterPresentPositionPressureRatingValveFunctionValveNumber

Valve

Angle ValveBall ValveBlock ValveCheck ValveControl ValveCurb ValveGate ValvePlug Valve

EventID (PK)InServiceDateInsulatedJoinTypeManufacturerPressureRating

PipeJoinMethod

WeldCouplingFlangeScrewElectro Stop

BranchConnectionTypeCapacityCapacityUnitsCappedEventID (PK)FlowDirectionInServiceDateManufacturerMeteredPressureRatingTapSizeTapTypeTappingMethod

Tap

Tap FittingTap Fabrication

Facilities Online PointOnline Polyline (MAware) APDMClass

APDMClass

APDMAbstractClass

APDMCore

Polyline

EventID (PK)FieldNoteType

FieldNote

CulturalEnvironmentalFacilityGeoPoliticalHydrologyLine CrossingOperationsRoutingTransportation

GeoMetaData

EventID (PK)FeatureElevationGroundElevationMeasurementDateWaterElevation

ElevationPointEventID (PK)InServiceDateMarkerNumber

Marker

Mile PostAerial MarkerMonumentSurvey PointPig Signal (AGM)

EventID (PK)SiteNameSiteType

SiteBoundaryClassTypeClassSourceClassLengthEventID (PK)

HCAClassEventID (PK)MinAdjustedPressureMinDesignPressurePreTestTestDateTestDurationTestMediumTestNameTestType

PressureTestConsequenceEconomicConsequenceEnvironmentalConsequenceLifeConsequencePropertyEventID (PK)POFConstructionPOFInternalCorrosionPOFMaterialsPOFOutsideForcePOFThirdPartyTotalConsequenceTotalPOFTotalRisk

RiskAnalysisActualPressureAgreedToPressureCalculatedPressureEventID (PK)PressureTypeVerifiedByEventID (FK)

OperatingPressure

Contact

EasementWidthEventID (PK)ParcelNumberROWTypeTraverseLength

RightOfWay

Address

LineLoop

OperationsOffline Point APDMClass

Online Polyline (MAware) APDMClass Polygon

Facility feature classes model the physicalappurtenances or devices found on or along a

pipeline system.

Cathodic Protection feature classes model the devices used to monitor and prevent corrosionfrom occurring to other facilities on or along the pipeline system.

CPRectifier, CPGroundBed, CPAnode, CPTestStation, CPBond are all Offline Features that mayhave a single online location.

CPCable may or may not have a single end connected-to or located-on the centerline.

Encroachment feature classes model any physical feature or boundarythat might impact the operation and/or regulated safety compliance of

the pipeline system.

LineCrossings represent offline linear features that intersect thecenterline. LineCrossings may have one or more online point locations

(crossing locations) and one or more online polyline locations(easements)

Structures are offline Points that may have zero or more online pointlocations - structure locations are typically derived for structures within

1000 feet (304.8 meters) of the centerline.

Inspection feature classes model the results ofin-line or physical inspection of the pipeline for

anomalies, corrosion and other possiblehazards or defects.

Event Support feature and object classes contain the meta-data, reports,documents, and customer/contact information that pertain to the regulation

and operation of the pipeline system.

Operational feature classes model terrain,survey, pressure testing, right-of-way,

operations and installations information on oralong the pipeline system.

Control Point and Station Serieshave the same subtypes which areused to differentiate betweendifferent forms of stationing (linearreferencing).

SymbolRotation(OffsetDistance)(OffsetAngle)

PointEndStationSeriesEventID (FK)EndStation

Polyline (MAware)

(EventID)

OfflineFeatures onthe Centerline

Features not onthe Centerline

ESRI Class

Centerline

APDM Class

Polyline

ClearanceCrossingTypeEasementWidthEventID (PK)Name

LineCrossing

Online Point

EventID (PK)LineCrossingEventID

LineCrossingLocationDimensionTie1DimensionTie2EventID (PK)StructureEventID

StructureLocation

PointESRI ClassESRI Class ESRI Class

ESRI ClassInspectionRange

BeginStationSeriesEventID (FK)BeginStationOffsetAngleOffsetDistance

Each implementation of the APDM can take the conceptual classes and derive more specialized featureand object classes that meet the business requirements of the organization.

OnlinePointESRI Class

APDM ClassOnline Polyline (M)


CrossingEasement

ESRI Class ESRI Class ESRI Class

ESRI Defined Class*

Abstract Class * **

Defined subtypes

Wormhole toAbstract Class

(italicized)

Key

Property1Property2

ConcreteClass1 ConcreteClass2

Property1Property2

Wormhole toConcrete Class

(non-italicized)

Notes

Property1Property2

Types of Relationships

Binary Association -Relationship between exactly two

classes

Composite Aggregation -A whole/part relationship in which the

existence of the part is dependentupon the existence of the whole**

Simple Aggregation -A whole/part relationship in which

the existence of the part is notdependent upon the existence of the

whole

Generalization -A superclass/sublass relationship

in which the subclass inherits all ofthe properties of the superclass

Superclass

Subclass

PartWhole

Whole Part

** Composite Aggregation relationships involving linear features will be implemented as Simple Aggregationrelationships.*** Class Header Boxes colored gray are 'Events'. Events 'occur' along the centerline of a pipeline system.

APDM Core orConceptual Class

NOTES:Last Revised: 10/29/2003 - Version 2.0

APDM Model is maintained by M.J. Harden Associates Inc./ESRI on behalf of the ESRI Pipeline Interest Group (PIG)Steering and Technical Committees.

Copyright 2002, 2003 Environment Systems Research Institute,Inc. All Rights Reserved.

EventID EventID is an arbitrary name assigned to a globallyunique identifier. The use of ‘Event’ in EventID attribute nameDOES NOT denote that features identified by this attribute are‘events’ created via linear referencing. EventID could bereplaced by FeatureID, GeoElementID, or GeoEntityID.

The feature classes depicted in this model are ‘SUGGESTED’feature classes. These classes are assumed to befeatureclasses and are depicted as such rather than as ‘events’or ‘event tables’.

Version 2.0

Feature Classes (Events) (Optional)

EventID (PK)

CPOnlineLocation

GeoMetaData

• APDM– ArcGIS Pipeline Data Model

12

• APDM– Support Information

• APDM has been published since 2001.• Maintained by APDM Steering and Technical

Committees.• Supported by Esri PUG and PIG.

13

• APDM– ArcGIS Pipeline Data Model

14

• Documentation– Posters– White Papers (Esri)– Data Dictionary

15

The ArcGIS Pipeline Data Model (APDM)ConceptualClasses

AreaTypeClassAreaEventID (PK)

HighConsequenceAreaStructureEventID (FK)EventI D (PK)

StructureOutline

Geo gr aph icalUtilityTr an spo rtat ion

Con tact

DaysOfWeekEventI D (PK)OccupantCountStructureStatusStructureTypeWeeksPerYearYearAdded

Structure

Resid ent ia lBu sine ssCiv ic

Addr ess

Owne r

Com pa ny/O pe rato r

AnomalyClusterEventID (F K)BPRCalcula tedBPRP igBPRVarianceDepthEventID (PK)InspectionRangeEventI D (FK)LengthMaxi mumDiameterMinimumDiameterOrientationOvalityRecommendedRemediationRPRCalculatedRPRP igPRPVarianceWidth

Anomaly

Ex tern al Corr osio nInte rn al Co rro sionDentGou ge

AnomalyTypeAveBPRCalcula tedAveBPRP igAveBPRVarianceAveDepthAveLengthAveMaximumDiameterAveMinimumDiameterAveOrientationAveOvalityAveRPRCalcula tedAveRPRP igAvePRPVarianceAveWi dthEventI D (PK)

AnomalyClusterEventI D (PK)Inspecti onDate

InspectionRange

Sm ar t Pig RunCle an ing Pig Ru nGeo me try Pig RunLea k Sur veyClo se Int erva l Sur veyVisu al Su rve yAe rial Sur ve yEx cava tion

Cont act

DateRepairedDateReportedDepthEventID (PK)Leak CauseLeak Origi nLeak StatusMethodDetectedRepairType

Leak

EventID (PK)ReadingDateReadingUnitsReadingValue

Reading

Sc adaCorr osio n C ontr olClose Int erv al Sur vey

CPRectif ie r

CPTe stSta tion

Pip eSe gme nt

M ete r

Valve

CompanyEventI D (F K)ContactTypeEmailEventID (PK)FaxFirstNameLastNameMobilePagerPhone

ContactCompanyLabelCompanyNameCompanyTypeEventI D (PK)

CompanyCityCountyCountryEventI D (PK)StateProvinceStreet1Street2ZipPosta lCode

AddressActivityD ateActivityD escriptionActivityNameActivityParentEventI D (FK)ActivityTypeEventID (PK)

Activity

<classname>EventI D (PK)ActivityEventI D (PK)Remarks

<classname>Activity

DocumentDescriptionDocumentTypeEventID (PK)FilePathFiletNameGeoMetaDataEventI D (FK)

ExternalDocumentDPNameEventID (PK)

DocumentPointEventID (PK)SheetNameSheetNumberSheetType

AlignmentSheetAttributesBeginStationSeriesEventID (F K)BeginStationEndStationSeriesEventID (FK)EndStationEventID (PK)EventTypeProjectionIDRemovedDate

RemovedLineAttributesEventI D (PK)EventTypeProjectionI DRemovedDateStationSeriesEventID (F K)Station

RemovedPoint

OBJ ECTI D

Object

DateCo llectedESRI ProjectionI DEventI D (PK)Orig inalXOrig inalYOrig inalZPointEventID (FK)Posit ionSource

GeoMetaData

Exter na lDocu me nt

Contro lPointAngleContro lPointTypeEventID (PK)PI DirectionStationValueStationSeriesEventI D (FK)SymbolRotation

ControlPoint

Cont in uo usEn gin eer ingHorizo nta lMile Po stPa cesSla ck Ch ainVa lveSe ctionUnspe cifie d

Shape

Feature

Beg inStationEndStationEventI D (PK)FromSeri esEventI D (FK)SeriesOrderToSeriesEventID (FK)

StationSeries

EventID (PK)LineNameLineTypeProduct

LineLoopCompanyEventI D (F K)EventI D (PK)LineL oopEventI D (FK)OperatorPercentageOperatorType

OwnerOperatorshipEventI D (PK)SubSystemNameEffectiveToEventI DEffectiveFromEventI D

SubSystem

EventI D (PK)ParentSubsystemEventI D (F K)ChildSubsystemEventI D (F K)

SubSystemHierarchyEventID (PK)ParentLineLoopEventID (FK)ChildLineLoopEventID (F K)

LineLoopHierarchyCom pa ny

ESRI Class

APDM Core

Point Polyline (MAware)

APDM Core

CreatedByCreatedDateEffectiveFromDateEffectiveToDateGroupEventI D (FK)LastModifiedModifiedByOrig inEventID (F K)(EventI D) (PK)RemarksOperationa lStatus

Audit

OBJ ECT ID

Object

Shape

Feature

APDMAbstractClass

ESRI Class

ESRI Class

Beg inStationSeriesEventI D (FK)Beg inStation

OnlineStatio nSe ries

APDMClasses

(EventI D)

Point(EventI D)

Polyline(EventID)

Polygon

USER DEFINED FEATURECLASSES

Object Tables and FeatureClasses

EventID (PK)I nServiceDateManufacturerModelNumberOfNegati vesNumberOfAnodesOperatingAmpsOutOperatingVol tsOutPowerSourceRatedAmpsOutRatedVo ltsOutRectifierStack TypeReplacedByDate

CPRectifierAnodeSpacingBackFillMaterialCPRectifierEventID (F K)EventI D (PK)InServiceDateLocationDescriptionNumberOfAnodesWaterSystem

CPGroundBedAnodeMateria lAnodeTypeAnodeWeightCPG roundBedEventI D (FK)EventI D (PK)InServiceDate

CPAnodeBondTypeCritica lBondEventID (PK)InServiceDate

CPBondEventID (PK)I nServiceDateTestStationType

CPTestStationCableCoatingCableSizeCableTypeCo lorCodeEventID (PK)InServiceDateNumberOfCabl esOnlineStationSeriesEventI D (F K)OnlineStation

CPCable

PointCathodicProtection

Polyline

PolygonAPDM Class

Encroachments

Online PointAPDMClass

MultiPoint APDMClass

Inspections

Event Support

Online Polyline (MAware)

OBJ ECT ID

Object ESRI Class

Attributes … (listed above)

Audit APDM AbstractClass

<clas s>

Point Polyline Polygon

The ESRI Object Class is the highest object in the conceptual object model . Object Class models a TABLE which contains rows (or features). Eachrow in an object class has a unique identifier ca lled ObjectID which is created and maintained within ArcSDE.

OBJECTID: System appl ied table-level unique identifier (Long Integer)

Offline polyl ine features may be located on the centerline by one or more ‘online polyline’ featuresrepresenting the intersection of the polygon by the centerline. An example of which are propertyparcels that are intersected by the centerl ine th is creating right-of-way ‘onl ine location ’ polylines.

Another example of the creation of ‘onl ine location ’ po lylines are easements that are created when alinear feature intersects the centerline and provides a ‘stationed offset’ to ei ther side of theintersection point a long the centerl ine.

Offline point features may be located on the centerline by one or more ‘online point’ locations. Astructure with in 1000ft of one or more StationSeries would record one ‘online point’ feature at theclosest point on each StationSeries feature within t 1000ft o f the structure.

The APDM Audi t Class is an abstract class contain ing attributes which are inherited by al l APDMobjects. The Audit class attributes are:

CreatedBy : The ID of the user who added the row to the tableCreatedDate: The date/time stamp when the row was added to the tableEffectiveFromDate: The start date the event was placed ‘In Service ’EffectiveToDate: The end date the event was ‘retired’ , ‘removed’ or ‘abandoned’GroupEventID: ForeignKey used to l ink 2 or more features together as a sing le feature.LastModified: The date the row was last modifiedModifiedBy: The ID of the user who last modified the row in the tab leOriginEventID: The parent ID of the feature this feature was created fromEventID: A globally unique Identi fier for every 'event' or 'feature ' in the systemRemarks: For general comments, tags, or descriptions.Status: Des crip tion of the current status of the object

Feature is an object class that contains geometry denotingthe class to be a FeatureClass. Geometry is stored in theShape attribute. Points, Polylines and Polygons are themost common forms of geometry in the APDM Model .Each ch ild of the feature object wi ll inherit the Shapeattribute and become a FeatureClass.

Shape: A BLOB conta ining a geometry object

Offline features are primary located by XY and NOT by linear re ferencing or stationed position. Thesefeatures typ ically include landbase data.

A Geodatabase can store both features in featureclasses and events in object classes. A feature is arow containing actual geometry. An event is a row with virtua l geometry either point or polyline. The

APDM al lows storage of geographic events as features and events.

Point features are drawn at a specific measure (or distance) along a route. Polyline features start at aspecified measure along a route and then fol low the route to a second specified measure. Both

polyl ine and point events are considered ‘spatia lly co incident’ wi th the route feature. The concept o fstationed position along a station series is di rectly analogous to the construct of measures and routes.

An online feature (or event) is located exactly on the centerline of the pipel ine system. A onl inefeature can be a point feature or a polyl ine feature. Point features can be p laced anywhere along

the length of a sta tion series. Linear features can begin or end at any position a long a station seriesand al l interv ening vertices between the begin/end point of the linear feature must be geometrically

coincident wi th the underlying station series. Geometrically coincident means that onl ine linearfeatures and the underlying station series share the same vertices.

To become an ‘on line’ feature - the feature is located by BOTH XY location and M or ‘Stationed’position along a station series or route. Online point features are located by

'BeginStationSeriesEventID' and ‘BeginStation’ attributes. Online polyline features share the sameattributes in addition to ‘BeginStationSeriesEventID’ and ‘EndStation’ attributes.

BeginStationSeriesEventID: ID of the route that the measured or referenced event occurs on.Station: The measure or station value along the route or station series the ev ent occurs at. (theposition along the l ine from the start of the line)

Note: Referenc ed features conta in geometry and thus can also be located by the coordinate valuescontained therein. However, Events to not contain geometry and therefore can only be located viameasure along a route..

An online point feature may contain offset d istance and angle attributes. These attributes are usedto locate an offline point feature via an ‘online location’. An example is a Structure (o ffline point) has

no reference information but has one or more ‘online point’ features (locations) that store stationposition and offset information by which the referenced location of the structure can be determined.

SubSy stem (O bje ct Clas s - Ta ble)

Own er Oper at orSh ip ( Obje ct Cla ss - T able)

Ac tivity ( Obje ct Cl ass - T able )

Ac tivityEven t ( Obj ect Cla ss - T able )

Ad dr ess (Ob je ct Class - T able )

Com pan y (O bje ct Cla ss - Ta ble)

Cont act ( Ob ject C lass - T ab le )

La stEven t ( Obje ct Clas s - Ta ble)

Exter na lDocu me nt ( Obje ct Cla ss - T able )

Geo Me taDa ta (Ob ject Class - T ab le)

Line Lo op (Ob ject Class - T ab le )

Rea ding (O bje ct Clas s - Ta ble)

Line Lo opHi era rch y (O bjec t Clas s - Ta ble)

SubSy stem Hier ar chy ( Ob je ct C la ss - Ta ble )

GeoDatabaseTr an smiss io n ( F eat ure dat ase t)

CPCab le ( Po lyline Fe atu re Class)

CPAnod e ( Point Fe atu re Class)

CPBond (Po int F ea tur e C la ss)

CPGr oun dBed (Poi nt F ea tur e Cla ss)

CPRect ifier (Poin t F ea ture Cla ss)

CPTe stStat ion (Poin t F ea ture Cla ss)

Statio nSer ies ( Polylin e F ea ture Cla ss - MAwa re)

Con tro lPo int (Poin t F ea ture Cla ss)

Line ar Encro ac hm ent (Poly lin e F ea tur e Cla ss)

Line Cr ossing ( Po int F ea tur e C la ss)

Stru ctur e ( Point F eatu re Class )

High Cons equ en ceAre a ( Polyg on Fe atu re C lass)

Stuct ure Ou tline (Polyg on Fe atu re Class)

Pip eSe gm ent (Po ly lin e Fea tur e C la ss)

Casin g ( Polyline F eat ure Class )

Vesse l (Poi nt F ea tur e Cla ss)

Appu rt ena nce (Poin t F eat ure Cla ss)

Closu re (Poin t F eat ur e Cla ss)

Coa ting (Poly li ne Fea tu re Cl ass)

Elb ow (Poin t F eat ure Clas s)

Me ter (Po int F ea tur e Cla ss)

Non Statio ned Pipe ( Polylin e F ea tur e Cla ss)

Pig gin gStr uctu re (Poly lin e Fea tur e C la ss)

Pip eJ oinM eth od (Poin t F ea ture Cla ss)

Red uce r ( Point Fe atu re Class)

Sle ev e ( Po lyline Fe atu re Class)

Ta p ( Point Fe atu re Class)

Te e ( Point Fe atu re Class)

Valve (Poin t F ea tur e Cla ss)

Insp ec tionRa ng e ( Po lyline F eat ure Class )

Le ak ( Point Fe atu re Class)

Anom aly (Poin t F eat ur e Clas s)

Anom alyC lu ste r ( Mu ltiPoin t Fe atu re Class)

Ope ra ting Pres sur e (Po lyline Fe atu re Class)

Sit eBo und ary (Po ly gon Fe at ure Clas s)

Ele va tionPo int ( Point Fe atu re Clas s)

Fie ldNo te ( Point Fe atu re Class)

HCAClass (Po ly lin e F ea tur e C la ss)

Ma rke r ( Point Fe atu re Class)

Pre ssur eT est ( Polylin e F ea ture Cla ss)

Righ tOfWa y ( Po lyline Fe at ure Class )

RiskAna lysis ( Polyline F ea ture Cla ss)

Docu me ntPo int ( Point Fe atu re Class )

Ali gnm en tShee t ( Po lygo n F ea tur e Class)

Rem ove dLi ne (Polyline F eat ur e Cla ss)

Rem ove dPoin t ( Point F e atur e Class)

Pip e_ To pol ogy (ESRI T op olog y)

Catalog View

ESRI TopologyPipe_Topo logy

FeatureClass RankStationSeries 1ControlPo int 1

Pipe Segment 2Online Referenced Line 5Online Referenced Po int 5

Participating feature classes and ranks

Sample Topol ogy RulesFeatureClass

Po int Must be Covered By LineMust Not Overlap

Must Be Covered By F eature Class OfMust Be Sing le Part

Po int Must Be Covered By LinePo int Must Be Covered By LinePo int Must Be Covered By Line

FeatureC lassStationSeries

Pipe Segment

Pipe SegmentPipe SegmentPipe Segment

FeatureClassContro lPointsStationSeriesStationSeriesStationSeries

TapTee

Valve

Event (Object)

Station Series form the ROUTES which are used to locate a ll referencedevents/features on or along the pipeline s ystem. StationSeries are MAwarePolyline features. StationSeries have one or more subtypes each representinga alternate reference measurement (or Stationing) system.

ControlPoints represent “known points of sta tion ing at a specific XY location”along the pipeline. Two or more ControlPoints represent the vertices of aStationSeries feature for the same subtype (Measurement System). Eac hControlPoint will have a single station value representing the measure value atthe vertex of the StationSeries on which the ControlPoint is located.

LineLoop represents one level of h ierarchy or organization of StationSeriesfeatures in the APDM. A LineLoop typ ically represents a main line or a branchand can be comprised of one or more StationSeries features.

Coati ngConditionCoati ngLengthCoati ngLocationCoati ngMaterialCoati ngMillCoati ngSourceEventID (PK)I nServiceDateI nternalCoating

CoatingEventID (PK)GradeI nServiceDateNominalDiameterSleeveLengthSleeveTypeWallThickness

SleeveCasingLengthCrossingTypeEventI D (PK)FilledInServiceDateInsulatorTypeOutsideDiameterSeal TypeShortedVentedWallThickness

CasingAppurtenanceTypeEventI D (PK)InServiceDate

AppurtenanceEventI D (PK)InServiceDateManufacturerSerialNumberVesse lType

Vessel

DiameterEventID (PK)I nServiceDatePipeTypeWallThickness

NonStationedPipeBarrelDiameterBarrelGradeBarrelWallThicknessEventID (PK)I nServiceDateManufacturerMaterialStructureLengthPressureRating

PiggingStructure

La unch erRece iver

BendRadi usDateManufacturedEventI D (PK)Gi rthWeldGradeInletWal lThicknessInServiceDateLong itudina lSeamManufacturerMateri alMillLocationMillTestPressureOutsideDiameterOutl etWallThicknessPipeTypePreTestedPressureRatingSegmentL engthSpecification

PipeSegment

Pip eBendTr an sition

DateManufacturedGradeI nletConnectionTypeI nletDiameterI nletWallThi cknessI nServiceDateManufacturerMaterialPressureRatingSpecification

Fitting

EventI D (PK)MeterF unctionMeterNameMeterNumberMeterTypeRemoteNetworkedSerialNumber

MeterElbowAngleElbowRadiusEventID (PK)

ElbowBranchConnectionTypeBranchDiameterBranchWallThicknessEventI D (PK)ScaperBarsTeeSizeTeeType

Tee

Fu ll On Te eTa pp in g T e eSplit T eeWide Ope n T ee

OutletConnectionTypeOutletDiameterOutletWal lThick nessEventID (PK)ReducerSizeReducerType

ReducerClosureTypeEventI D (PK)

Closure

AutomatedEventI D (PK)InletConnectionTypeInletDiameterInServiceDateManufacturerNormalPositionOperatorTypeOutletConnectionTypeOutletDiameterPresentPosit ionPressureRatingValveFunctionValveNumber

Valve

Angle ValveBall ValveBlo ck Va lveChe ck Valv eCon tro l ValveCur b Va lv eGat e Va lv ePlu g Valve

EventID (PK)InServiceDateInsulatedJo inTypeManufacturerPressureRating

PipeJoinMethod

We ldCou plingF lang eScr ewElect ro St op

BranchConnectionTypeCapacityCapacityUnitsCappedEventID (PK)FlowDirectionI nServiceDateManufacturerMeteredPressureRatingTapSizeTapTypeTappingMethod

Tap

Ta p F itti ngTa p F a brica tion

Facilities Online PointOnline Polyline (MAware) APDMClass

APDMClass

APDMAbstractClass

APDMCore

Polyline

EventI D (PK)FieldNoteType

FieldNote

Cultu ralEn vir onm en talFa cilityGeo PoliticalHydr olog yLine Cro ssingOpe rat ion sRou tingTr ans por tati on

Geo Me taDa ta

EventI D (PK)FeatureElevati onGroundElevationMeasurementDateWaterElevation

ElevationPointEventID (PK)I nServiceDateMarkerNumber

Marker

M ile PostAer ial M ark erM onu me ntSur vey Po intPig Sign al ( AGM )

EventID (PK)SiteNameSiteType

SiteBoundaryClassTypeClassSourceClassL engthEventID (PK)

HCAClassEventID (PK)MinAdj ustedPressureMinDesignPressurePreTestTestDateTestDurationTestMediumTestNameTestType

PressureTestConsequenceEconomicConsequenceEnvironmentalConsequenceLifeConsequencePropertyEventID (PK)POFConstructionPOFI nternalCorrosionPOFMateria lsPOFO utsideForcePOFThirdPartyTotalConsequenceTotalPOFTotalRisk

RiskAnalysisActualPressureAgreedToPressureCalculatedPressureEventI D (PK)PressureTypeVerifiedByEventI D (FK)

OperatingPressure

Con tact

EasementWidthEventID (PK)ParcelNumberRO WTypeTraverseL ength

RightOfWay

Add res s

Lin eLo op

OperationsOffline Point APDMClass

Online Polyline (MAware) APDMClass Polygon

Fa cility f eat ure clas ses m od el th e p hysi calap pur ten an ces o r d evic es fo un d on or a lo ng a

pipe line syste m.

Cath od ic Pro tectio n f eat ure clas ses mod el th e d evic es u sed to mo nitor an d p re vent cor ro sionfro m occu rr ing to o the r f acilities on or alo ng the pipe line syste m.

CPR ectif ie r, CPGro und Bed , CPAno de, CPTe stSta tion, CPBond a re a ll Of flin e Fea tur es tha t m ayhave a sing le o nline loca tion.

CPCab le m ay or ma y no t h ave a sin gle end con ne cted -t o or loca ted -o n th e c ent erlin e.

Encro ac hm ent fea tur e cla sses mo del any phy sical fe atu re or bo un dar ytha t m ig ht imp act the op era tion an d/or re gu late d sa fet y com p lia nce of

th e p ip eline syst em .

Lin eCr ossin gs r ep re sent offl in e lin ear fe atu re s tha t in ters ect thecen ter line . L in eCr oss in gs ma y ha ve o ne or mo re onl in e p oin t loca tion s

(cr ossi ng lo cat io ns) an d o ne or mo re onlin e p olylin e loc ation s(e ase me nts)

Stru ctu res ar e o ffline Point s th at m ay have ze ro or mo re onlin e p ointloca tions - s tru ctur e lo cati ons a re typ ically der ived for str uct ure s with in

10 00 fee t (3 04 .8 met ers ) o f th e ce nter line .

In spec tion fea tur e cla sse s mo del the re sults ofin- line or phy sical in spe ction of the pipe line for

an om alies, cor ro sion an d ot her p ossibleha zard s o r d efec ts.

Even t Sup por t fe at ure and o bject clas ses co nta in the me ta- dat a, r epo rts ,docu me nt s, an d c usto me r/co nta ct in for ma tion tha t p erta in t o th e r eg ulati on

and op er ation of the pip eline syste m.

Ope rat ion al fe atur e classe s m ode l te rra in,sur vey, pr essu re t est in g, r igh t-o f-wa y,

op era tio ns an d i nsta llatio ns in form at ion on oralon g th e pipe line s ystem .

Contro l Point and Station Serieshave the same subtypes which areused to differentiate betweendifferent forms of stationing (l inearreferencing).

SymbolRotation(OffsetDi stance)(OffsetAngle)

PointEndStationSeriesEventI D (FK)EndStation

Polyline (MAware)

(EventI D)

OfflineFeatures onthe Centerline

Features not onthe Centerline

ESRI Class

Centerline

APDM Class

Polyline

ClearanceCrossingTypeEasementWidthEventID (PK)Name

LineCrossing

Online Point

EventID (PK)LineCrossingEventI D

LineCrossingLocationDimensionTie1DimensionTie2EventID (PK)StructureEventI D

StructureLocation

PointESRI ClassESRI Class ESRI Class

ESRI ClassIn spec tionR ang e

Beg inStationSeriesEventI D (FK)Beg inStationOffsetAngl eOffsetDistance

Each implementation of the APDM can take the conceptual classes and deriv e more special ized featureand object classes that meet the business requi rements of the organization.

OnlinePointESRI Class

APDM ClassOnline Polyline (M)


CrossingEasement

ESRI Class ESRI Class ESRI Class

ESRI Defined Class*

Abstract Class * **

Defin ed s ub type s

Wormhole toAbstract Class

(it alicize d)

Key

Property1Property2

ConcreteClass1 ConcreteClass2

Property1Property2

Wormhole toConcrete Class

(n on- italic iz ed)

Note s

Property1Property2

Types of Relationships

Bin ar y Asso ciatio n -Rela tion ship bet ween e xactly two

classe s

Com po site Ag gr eg ation -A who le /p art re la tio nship in w hich the

exist enc e o f th e p art is de pe nde ntupo n t he e xiste nce of the who le**

Simp le Agg re gat io n -A who le /p art re la tio nshi p in w hich

th e exi sten ce o f th e p ar t is n otde pe nde nt u po n th e e xiste nce of t he

who le

Gen era lizati on -A sup er class /subl ass rela tions hip

in wh ich t he sub class i nhe rits a ll ofth e pr op ert ies o f th e s upe rclas s

Supe rcla ss

Su bcla ss

Par tWhol e

Who le Par t

** Composite Aggregation relationships involving linear features will be implemented as Simple Aggregationrelationships.*** Class Header Boxes co lored gray are 'Events'. Events 'occur' a long the centerl ine of a pipeline system.

APDM Co re orCon ce ptu al Cla ssNOTES:

La st Rev ise d: 10 /29 /20 03 - Ve rs ion 2. 0

APD M M od el is ma in tain ed by M .J. Har den Asso ciate s In c./ESR I on be hal f of the ESRI Pipe line I nte re st Gr oup ( PIG )Stee ring an d T ech nica l Com m it tees .

Cop yrigh t 2 002 , 2 003 Envir onm e nt Sys tem s Res ea rch Insti tute ,Inc. All Righ ts Re ser ved .

Even tID Even tID is an ar bitr ar y na me assig ne d t o a glob allyun iq ue ide ntifie r. T he us e o f ‘Even t’ in Ev ent ID at trib ute na meDOES NO T d en ote tha t fe atu re s ide ntifie d b y this att ribu te a re‘eve nts’ cre ate d via line ar r efe re ncin g. Eve ntID cou ld berep lace d b y F ea ture ID, Geo Ele m ent ID, o r G eoEn tityID.

Th e f eat ure clas ses d ep icted in t his m od el a re ‘ SU GGEST ED ’fea tur e cla sses . T hes e cla sses ar e as sum ed to b efea tur ecla sses and ar e dep ic ted as s uch ra the r th an as ‘ even ts’or ‘even t t able s’.

Version 2.0

Feature Classes (Events) (Optional)

EventI D (PK)

CPOnlineLocation

Geo Me taDa ta

Summary…PODS was flat and GIS software

neutral but now is spatial.APDM was always spatial and specifically designed for Esri.

16

Which model will GIE use?

17

• Questions?

18


19

• Hierarchy– APDM & PODS have hierarchy

20

Grandparent

Parent

Child

Parent

Child Child

Grandchild

• Hierarchy– Classes

• Abstract → Core → Concrete Class

21

ObjectOBJECTID

FeatureArchiveGlobalID

EventID (pk)CreatedBy

CreatedDateEffectiveFromDate

EffectiveToDateHistoricalState <d>

LastModifiedModifiedBy

OriginEventIDProcessFlag

Remarks

FeatureSHAPE

ControlPointControlPointAngle

ControlPointType <d>PIDirection <d>

StationSeriesStationSeriesName

SeriesOrderParentStationSeriesEventID (fk)

LineLoopEventID (fk)FromConnectionStationValue

FromStationSeriesEventID (fk)ToConnectionStationValue

ToStationSeriesEventID (fk)RefMode <d>

CenterlinePolylineBeginMeasureEndMeasureBeginStationEndStation

OperationalStatus <d>

CenterlinePointOperationalStatus <d>

RouteEventID (fk)MeasureValue

StationSeriesEventID (fk)StationValue

Point_XPoint_YPoint_Z

CLControl <d>CLStationEditResponse <d>

CLXYEditResponse <d>CLZEditResponse <d>

SymbolRotation

• Hierarchy– Levels

• Example: StationSeries (Centerline)– How many levels?

• Example: Marker (Operations)– How many levels?

22

• Questions?

23


24

• Relationships– Primary & Foreign Keys

25

StationSeries

StationSeriesNameSeriesOrder

ParentStationSeriesEventID (fk)LineLoopEventID (fk)

FromConnectionStationValueFromStationSeriesEventID (fk)

ToConnectionStationValueToStationSeriesEventID (fk)

RefMode <d>

GlobalIDEventID (pk)

CreatedByCreatedDate

EffectiveFromDateEffectiveToDate

HistoricalState <d>LastModifiedModifiedBy


Remarks

BeginMeasureEndMeasureBeginStationEndStation

OperationalStatus <d>

ControlPoint

ControlPointAngleControlPointType <d>

PIDirection <d>

OperationalStatus <d>RouteEventID (fk)

MeasureValueStationSeriesEventID (fk)

StationValuePoint_XPoint_YPoint_Z

CLControl <d>CLStationEditResponse <d>

CLXYEditResponse <d>CLZEditResponse <d>

SymbolRotation

GlobalIDEventID (pk)CreatedBy





Remarks

Rou

te A

• Relationships– Primary & Foreign Keys

1

2

EventID SeriesName

1 Route A

EventID StationSeriesEventID

1 1

2 1

• Domains & SubTypes

27

LineCrossing

ClearanceCrossingType <d>

EasementWidthName

SubtypeCD

GlobalIDEventID (pk)CreatedBy





Remarks

Status <d>

GeographicalUtility

Transportation

• Domains & SubTypesR

oute

A

StationSeriesEventID CrossingType SubtypeCD

1 Transportation

1 Geographic

1 Utility

StationSeriesEventID CrossingType SubtypeCD

1 Highway Transportation

1 River Geographic

1 Cable Line Utility

• Questions?

29


30

• Gather in groups and answer the following…

1. Briefly discuss and explain the difference between PODS & APDM.

2. In APDM, under Facilities; how many class levels make up the Tee feature class?

3. In PODS, under Pipeline Facilities; how many relationships can the Valve feature class have?

4. In APDM, under Facilities; how many subtypes does the PipeJoinMethod feature class have?


33

• Tips & Tricks– Load Objects Wizard

34

http://webhelp.esri.com/arcgisdesktop/9.3/tutorials/editor/editor_ex6_1.htm

• Resources• http://support.esri.com/en/downloads/datamodel/• http://www.apdm.net/• http://www.pods.org/• http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/A_quick_tour

_of_attribute_domains/001s00000001000000/• http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/A_quick_tour

_of_subtypes/005r00000001000000/• http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Relationships

_and_ArcGIS/004t00000001000000/• http://webhelp.esri.com/arcgisdesktop/9.3/tutorials/editor/editor_ex6_1.htm

35

http://support.esri.com/en/downloads/datamodel/

http://www.apdm.net/

http://www.pods.org/

http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html






http://webhelp.esri.com/arcgisdesktop/9.3/tutorials/editor/editor_ex6_1.htm

36

“Knowing where things are, and why, is essential to rational decision making”

Jack Dangermond

“There is no such thing as information overload, only bad design.”

Edward Tufte

gis data models explained

Career