Your SlideShare is downloading. ×
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
GIS Data Models Explained
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

GIS Data Models Explained

687

Published on

Published in: Career
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
687
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
40
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Enterprisevs Personal: Accessibility, Security, Size (PGDB 2 GB, SQL Express 4 GB, SQL & Oracle Enterprise limitless)Storage: Indexes (100 files but only 10 used)Structure: Data Model (how data is stored)
  • GIS neutral = Not just Esri but any GIS applicationFlat = non-spatial
  • ISPDM – industry standard pipeline data management systemISAT – integrated spatial analysis techniques
  • Logical – generic blue printPhysical – detailed structure designData dictionary – document that defines the structure
  • Features inherit attributes.
  • StationSeries=5Marker=6
  • Transcript

    • 1. September 2012 GIS Data Models Explained A look at GIS data models and their functions.GULF INTERSTATE ENGINEERING COMPANY16010 BARKERS POINT LANESUITE 600HOUSTON, TEXAS 77079 USA(713) 850-3400
    • 2. 1. Purpose2. Introduction to GIS Data Models3. Hierarchy4. Database Objects5. Exercise6. Tips & Tricks 2
    • 3. • Quick Database Information… – Enterprise versus Personal • Accessibility • Storage • Structure 3
    • 4. • What is the purpose of using data models? – Efficiency – Quality – Standard 4
    • 5. 1. Purpose2. Introduction to GIS Data Models3. Hierarchy4. Database Objects5. Exercise6. Tips & Tricks 5
    • 6. • 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
    • 7. • PODS – Key Notes • GIS software neutral • Relational, hierarchal, GIS data model • Non-spatial / “Flat” • Uses GUIDs 7
    • 8. • PODS – Pipeline Open Data Standard 8
    • 9. • PODS – Support Information • PODS was first developed in 1998. • GIS database expanded ISAT data model. • Maintained by PODS Association. 9
    • 10. • PODS – Pipeline Open Data Standard 10
    • 11. • 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
    • 12. • APDM – ArcGIS Pipeline Data Model The ArcGIS Pipeline Data Model (APDM) Object Tables and Feature Conceptual The ESRI Object Class is the highest object in the conceptual object model. Object Class models a TABLE which contains rows (or features). Each ESRI Class OBJECTID Object row 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) Catalog View Centerline Classes Classes OBJECTID Object ESRI Class A Geodatabase can store both features in featureclasses and events in object classes. A feature is a row 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. CreatedBy CreatedDate Audit EffectiveFromDate EffectiveToDate APDM Abstract Class The APDM Audit Class is an abstract class containing attributes which are inherited by all APDM objects. The Audit class attributes are: CreatedBy: The ID of the user who added the row to the table GeoDatabase Transmission (Featuredataset) AlignmentSheet (Polygon Feature Class) Anomaly (Point Feature Class) AnomalyCluster (MultiPoint Feature Class) Point features are drawn at a specific measure (or distance) along a route. Polyline features start at a GroupEventID (FK) CreatedDate: The date/time stamp when the row was added to the table Appurtenance (Point Feature Class) specified measure along a route and then follow the route to a second specified measure. Both LastModified EffectiveFromDate: The start date the event was placed „In Service‟ polyline and point events are considered „spatially coincident‟ with the route feature. The concept of ModifiedBy EffectiveToDate: The end date the event was „retired‟, „removed‟ or „abandoned‟ Casing (Polyline Feature Class) OriginEventID (FK) stationed position along a station series is directly analogous to the construct of measures and routes. (EventID) (PK) GroupEventID: ForeignKey used to link 2 or more features together as a single feature. Closure (Point Feature Class) Remarks LastModified: The date the row was last modified Coating (Polyline Feature Class) GeoMetaData Feature APDM Core LineLoop OwnerOperatorship SubSystem OperationalStatus Feature is an object class that contains geometry denoting ModifiedBy: The ID of the user who last modified the row in the table ControlPoint (Point Feature Class) the class to be a FeatureClass. Geometry is stored in the OriginEventID: The parent ID of the feature this feature was created from DateCollected Shape EventID (PK) CompanyEventID (FK) EventID (PK) An online feature (or event) is located exactly on the centerline of the pipeline system. A online CPAnode (Point Feature Class) Shape attribute. Points, Polylines and Polygons are the EventID: A globally unique Identifier for every event or feature in the system ESRIProjectionID LineName EventID (PK) SubSystemName feature can be a point feature or a polyline feature. Point features can be placed anywhere along CPBond (Point Feature Class) most common forms of geometry in the APDM Model. Remarks: For general comments, tags, or descriptions. EventID (PK) LineType LineLoopEventID (FK) EffectiveToEventID the length of a station series. Linear features can begin or end at any position along a station series OriginalX Product OperatorPercentage EffectiveFromEventID and all intervening vertices between the begin/end point of the linear feature must be geometrically Event (Object) Feature Each child of the feature object will inherit the Shape Status: Description of the current status of the object CPCable (Polyline Feature Class) OriginalY OperatorType attribute and become a FeatureClass. CPGroundBed (Point Feature Class) OriginalZ coincident with the underlying station series. Geometrically coincident means that online linear Shape CPRectifier (Point Feature Class) PointEventID (FK) PositionSource Point Polyline (MAware) features and the underlying station series share the same vertices. ESRI Class Shape: A BLOB containing a geometry object CPTestStation (Point Feature Class) 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 DocumentPoint (Point Feature Class) Offline features are primary located by XY and NOT by linear referencing or stationed position. These ExternalDocument BeginStationSeriesEventID and „BeginStation‟ attributes. Online polyline features share the same Elbow (Point Feature Class) features typically include landbase data. Company attributes in addition to „BeginStationSeriesEventID‟ and „EndStation‟ attributes. ElevationPoint (Point Feature Class) LineLoopHierarchy Features on Online Offline Features not on FieldNote (Point Feature Class) ControlPoint StationSeries EventID (PK) SubSystemHierarchy BeginStationSeriesEventID: ID of the route that the measured or referenced event occurs on. the Centerline BeginStationSeriesEventID (FK) StationSeries (EventID) the Centerline HCAClass (Polyline Feature Class) ParentLineLoopEventID (FK) BeginStation ControlPointAngle BeginStation EventID (PK) Station: The measure or station value along the route or station series the event occurs at. (the ChildLineLoopEventID (FK) HighConsequenceArea (Polygon Feature Class) ControlPointType EndStation ParentSubsystemEventID (FK) position along the line from the start of the line) EventID (PK) EventID (PK) ChildSubsystemEventID (FK) Offline polyline features may be located on the centerline by one or more „online polyline‟ features InspectionRange (Polyline Feature Class) PIDirection FromSeriesEventID (FK) representing the intersection of the polygon by the centerline. An example of which are property Leak (Point Feature Class) StationValue SeriesOrder Note: Referenced features contain geometry and thus can also be located by the coordinate values parcels that are intersected by the centerline this creating right-of-way „online location‟ polylines. StationSeriesEventID (FK) ToSeriesEventID (FK) contained therein. However, Events to not contain geometry and therefore can only be located via Point Polyline (MAware) Point Polyline Polygon LinearEncroachment (Polyline Feature Class) SymbolRotation LineLoop represents one level of hierarchy or organization of StationSeries measure along a route.. SymbolRotation APDM EndStationSeriesEventID (FK) (EventID) (EventID) (EventID) Another example of the creation of „online location‟ polylines are easements that are created when a LineCrossing (Point Feature Class) features in the APDM. A LineLoop typically represents a mainline or a branch and can be comprised of one or more StationSeries features. (OffsetDistance) (OffsetAngle) Classes EndStation linear feature intersects the centerline and provides a „stationed offset‟ to either side of the Marker (Point Feature Class) Meter (Point Feature Class) An online point feature may contain offset distance and angle attributes. These attributes are used intersection point along the centerline. to locate an offline point feature via an „online location‟. An example is a Structure (offline point) has NonStationedPipe (Polyline Feature Class) Control Point and Station Series Continuous Station Series form the ROUTES which are used to locate all referenced no reference information but has one or more „online point‟ features (locations) that store station Engineering Offline point features may be located on the centerline by one or more „online point‟ locations. A OperatingPressure (Polyline Feature Class) have the same subtypes which are events/features on or along the pipeline system. StationSeries are MAware position and offset information by which the referenced location of the structure can be determined. Horizontal structure within 1000ft of one or more StationSeries would record one „online point‟ feature at the PiggingStructure (Polyline Feature Class) used to differentiate between Mile Post Polyline features. StationSeries have one or more subtypes each representing closest point on each StationSeries feature withint 1000ft of the structure. PipeJoinMethod (Point Feature Class) different forms of stationing (linear Paces a alternate reference measurement (or Stationing) system. Slack Chain PipeSegment (Polyline Feature Class) referencing). Valve APDM Core ControlPoints represent “known points of stationing at a specific XY location” USER DEFINED FEATURECLASSES PressureTest (Polyline Feature Class) Section Unspecified along the pipeline. Two or more ControlPoints represent the vertices of a Reducer (Point Feature Class) StationSeries feature for the same subtype (Measurement System). Each RemovedLine (Polyline Feature Class) ControlPoint will have a single station value representing the measure value at Each implementation of the APDM can take the conceptual classes and derive more specialized feature RemovedPoint (Point Feature Class) the vertex of the StationSeries on which the ControlPoint is located. and object classes that meet the business requirements of the organization. RightOfWay (Polyline Feature Class) Feature Classes (Events) RiskAnalysis (Polyline Feature Class) SiteBoundary (Polygon Feature Class) (Optional) Sleeve (Polyline Feature Class) StationSeries (Polyline Feature Class - MAware) Structure (Point Feature Class) StuctureOutline (Polygon Feature Class) APDM Online Polyline (MAware) APDM Encroachments APDM Class ESRI Class APDM Class ESRI Class ESRI Class Class Facilities Online Point Class Tap (Point Feature Class) Tee (Point Feature Class) Pipe_Topology (ESRI Topology) Valve (Point Feature Class) Online Polyline (M) Polyline Online Point Point Polygon Vessel (Point Feature Class) Activity (Object Class - Table) Coating Sleeve Casing PipeSegment Valve Tap PipeJoinMethod Vessel Appurtenance Fitting APDM ActivityEvent (Object Class - Table) CoatingCondition EventID (PK) CasingLength BendRadius Automated BranchConnectionType EventID (PK) EventID (PK) AppurtenanceType DateManufactured Abstract Address (Object Class - Table) CoatingLength Grade CrossingType DateManufactured EventID (PK) Capacity InServiceDate InServiceDate EventID (PK) Grade CoatingLocation InServiceDate EventID (PK) EventID (PK) InletConnectionType CapacityUnits Insulated Manufacturer InServiceDate InletConnectionType Class Company (Object Class - Table) CoatingMaterial NominalDiameter Filled GirthWeld InletDiameter Capped JoinType SerialNumber InletDiameter CrossingEasement LineCrossing LineCrossingLocation StructureLocation Structure StructureOutline HighConsequenceArea CoatingMill SleeveLength InServiceDate Grade InServiceDate EventID (PK) Manufacturer VesselType InletWallThickness Contact (Object Class - Table) EventID (PK) Clearance EventID (PK) DimensionTie1 DaysOfWeek StructureEventID (FK) AreaType CoatingSource SleeveType InsulatorType InletWallThickness Manufacturer FlowDirection PressureRating InServiceDate ExternalDocument (Object Class - Table) LineCrossingEventID CrossingType LineCrossingEventID DimensionTie2 EventID (PK) EventID (PK) ClassArea EventID (PK) WallThickness OutsideDiameter InServiceDate NormalPosition InServiceDate Manufacturer GeoMetaData (Object Class - Table) EasementWidth EventID (PK) OccupantCount EventID (PK) InServiceDate SealType LongitudinalSeam OperatorType Manufacturer Material EventID (PK) StructureEventID StructureStatus InternalCoating Shorted Manufacturer OutletConnectionType Metered PressureRating LastEvent (Object Class - Table) Weld Name StructureType Vented Material OutletDiameter PressureRating Specification LineLoop (Object Class - Table) Coupling WeeksPerYear WallThickness MillLocation PresentPosition TapSize YearAdded Polyline MillTestPressure PressureRating TapType Flange Screw LineLoopHierarchy (Object Class - Table) OutsideDiameter ValveFunction TappingMethod Electro Stop Geographical OutletWallThickness ValveNumber OwnerOperatorShip (Object Class - Table) Contact Residential Encroachment feature classes model any physical feature or boundary Utility PipeType Reading (Object Class - Table) Business that might impact the operation and/or regulated safety compliance of Tap Fitting Transportation PreTested Civic the pipeline system. PressureRating Angle Valve Tap Fabrication Meter Tee Reducer Elbow Closure SubSystem (Object Class - Table) Company/Operator SegmentLength Ball Valve LineCrossings represent offline linear features that intersect the EventID (PK) BranchConnectionType OutletConnectionType ElbowAngle ClosureType SubSystemHierarchy (Object Class - Table) Specification Block Valve Address centerline. LineCrossings may have one or more online point locations Check Valve MeterFunction BranchDiameter OutletDiameter ElbowRadius EventID (PK) (crossing locations) and one or more online polyline locations Control Valve MeterName BranchWallThickness OutletWallThickness EventID (PK) (easements) PiggingStructure NonStationedPipe Pipe Curb Valve MeterNumber EventID (PK) EventID (PK) ESRI Topology Owner MeterType ScaperBars ReducerSize Bend Gate Valve Pipe_Topology Structures are offline Points that may have zero or more online point BarrelDiameter Diameter Transition Plug Valve RemoteNetworked TeeSize ReducerType locations - structure locations are typically derived for structures within BarrelGrade EventID (PK) SerialNumber TeeType Participating feature classes and ranks 1000 feet (304.8 meters) of the centerline. BarrelWallThickness InServiceDate FeatureClass Rank EventID (PK) PipeType InServiceDate WallThickness APDM Full On Tee StationSeries 1 Manufacturer Core Tapping Tee ControlPoint 1 Material Split Tee Pipe Segment 2 StructureLength Wide Open Tee Launcher Facility feature classes model the physical Online Referenced Line 5 PressureRating Cathodic Receiver appurtenances or devices found on or along a Online Referenced Point 5 pipeline system. ESRI Class APDM Class ESRI Class Sample Topology Rules Point OnlinePoint Polyline FeatureClass FeatureClass FeatureClass ControlPoints Point Must be Covered By Line StationSeries Protection Object StationSeries StationSeries Must Not Overlap Must Be Covered By Feature Class Of Pipe Segment OBJECTID ESRI Class Event Support StationSeries Tap Tee Valve Must Be Single Part Point Must Be Covered By Line Point Must Be Covered By Line Point Must Be Covered By Line Pipe Segment Pipe Segment Pipe Segment CPRectifier CPGroundBed CPAnode CPTestStation CPBond CPCable ESRI Class ESRI Class ESRI Class EventID (PK) AnodeSpacing AnodeMaterial EventID (PK) BondType CableCoating APDM Abstract Point Polyline Polygon InServiceDate BackFillMaterial AnodeType InServiceDate CriticalBond CableSize Audit Manufacturer Model CPRectifierEventID (FK) EventID (PK) AnodeWeight CPGroundBedEventID (FK) TestStationType EventID (PK) InServiceDate CableType ColorCode Attributes … (listed above) Class NumberOfNegatives InServiceDate EventID (PK) EventID (PK) Key NumberOfAnodes LocationDescription InServiceDate InServiceDate Types of Relationships OperatingAmpsOut NumberOfAnodes CPOnlineLocation NumberOfCables OperatingVoltsOut WaterSystem OnlineStationSeriesEventID (FK) PowerSource EventID (PK) OnlineStation ESRI Defined Class* Binary Association - RatedAmpsOut Relationship between exactly two RatedVoltsOut classes RectifierStackType Cathodic Protection feature classes model the devices used to monitor and prevent corrosion from occurring to other facilities on or along the pipeline system. CPRectifier Reading Contact Company Address Activity ExternalDocument DocumentPoint RemovedPoint RemovedLine AlignmentSheet ReplacedByDate CPRectifier, CPGroundBed, CPAnode, CPTestStation, CPBond are all Offline Features that may EventID (PK) CompanyEventID (FK) CompanyLabel City ActivityDate DocumentDescription DPName Attributes Attributes EventID (PK) Whole Part have a single online location. CPTestStation ReadingDate ContactType CompanyName County ActivityDescription DocumentType EventID (PK) EventID (PK) BeginStationSeriesEventID (FK) SheetName Wormhole to CPCable may or may not have a single end connected-to or located-on the centerline. ReadingUnits Email CompanyType Country ActivityName EventID (PK) EventType BeginStation SheetNumber Abstract Class Meter ReadingValue EventID (PK) Fax EventID (PK) EventID (PK) StateProvince ActivityParentEventID (FK) ActivityType FilePath FiletName ProjectionID RemovedDate EndStationSeriesEventID (FK) EndStation SheetType (italicized) Abstract Class *** Composite Aggregation - A whole/part relationship in which the FirstName Street1 EventID (PK) GeoMetaDataEventID (FK) StationSeriesEventID (FK) EventID (PK) existence of the part is dependent PipeSegment Scada Corrosion Control LastName Street2 Station EventType Property1 upon the existence of the whole** Mobile ZipPostalCode ProjectionID Wormhole to Property2 Inspections Close Interval Survey Pager RemovedDate Valve Phone Concrete Class Whole Part (non-italicized) GeoMetaData <classname>Activity Simple Aggregation - ESRI Class <classname>EventID (PK) A whole/part relationship in which the existence of the part is not APDM Online Point MultiPoint Online Polyline (MAware) APDM InspectionRange ActivityEventID (PK) Event Support feature and object classes contain the meta-data, reports, documents, and customer/contact information that pertain to the regulation dependent upon the existence of the Remarks Class Class <class> and operation of the pipeline system. whole ConcreteClass1 ConcreteClass2 Superclass APDM Core or Property1 Property1 Subclass Conceptual Class Property2 Property2 Offline Point APDM Online Polyline (MAware) APDM NOTES: Generalization - DateRepaired DateReported Depth Leak Anomaly AnomalyClusterEventID (FK) BPRCalculated BPRPig AnomalyCluster AnomalyType AveBPRCalculated AveBPRPig InspectionRange EventID (PK) InspectionDate BeginStationSeriesEventID (FK) BeginStation OffsetAngle OffsetDistance Class Class Operations Polygon Last Revised: 10/29/2003 - Version 2.0 APDM Model is maintained by M.J. Harden Associates Inc./ Defined subtypes Notes A superclass/sublass relationship in which the subclass inherits all of the properties of the superclass ESRI on behalf of the ESRI Pipeline Interest Group (PIG) EventID (PK) BPRVariance AveBPRVariance Steering and Technical Committees. LeakCause Depth AveDepth Smart Pig Run Contact ** Composite Aggregation relationships involving linear features will be implemented as Simple Aggregation LeakOrigin EventID (PK) AveLength Cleaning Pig Run Copyright 2002, 2003 Environment Systems Research Institute, relationships. LeakStatus InspectionRangeEventID (FK) AveMaximumDiameter Geometry Pig Run Inc. All Rights Reserved. MethodDetected Length AveMinimumDiameter *** Class Header Boxes colored gray are Events. Events occur along the centerline of a pipeline system. Leak Survey RepairType MaximumDiameter AveOrientation Close Interval Survey EventID  EventID is an arbitrary name assigned to a globally MinimumDiameter AveOvality Visual Survey FieldNote ElevationPoint Marker RiskAnalysis PressureTest OperatingPressure RightOfWay HCAClass SiteBoundary unique identifier. The use of „Event‟ in EventID attribute name Orientation AveRPRCalculated Aerial Survey DOES NOT denote that features identified by this attribute are Ovality AveRPRPig Excavation EventID (PK) EventID (PK) EventID (PK) ConsequenceEconomic EventID (PK) ActualPressure EasementWidth ClassType EventID (PK) FieldNoteType FeatureElevation InServiceDate ConsequenceEnvironmental MinAdjustedPressure AgreedToPressure EventID (PK) ClassSource SiteName „events‟ created via linear referencing. EventID could be RecommendedRemediation AvePRPVariance replaced by FeatureID, GeoElementID, or GeoEntityID. RPRCalculated AveWidth GroundElevation MarkerNumber ConsequenceLife MinDesignPressure CalculatedPressure ParcelNumber ClassLength SiteType RPRPig EventID (PK) MeasurementDate ConsequenceProperty PreTest EventID (PK) ROWType EventID (PK) Cultural WaterElevation EventID (PK) TestDate PressureType TraverseLength The feature classes depicted in this model are „SUGGESTED‟ PRPVariance feature classes. These classes are assumed to be Width Environmental Mile Post POFConstruction TestDuration VerifiedByEventID (FK) Facility Aerial Marker POFInternalCorrosion TestMedium featureclasses and are depicted as such rather than as „events‟ GeoMetaData GeoPolitical Monument POFMaterials TestName or „event tables‟. External Corrosion Hydrology Survey Point POFOutsideForce TestType Pig Signal (AGM) POFThirdParty Contact Address Internal Corrosion Line Crossing Inspection feature classes model the results of Operations TotalConsequence Operational feature classes model terrain, Dent in-line or physical inspection of the pipeline for LineLoop survey, pressure testing, right-of-way, TotalPOF Gouge anomalies, corrosion and other possible Routing Transportation TotalRisk operations and installations information on or Version 2.0 hazards or defects. along the pipeline system. 12
    • 13. • APDM – Support Information • APDM has been published since 2001. • Maintained by APDM Steering and Technical Committees. • Supported by Esri PUG and PIG. 13
    • 14. • APDM – ArcGIS Pipeline Data Model 14
    • 15. • Documentation – Posters – White Papers (Esri) – Data Dictionary The ArcGIS Pipeline Data Model (APDM) Object Tables and Feature Conceptual The ESRI Object Class is the highest object in the conceptual object model. Object Class models a TABLE which contains rows (or features). Each ESRI Class OBJECTID Object row 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) Catalog View Centerline OBJECTID Classes Classes Object ESRI Class A Geodatabase can store both features in featureclasses and events in object classes. A feature is a row 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. CreatedBy CreatedDate Audit EffectiveFromDate EffectiveToDate APDM Abstract Class The APDM Audit Class is an abstract class containing attributes which are inherited by all APDM objects. The Audit class attributes are: CreatedBy: The ID of the user who added the row to the table GeoDatabase Transmission (Featuredataset) AlignmentSheet (Polygon Feature Class) Anomaly (Point Feature Class) AnomalyCluster (MultiPoint Feature Class) Point features are drawn at a specific measure (or distance) along a route. Polyline features start at a GroupEventID (FK) CreatedDate: The date/time stamp when the row was added to the table Appurtenance (Point Feature Class) specified measure along a route and then follow the route to a second specified measure. Both LastModified EffectiveFromDate: The start date the event was placed „In Service‟ polyline and point events are considered „spatially coincident‟ with the route feature. The concept of ModifiedBy EffectiveToDate: The end date the event was „retired‟, „removed‟ or „abandoned‟ Casing (Polyline Feature Class) OriginEventID (FK) stationed position along a station series is directly analogous to the construct of measures and routes. (EventID) (PK) GroupEventID: ForeignKey used to link 2 or more features together as a single feature. Closure (Point Feature Class) Remarks LastModified: The date the row was last modified Coating (Polyline Feature Class) GeoMetaData Feature APDM Core LineLoop OwnerOperatorship SubSystem OperationalStatus Feature is an object class that contains geometry denoting ModifiedBy: The ID of the user who last modified the row in the table ControlPoint (Point Feature Class) the class to be a FeatureClass. Geometry is stored in the OriginEventID: The parent ID of the feature this feature was created from DateCollected Shape EventID (PK) CompanyEventID (FK) EventID (PK) An online feature (or event) is located exactly on the centerline of the pipeline system. A online CPAnode (Point Feature Class) Shape attribute. Points, Polylines and Polygons are the EventID: A globally unique Identifier for every event or feature in the system ESRIProjectionID LineName EventID (PK) SubSystemName feature can be a point feature or a polyline feature. Point features can be placed anywhere along CPBond (Point Feature Class) most common forms of geometry in the APDM Model. Remarks: For general comments, tags, or descriptions. EventID (PK) LineType LineLoopEventID (FK) EffectiveToEventID the length of a station series. Linear features can begin or end at any position along a station series OriginalX Product OperatorPercentage EffectiveFromEventID and all intervening vertices between the begin/end point of the linear feature must be geometrically Event (Object) Feature Each child of the feature object will inherit the Shape Status: Description of the current status of the object CPCable (Polyline Feature Class) OriginalY OperatorType attribute and become a FeatureClass. CPGroundBed (Point Feature Class) OriginalZ coincident with the underlying station series. Geometrically coincident means that online linear Shape CPRectifier (Point Feature Class) PointEventID (FK) PositionSource Point Polyline (MAware) features and the underlying station series share the same vertices. ESRI Class Shape: A BLOB containing a geometry object CPTestStation (Point Feature Class) 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 DocumentPoint (Point Feature Class) Offline features are primary located by XY and NOT by linear referencing or stationed position. These ExternalDocument BeginStationSeriesEventID and „BeginStation‟ attributes. Online polyline features share the same Elbow (Point Feature Class) Company features typically include landbase data. attributes in addition to „BeginStationSeriesEventID‟ and „EndStation‟ attributes. ElevationPoint (Point Feature Class) LineLoopHierarchy Features on Online Offline Features not on FieldNote (Point Feature Class) ControlPoint StationSeries EventID (PK) SubSystemHierarchy BeginStationSeriesEventID: ID of the route that the measured or referenced event occurs on. the Centerline BeginStationSeriesEventID (FK) StationSeries (EventID) the Centerline HCAClass (Polyline Feature Class) ParentLineLoopEventID (FK) BeginStation ControlPointAngle BeginStation EventID (PK) Station: The measure or station value along the route or station series the event occurs at. (the ChildLineLoopEventID (FK) HighConsequenceArea (Polygon Feature Class) ControlPointType EndStation ParentSubsystemEventID (FK) position along the line from the start of the line) EventID (PK) EventID (PK) ChildSubsystemEventID (FK) Offline polyline features may be located on the centerline by one or more „online polyline‟ features InspectionRange (Polyline Feature Class) PIDirection FromSeriesEventID (FK) representing the intersection of the polygon by the centerline. An example of which are property Leak (Point Feature Class) StationValue SeriesOrder Note: Referenced features contain geometry and thus can also be located by the coordinate values parcels that are intersected by the centerline this creating right-of-way „online location‟ polylines. StationSeriesEventID (FK) ToSeriesEventID (FK) contained therein. However, Events to not contain geometry and therefore can only be located via Point Polyline (MAware) Point Polyline Polygon LinearEncroachment (Polyline Feature Class) SymbolRotation LineLoop represents one level of hierarchy or organization of StationSeries measure along a route.. SymbolRotation APDM EndStationSeriesEventID (FK) (EventID) (EventID) (EventID) Another example of the creation of „online location‟ polylines are easements that are created when a LineCrossing (Point Feature Class) features in the APDM. A LineLoop typically represents a mainline or a branch and can be comprised of one or more StationSeries features. (OffsetDistance) (OffsetAngle) Classes EndStation linear feature intersects the centerline and provides a „stationed offset‟ to either side of the Marker (Point Feature Class) Meter (Point Feature Class) An online point feature may contain offset distance and angle attributes. These attributes are used intersection point along the centerline. to locate an offline point feature via an „online location‟. An example is a Structure (offline point) has NonStationedPipe (Polyline Feature Class) Control Point and Station Series Continuous Station Series form the ROUTES which are used to locate all referenced no reference information but has one or more „online point‟ features (locations) that store station Engineering Offline point features may be located on the centerline by one or more „online point‟ locations. A OperatingPressure (Polyline Feature Class) have the same subtypes which are events/features on or along the pipeline system. StationSeries are MAware position and offset information by which the referenced location of the structure can be determined. Horizontal structure within 1000ft of one or more StationSeries would record one „online point‟ feature at the PiggingStructure (Polyline Feature Class) used to differentiate between Mile Post Polyline features. StationSeries have one or more subtypes each representing closest point on each StationSeries feature withint 1000ft of the structure. PipeJoinMethod (Point Feature Class) different forms of stationing (linear Paces a alternate reference measurement (or Stationing) system. Slack Chain PipeSegment (Polyline Feature Class) referencing). Valve APDM Core ControlPoints represent “known points of stationing at a specific XY location” USER DEFINED FEATURECLASSES PressureTest (Polyline Feature Class) Section Unspecified along the pipeline. Two or more ControlPoints represent the vertices of a Reducer (Point Feature Class) StationSeries feature for the same subtype (Measurement System). Each RemovedLine (Polyline Feature Class) ControlPoint will have a single station value representing the measure value at Each implementation of the APDM can take the conceptual classes and derive more specialized feature RemovedPoint (Point Feature Class) the vertex of the StationSeries on which the ControlPoint is located. and object classes that meet the business requirements of the organization. RightOfWay (Polyline Feature Class) Feature Classes (Events) RiskAnalysis (Polyline Feature Class) SiteBoundary (Polygon Feature Class) (Optional) Sleeve (Polyline Feature Class) StationSeries (Polyline Feature Class - MAware) Structure (Point Feature Class) StuctureOutline (Polygon Feature Class) APDM Online Polyline (MAware) APDM Encroachments APDM Class ESRI Class APDM Class ESRI Class ESRI Class Class Facilities Online Point Class Tap (Point Feature Class) Tee (Point Feature Class) Pipe_Topology (ESRI Topology) Valve (Point Feature Class) Online Polyline (M) Polyline Online Point Point Polygon Vessel (Point Feature Class) Activity (Object Class - Table) Coating Sleeve Casing PipeSegment Valve Tap PipeJoinMethod Vessel Appurtenance Fitting APDM ActivityEvent (Object Class - Table) CoatingCondition EventID (PK) CasingLength BendRadius Automated BranchConnectionType EventID (PK) EventID (PK) AppurtenanceType DateManufactured Abstract Address (Object Class - Table) CoatingLength Grade CrossingType DateManufactured EventID (PK) Capacity InServiceDate InServiceDate EventID (PK) Grade CoatingLocation InServiceDate EventID (PK) EventID (PK) InletConnectionType CapacityUnits Insulated Manufacturer InServiceDate InletConnectionType Class Company (Object Class - Table) CoatingMaterial NominalDiameter Filled GirthWeld InletDiameter Capped JoinType SerialNumber InletDiameter CrossingEasement LineCrossing LineCrossingLocation StructureLocation Structure StructureOutline HighConsequenceArea CoatingMill SleeveLength InServiceDate Grade InServiceDate EventID (PK) Manufacturer VesselType InletWallThickness Contact (Object Class - Table) EventID (PK) Clearance EventID (PK) DimensionTie1 DaysOfWeek StructureEventID (FK) AreaType CoatingSource SleeveType InsulatorType InletWallThickness Manufacturer FlowDirection PressureRating InServiceDate ExternalDocument (Object Class - Table) LineCrossingEventID CrossingType LineCrossingEventID DimensionTie2 EventID (PK) EventID (PK) ClassArea EventID (PK) WallThickness OutsideDiameter InServiceDate NormalPosition InServiceDate Manufacturer GeoMetaData (Object Class - Table) EasementWidth EventID (PK) OccupantCount EventID (PK) InServiceDate SealType LongitudinalSeam OperatorType Manufacturer Material EventID (PK) StructureEventID StructureStatus InternalCoating Shorted Manufacturer OutletConnectionType Metered PressureRating LastEvent (Object Class - Table) Weld Name StructureType Vented Material OutletDiameter PressureRating Specification LineLoop (Object Class - Table) Coupling WeeksPerYear WallThickness MillLocation PresentPosition TapSize YearAdded Polyline MillTestPressure PressureRating TapType Flange Screw LineLoopHierarchy (Object Class - Table) OutsideDiameter ValveFunction TappingMethod Electro Stop Geographical OutletWallThickness ValveNumber OwnerOperatorShip (Object Class - Table) Contact Residential Encroachment feature classes model any physical feature or boundary Utility PipeType Reading (Object Class - Table) Business that might impact the operation and/or regulated safety compliance of Tap Fitting Transportation PreTested Civic the pipeline system. PressureRating Angle Valve Tap Fabrication Meter Tee Reducer Elbow Closure SubSystem (Object Class - Table) Company/Operator SegmentLength Ball Valve LineCrossings represent offline linear features that intersect the EventID (PK) BranchConnectionType OutletConnectionType ElbowAngle ClosureType SubSystemHierarchy (Object Class - Table) Specification Block Valve Address centerline. LineCrossings may have one or more online point locations Check Valve MeterFunction BranchDiameter OutletDiameter ElbowRadius EventID (PK) (crossing locations) and one or more online polyline locations Control Valve MeterName BranchWallThickness OutletWallThickness EventID (PK) (easements) PiggingStructure NonStationedPipe Pipe Curb Valve MeterNumber EventID (PK) EventID (PK) ESRI Topology Owner MeterType ScaperBars ReducerSize Bend Gate Valve Pipe_Topology Structures are offline Points that may have zero or more online point BarrelDiameter Diameter Transition Plug Valve RemoteNetworked TeeSize ReducerType locations - structure locations are typically derived for structures within BarrelGrade EventID (PK) SerialNumber TeeType Participating feature classes and ranks 1000 feet (304.8 meters) of the centerline. BarrelWallThickness InServiceDate FeatureClass Rank EventID (PK) PipeType InServiceDate WallThickness APDM Full On Tee StationSeries 1 Manufacturer Core Tapping Tee ControlPoint 1 Material Split Tee Pipe Segment 2 StructureLength Wide Open Tee Launcher Facility feature classes model the physical Online Referenced Line 5 PressureRating Cathodic Receiver appurtenances or devices found on or along a Online Referenced Point 5 pipeline system. ESRI Class APDM Class ESRI Class Sample Topology Rules Point OnlinePoint Polyline FeatureClass FeatureClass FeatureClass ControlPoints Point Must be Covered By Line StationSeries Protection Object StationSeries StationSeries Must Not Overlap Must Be Covered By Feature Class Of Pipe Segment OBJECTID ESRI Class Event Support StationSeries Tap Tee Valve Must Be Single Part Point Must Be Covered By Line Point Must Be Covered By Line Point Must Be Covered By Line Pipe Segment Pipe Segment Pipe Segment CPRectifier CPGroundBed CPAnode CPTestStation CPBond CPCable ESRI Class ESRI Class ESRI Class EventID (PK) AnodeSpacing AnodeMaterial EventID (PK) BondType CableCoating APDM Abstract Point Polyline Polygon InServiceDate BackFillMaterial AnodeType InServiceDate CriticalBond CableSize Audit Manufacturer Model CPRectifierEventID (FK) EventID (PK) AnodeWeight CPGroundBedEventID (FK) TestStationType EventID (PK) InServiceDate CableType ColorCode Attributes … (listed above) Class NumberOfNegatives InServiceDate EventID (PK) EventID (PK) Key NumberOfAnodes LocationDescription InServiceDate InServiceDate Types of Relationships OperatingAmpsOut NumberOfAnodes CPOnlineLocation NumberOfCables OperatingVoltsOut WaterSystem OnlineStationSeriesEventID (FK) PowerSource EventID (PK) OnlineStation ESRI Defined Class* Binary Association - RatedAmpsOut Relationship between exactly two RatedVoltsOut classes RectifierStackType Cathodic Protection feature classes model the devices used to monitor and prevent corrosion from occurring to other facilities on or along the pipeline system. CPRectifier Reading Contact Company Address Activity ExternalDocument DocumentPoint RemovedPoint RemovedLine AlignmentSheet ReplacedByDate CPRectifier, CPGroundBed, CPAnode, CPTestStation, CPBond are all Offline Features that may EventID (PK) CompanyEventID (FK) CompanyLabel City ActivityDate DocumentDescription DPName Attributes Attributes EventID (PK) Whole Part have a single online location. CPTestStation ReadingDate ContactType CompanyName County ActivityDescription DocumentType EventID (PK) EventID (PK) BeginStationSeriesEventID (FK) SheetName Wormhole to CPCable may or may not have a single end connected-to or located-on the centerline. ReadingUnits Email CompanyType Country ActivityName EventID (PK) EventType BeginStation SheetNumber Abstract Class Meter ReadingValue EventID (PK) Fax EventID (PK) EventID (PK) StateProvince ActivityParentEventID (FK) ActivityType FilePath FiletName ProjectionID RemovedDate EndStationSeriesEventID (FK) EndStation SheetType (italicized) Abstract Class *** Composite Aggregation - A whole/part relationship in which the FirstName Street1 EventID (PK) GeoMetaDataEventID (FK) StationSeriesEventID (FK) EventID (PK) existence of the part is dependent PipeSegment Scada Corrosion Control LastName Street2 Station EventType Property1 upon the existence of the whole** Mobile ZipPostalCode ProjectionID Wormhole to Property2 Inspections Close Interval Survey Pager RemovedDate Valve Phone Concrete Class Whole Part (non-italicized) GeoMetaData <classname>Activity Simple Aggregation - ESRI Class <classname>EventID (PK) A whole/part relationship in which the existence of the part is not APDM Online Point MultiPoint Online Polyline (MAware) APDM InspectionRange ActivityEventID (PK) Event Support feature and object classes contain the meta-data, reports, documents, and customer/contact information that pertain to the regulation dependent upon the existence of the Remarks Class Class <class> and operation of the pipeline system. whole ConcreteClass1 ConcreteClass2 Superclass APDM Core or Property1 Property1 Subclass Conceptual Class Property2 Property2 Offline Point APDM Online Polyline (MAware) APDM NOTES: Generalization - DateRepaired DateReported Depth Leak Anomaly AnomalyClusterEventID (FK) BPRCalculated BPRPig AnomalyCluster AnomalyType AveBPRCalculated AveBPRPig InspectionRange EventID (PK) InspectionDate BeginStationSeriesEventID (FK) BeginStation OffsetAngle OffsetDistance Class Class Operations Polygon Last Revised: 10/29/2003 - Version 2.0 APDM Model is maintained by M.J. Harden Associates Inc./ Defined subtypes Notes A superclass/sublass relationship in which the subclass inherits all of the properties of the superclass ESRI on behalf of the ESRI Pipeline Interest Group (PIG) EventID (PK) BPRVariance AveBPRVariance Steering and Technical Committees. LeakCause Depth AveDepth Smart Pig Run Contact ** Composite Aggregation relationships involving linear features will be implemented as Simple Aggregation LeakOrigin EventID (PK) AveLength Cleaning Pig Run Copyright 2002, 2003 Environment Systems Research Institute, relationships. LeakStatus InspectionRangeEventID (FK) AveMaximumDiameter Geometry Pig Run Inc. All Rights Reserved. MethodDetected Length AveMinimumDiameter *** Class Header Boxes colored gray are Events. Events occur along the centerline of a pipeline system. Leak Survey RepairType MaximumDiameter AveOrientation Close Interval Survey EventID  EventID is an arbitrary name assigned to a globally MinimumDiameter AveOvality Visual Survey FieldNote ElevationPoint Marker RiskAnalysis PressureTest OperatingPressure RightOfWay HCAClass SiteBoundary unique identifier. The use of „Event‟ in EventID attribute name Orientation AveRPRCalculated Aerial Survey DOES NOT denote that features identified by this attribute are Ovality AveRPRPig Excavation EventID (PK) EventID (PK) EventID (PK) ConsequenceEconomic EventID (PK) ActualPressure EasementWidth ClassType EventID (PK) FieldNoteType FeatureElevation InServiceDate ConsequenceEnvironmental MinAdjustedPressure AgreedToPressure EventID (PK) ClassSource SiteName „events‟ created via linear referencing. EventID could be RecommendedRemediation AvePRPVariance replaced by FeatureID, GeoElementID, or GeoEntityID. RPRCalculated AveWidth GroundElevation MarkerNumber ConsequenceLife MinDesignPressure CalculatedPressure ParcelNumber ClassLength SiteType RPRPig EventID (PK) MeasurementDate ConsequenceProperty PreTest EventID (PK) ROWType EventID (PK) Cultural WaterElevation EventID (PK) TestDate PressureType TraverseLength The feature classes depicted in this model are „SUGGESTED‟ PRPVariance feature classes. These classes are assumed to be Width Environmental Mile Post POFConstruction TestDuration VerifiedByEventID (FK) Facility Aerial Marker POFInternalCorrosion TestMedium featureclasses and are depicted as such rather than as „events‟ GeoMetaData GeoPolitical Monument POFMaterials TestName or „event tables‟. External Corrosion Hydrology Survey Point POFOutsideForce TestType Pig Signal (AGM) POFThirdParty Contact Address Internal Corrosion Line Crossing Inspection feature classes model the results of Operations TotalConsequence Operational feature classes model terrain, Dent in-line or physical inspection of the pipeline for LineLoop survey, pressure testing, right-of-way, TotalPOF Gouge anomalies, corrosion and other possible Routing Transportation TotalRisk operations and installations information on or Version 2.0 hazards or defects. along the pipeline system. 15
    • 16. Summary…PODS was flat and GIS software neutral but now is spatial. APDM was always spatial and specifically designed for Esri. 16
    • 17. Which model will GIE use? 17
    • 18. • Questions? 18
    • 19. 1. Purpose2. Introduction to GIS Data Models3. Hierarchy4. Database Objects5. Exercise6. Tips & Tricks 19
    • 20. • Hierarchy – APDM & PODS have hierarchy Grandparent Parent Parent Child Child Child Grandchild 20
    • 21. Object• Hierarchy OBJECTID Feature – Classes SHAPE • Abstract → Core → Concrete Class FeatureArchive GlobalID EventID (pk) CreatedBy CreatedDate EffectiveFromDate EffectiveToDate CenterlinePoint HistoricalState <d> CenterlinePolyline LastModified OperationalStatus <d> ModifiedBy RouteEventID (fk) BeginMeasure OriginEventID MeasureValue EndMeasure ProcessFlag StationSeriesEventID (fk) BeginStation Remarks StationValue EndStation Point_X OperationalStatus <d> Point_Y Point_Z CLControl <d> CLStationEditResponse <d> CLXYEditResponse <d> StationSeries CLZEditResponse <d> StationSeriesName SymbolRotation SeriesOrder ParentStationSeriesEventID (fk) LineLoopEventID (fk) ControlPoint FromConnectionStationValue FromStationSeriesEventID (fk) ControlPointAngle ToConnectionStationValue ControlPointType <d> ToStationSeriesEventID (fk) PIDirection <d> RefMode <d> 21
    • 22. • Hierarchy – Levels • Example: StationSeries (Centerline) – How many levels? • Example: Marker (Operations) – How many levels? 22
    • 23. • Questions? 23
    • 24. 1. Purpose2. Introduction to GIS Data Models3. Hierarchy4. Database Objects5. Exercise6. Tips & Tricks 24
    • 25. • Relationships – Primary & Foreign Keys ControlPoint GlobalID StationSeries EventID (pk) CreatedBy GlobalID CreatedDate EventID (pk) EffectiveFromDate CreatedBy EffectiveToDate CreatedDate HistoricalState <d> EffectiveFromDate LastModified EffectiveToDate ModifiedBy HistoricalState <d> OriginEventID LastModified ProcessFlag ModifiedBy Remarks OriginEventID ProcessFlag OperationalStatus <d> Remarks RouteEventID (fk) BeginMeasure MeasureValue EndMeasure StationSeriesEventID (fk) BeginStation StationValue EndStation Point_X OperationalStatus <d> Point_Y Point_Z StationSeriesName CLControl <d> SeriesOrder CLStationEditResponse <d> ParentStationSeriesEventID (fk) CLXYEditResponse <d> LineLoopEventID (fk) CLZEditResponse <d> FromConnectionStationValue SymbolRotation FromStationSeriesEventID (fk) ToConnectionStationValue ControlPointAngle ToStationSeriesEventID (fk) ControlPointType <d> RefMode <d> PIDirection <d> 25
    • 26. • Relationships – Primary & Foreign Keys EventID SeriesName 1 Route A 1 2 EventID StationSeriesEventID 1 1 2 1
    • 27. • Domains & SubTypes LineCrossing GlobalID EventID (pk) CreatedBy CreatedDate EffectiveFromDate EffectiveToDate HistoricalState <d> LastModified ModifiedBy OriginEventID ProcessFlag Remarks Status <d> Clearance CrossingType <d> EasementWidth Name SubtypeCD Geographical Utility Transportation 27
    • 28. • Domains & SubTypes StationSeriesEventID CrossingType SubtypeCD 1 Highway Transportation 1 River Geographic 1 Cable Line Utility
    • 29. • Questions? 29
    • 30. 1. Purpose2. Introduction to GIS Data Models3. Hierarchy4. Database Objects5. Exercise6. Tips & Tricks 30
    • 31. • 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?
    • 32. 1. Purpose2. Introduction to GIS Data Models3. Hierarchy4. Database Objects5. Exercise6. Tips & Tricks 33
    • 33. • Tips & Tricks – Load Objects Wizard 34
    • 34. • 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
    • 35. “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 36

    ×