Pipeline GIS Blog

A PODS relational database can be a tricky thing to query especially if you are not familiar with the complicated joins and flags that normally accompany such a complex and rich data model.  In this case, I will show how to construct a query for a PODS 3.2.1 Relational model with history.  I will not cover “inline vs offline” history here since offline is not technically supported by PODS at this time.

At the 2011 GITA GIS for Oil & Gas Pipeline Conference, Eagle will be giving away a new Apple iPad 2. Well, not exactly giving it away; it's a contest to see who can create the coolest pipeline in our ArcGIS Online-driven, gisgap powered pipeline editing application! In order to play, you'll need an ArcGIS Online account. If you already have one, you can skip down to the part where we tell you how to join the Eagle GITA Pipeline Palooza group. If you don't have an ArcGIS Online account, follow these instructions...

"An ounce of prevention is worth a pound of cure." - Benjamin Franklin

In the previous post we introduced the concept of treating data collection and management as a manufacturing process. We touched on the notion that all data is potentially important, and should be treated as such. Finally, we posited that the first requisite of successful data governance is an attitude that focuses on attention to detail. This is all well and good, but face it, a positive attitude and five bucks won't buy you a non-fat, no-whip, double-shot, mocha macchiato. What you need is some concrete help. That's what we'll discuss here.

Not the best way to understand your underground assets...

On January 3, 2011, the National Transportation Safety Board (NTSB) issued a series of urgent pipeline safety recommendations based on preliminary findings from the September 9, 2010, gas transmission pipeline rupture in San Bruno, California, which killed eight people and caused extensive property damage. The NTSB investigation determined that pipeline records were inaccurate, and potentially resulted in an inappropriate Maximum Allowable Operating Pressure (MAOP) for the line in question. The resulting urgent safety recommendations "call on pipeline operators and regulators to ensure that the records, surveys, and documents for all pipeline systems accurately reflect the pipeline infrastructure as built throughout the United States so that maximum safe operating pressures are accurately calculated."

At GITA 2010 GIS for Oil & Gas Conference, Christopher Moravec talked briefly about GIS-enabled Field Data Collection. Field operators can now use inexpensive hand held devices to easily collect field data and have that data go round trip from the field, to the backoffice system and back to the field with all necessary approvals. This not only saves time and money by streamlining the process, it also gets the data back to the people who need it in the field.

In the last post we discussed pros and cons of event- and feature-based implementations of the APDM. Here, in the last post of this series, we concentrate on actually loading features (facilities data, etc.) into the geodatabase.

In the last post we unveiled a free tool to load centerline features (LineLoop, StationSeries and ControlPoint) in a PODS ESRI Spatial 5.0 or APDM 5.0 geodatabase and wrapped up the topic of centerline loading. It's almost time to actually load features (facilities data, etc.) into the geodatabase. But first, a few words on event-based and feature-based APDM implementations...