Version 0.1.1

Please reference the Change Log page for information regarding feature and functionality changes included in each version.

The following resources are prototypes and should not be used to develop PipelineML-compliant applications (as these specifications are undergoing significant changes). These resources are intended for consumption by pipeline industry stakeholders and data interchange standards stakeholders for the purpose of testing and discussion of the standards development.

Application Schema

PipelineML GML SF-0 Application Schema

Sample PipelineML Files

Sample 1 – 1 Component No Attributes – This is the simplest possible version of a PipelineML file. It contains only a single pipeline component with only 1 required attribute (gml:id). This demonstrates the minimum requirements for a PipelineML file. All other pipeline components are optional and may be omitted based on business need. The file header contains inline documentation that provides more detailed explanation of its contents.

Sample 2 – 1 Component 1 Geometry – This is another simple example of PipelineML. This file contains only 1 pipeline component. In addition to the minimal requirements, it contains a component name and 1 geometric attribute. The file header contains inline documentation that provides more detailed explanation of its contents.

Sample 3 – 1 Component 2 Geometries – This is another simple example of PipelineML. This file contains only 1 pipeline component. In addition to the minimal requirements, it contains a component name and 2 geometric attributes. The file header contains inline documentation that provides more detailed explanation of its contents.

Sample 4 – 1 Component All Attributes – This is a more thorough example of PipelineML. This file contains only 1 pipeline component. However, it contains a complete list of all possible attributes pertaining to a LinePipe component. All of these attributes are optional except the mandatory gml:id. Therefore, any of these attributes may be included that are of interest to a particular business need, but none that do not support the needed business use cases. The file header contains inline documentation that provides more detailed explanation of its contents.

Sample 5 – 3 Components No Attributes – This example of a PipelineML file shows 3 components (a linepipe component, a joint, and another linepipe component) that only contain the minimal required attribute (gml:id). This should help communicate the concept of a series of components in a sequence as they are installed in the field. The file header contains inline documentation that provides more detailed explanation of its contents.

Sample 6 – 3 Components 1 Geometry – This example of a PipelineML file shows the same 3 components as Sample 5 except that it adds the name attribute as well as 1 geometry attribute. The file header contains inline documentation that provides more detailed explanation of its contents.

Sample 7 – 3 Components 2 Geometries – This example is similar to Sample 6 except that it contains 2 geometries per component (a 0-dimension point geometry and a 1-dimension linestring geometry). The file header contains inline documentation that provides more detailed explanation of its contents.

Sample 8 – All Components All Attributes – This is a complete sample pipeline that includes weld-level details. It contains thousands of components and each component lists many attributes. This is an example of a typically PipelineML file that may be used in a new construction survey, acquisition, divestiture, etc.

Technical Help Files

Schema Interactive Help Files – This is an HTML interactive document designed to help software developers understand the technical details of the PipelineML Application Schema.