Click here to load reader

Navigating PODS and APDM - Esri ... PODS • You are editing two distinct databases – the PODS database and the spatial features in in the mapping application. • Changing the location

  • View
    2

  • Download
    0

Embed Size (px)

Text of Navigating PODS and APDM - Esri ... PODS • You are editing two distinct databases – the...

  • Navigating PODS and APDMNavigating PODS and APDM Pipeline Models 101Pipeline Models 101

    John Linehan GISPJohn Linehan GISP GIS Database ConsultantGIS Database Consultant

    Geospatial Integration ServicesGeospatial Integration Services Houston TXHouston TX

  • What is a database model?What is a database model?

    A model defines data storage and structure A model defines data storage and structure as well as defining operations that can be as well as defining operations that can be performed on the data.performed on the data.

    •• Relational models allow operations such as select Relational models allow operations such as select and join using SQL commands to manipulate and and join using SQL commands to manipulate and extract data.extract data.

    •• Spatial models Spatial models alsoalso allow operations based on allow operations based on topology to query and extract data based on topology to query and extract data based on location.location.

  • PODS BackgroundPODS Background

    PODS PODS –– Pipeline Open Database StandardPipeline Open Database Standard

    •• Developed by the Gas Technology Institute Developed by the Gas Technology Institute (GTI) along with several Operators and (GTI) along with several Operators and vendors beginning in 1995.vendors beginning in 1995.

    •• Enhancement of ISAT database.Enhancement of ISAT database. •• Bridges ISAT gaps in GIS integration, Bridges ISAT gaps in GIS integration, normalization, and common pipeline normalization, and common pipeline industry practices.industry practices.

  • PODS BackgroundPODS Background

    •• Standard release is a Relational Model.Standard release is a Relational Model. •• Commonly loaded using SQL.Commonly loaded using SQL. •• Somewhat Proprietary, Owned by PODS.Somewhat Proprietary, Owned by PODS. •• Platform independent, closely Platform independent, closely ““LinkedLinked”” with mapping application.with mapping application.

    ““Complete and Ready out of the boxComplete and Ready out of the box””

  • APDM BackgroundAPDM Background

    APDM APDM –– ArcGIS Pipeline Data ModelArcGIS Pipeline Data Model

    •• Developed on the ESRI ArcGIS platform by Developed on the ESRI ArcGIS platform by several pipeline operators and vendors several pipeline operators and vendors beginning in 2002.beginning in 2002.

    •• Developed as a template, not a complete Developed as a template, not a complete database.database.

    •• Common pipeline practices are optimized Common pipeline practices are optimized by ArcGIS dynamic segmentation and by ArcGIS dynamic segmentation and spatial toolsets.spatial toolsets.

  • APDM BackgroundAPDM Background

    •• Standard release is a Spatial Model.Standard release is a Spatial Model. •• Commonly designed and installed using Commonly designed and installed using Case/UML.Case/UML.

    •• Open Architecture. Open Architecture. •• Spatial platform needed to fully utilize Spatial platform needed to fully utilize model.model.

    ““Some assembly requiredSome assembly required””

  • CORE TablesCORE Tables PODSPODS

    LINELINE ROUTEROUTE SERIESSERIES FEATURE_TABLEFEATURE_TABLE EVENT_RANGEEVENT_RANGE STATION_POINTSTATION_POINT LOCATIONLOCATION COORDINATECOORDINATE

    APDMAPDM LineLoopLineLoop StationSeriesStationSeries ControlPointControlPoint AltRefMeasure (ver 4)AltRefMeasure (ver 4) SubSystemSubSystem SubSystemRangeSubSystemRange ActivityActivity OwnerOperatorOwnerOperator ProductProduct Audit Tables Audit Tables Hierarchy TablesHierarchy Tables APDMClass (Metadata)APDMClass (Metadata) ReferenceMode (Metadata)ReferenceMode (Metadata) OnlineLocationClass (Metadata)OnlineLocationClass (Metadata)

  • The Data Chain in PODSThe Data Chain in PODS

    –– Information is stored in relational database tables.Information is stored in relational database tables. –– These tables are cataloged in the FEATURE_TABLE.These tables are cataloged in the FEATURE_TABLE. –– All elements are related through the EVENT_RANGE table All elements are related through the EVENT_RANGE table

    via the EVENT_ID or EVENT_GUID.via the EVENT_ID or EVENT_GUID. –– This _ID or _GUID is used to link with the spatial element This _ID or _GUID is used to link with the spatial element

    in the mapping application.in the mapping application. –– Elements in the EVENT_RANGE table have Elements in the EVENT_RANGE table have

    STATION_POINT locations.STATION_POINT locations. –– STATION_POINT locations have realSTATION_POINT locations have real--world coordinates in world coordinates in

    the COORDINATE table.the COORDINATE table.

    –– For Centerlines, one or more Event_Ranges define a For Centerlines, one or more Event_Ranges define a SERIES. One or more Series compose a ROUTE and one SERIES. One or more Series compose a ROUTE and one or more Routes compose a LINE.or more Routes compose a LINE.

  • PODS Event_Range – “Heart of the model”

  • The Data Chain in APDMThe Data Chain in APDM

    –– Information is stored in object classes.Information is stored in object classes. –– These classes are Abstract, Object, or ConcreteThese classes are Abstract, Object, or Concrete

    •• Abstract Abstract –– root class which others inherit fromroot class which others inherit from •• Object Object –– NonNon--spatial class spatial class –– Event & ActivityEvent & Activity •• Concrete Concrete –– Spatial features Spatial features –– ESRI Objects (line, point etc)ESRI Objects (line, point etc)

    –– All spatial features are associated with a All spatial features are associated with a StationSeriesStationSeries –– ControlPoint ControlPoint stores the stationed mapping coordinates for a stores the stationed mapping coordinates for a

    StationSeriesStationSeries –– The measured stationing for spatial features (points, lines, etcThe measured stationing for spatial features (points, lines, etc) )

    are stored in the are stored in the AltRefMeasureAltRefMeasure table (Ver 4) table (Ver 4) •• Ver 5 Ver 5 –– Measures are stored in spatial featureMeasures are stored in spatial feature

    –– The StationSeries is the base for Dynamic Segmentation The StationSeries is the base for Dynamic Segmentation placement of features using measure values from placement of features using measure values from AltRefMeasure.AltRefMeasure.

    –– NonNon--spatial support objects are related to spatial objects using spatial support objects are related to spatial objects using the EventID GUID. These relationships are built into the model.the EventID GUID. These relationships are built into the model.

    –– For Centerlines, one or more StationSeries define a For Centerlines, one or more StationSeries define a LineLoopLineLoop. . –– StationSeries may be grouped into StationSeries may be grouped into SystemSystem and and SubSystemSubSystem..

  • APDM Centerline Tables – “Core Elements”

  • PODS Core Elements

  • APDM Core Elements

  • STATIONINGSTATIONING

    •• Stationing is a means to reference distance along a linear Stationing is a means to reference distance along a linear feature from start to end.feature from start to end.

    –– Continuous / Series Stationing references distances along the Continuous / Series Stationing references distances along the centerline centerline ““as the crow fliesas the crow flies””. It is the overall length in 2D. It is the overall length in 2D

    –– Engineering / Measure Stationing references distances along Engineering / Measure Stationing references distances along the centerline the centerline ““as surveyedas surveyed””. It is the overall length in 3D. It is the overall length in 3D

    •• Throughout the history of the pipeline, itThroughout the history of the pipeline, it’’s stationing may s stationing may change due to rechange due to re--routes, extensions, and removal. These routes, extensions, and removal. These changes are handled through the use of changes are handled through the use of ““EquationsEquations””..

    •• Stationing is calibrated to the centerline using known points.Stationing is calibrated to the centerline using known points. –– In PODS, these are managed by the Station_Point/Coordinate In PODS, these are managed by the Station_Point/Coordinate

    tables.tables. –– In APDM, these are managed in the ControlPoint table.In APDM, these are managed in the ControlPoint table.

  • GUID’s and ID’s

    • A GUID is a 16 byte (38 character) hexadecimal string called a Global Unique Identifier.

    • GUID’s are commonly generated by the underlying database software.

    • Example GUID: 38a52be4-9352-453e-af97-5c3b448652f0 • There are a possible 3.4 x 1038 GUID’s. The possibility of two

    being the same is extremely unlikely.

    • ID’s are usually generated sequentially by applications based on prior counts, or they are user assigned.

    • They are integer values • The possibility of two ID’s of the same value is high.

  • Domains

    PODS • Domains are kept in Code Lookup tables.

    – CL – Code Lookup – unique for a specific feature – GCL – General Code Lookup – used by several features – SCL – Sub-Code Lookup – Multi-value con

Search related