We held a heavily attended meeting this week in Dublin (as most of the current stakeholders are in the U.S.). Several members of the PODS Association were on hand. We had a wide variety of dialogue that involved retracing much of the work undertaken to date as well as philosophical and technical discussions. The following was our meeting agenda:
- Quick walkthrough of Prototype 1 Definition document (to be posted to portal prior to the meeting and as quickly as possible although it is undergoing heavy revision currently—it is not subject to 3 week rule as it will not require a vote, per Scott Simmons)
- Gather feedback on such issues as:
- Prototype methodology, scope and schedule
- Whether to support pipeline component sub-elements for type attribution or role all component type attribution up to the parent component feature element
- How best to leverage FeatureCollections based on the proposed data structure (experience from past initiatives)
- Given the sample instance data structure defined in above document, can we achieve GML-SF level 0 compliance or will we need to resort to level 1 compliance (why and how)
- Should we attempt to support 2 levels of data granularity in this first prototype – (1) detailed feature attribution and (2) simplified geography representation for visualization and if so what are thoughts on the best approach (any lessons learned from other group initiatives)
- Discuss possible participation in Interoperability Program and interest in sponsorship among stakeholders
- Request assistance with:
- Modeling conformance classes in UML
- Vetting of metadata and feature attribution from pipeline industry and survey professionals
The following were the summary points made during the Closing Plenary:
- Reviewed PipelineML Prototype 1 Definition document
- PipelineML SWG is pursuing an early encoding prototype based on GML Application Schema and Simple Features profile SF-0 compliance with a very narrow scope.
- Goal is to get sample data to stakeholders quickly to inform technical decisions regarding supported features, reference code lists, abstract/conceptual model, conformance classes, etc.
- Use Cases
–Detailed Survey Data Package from New Pipeline Construction
–Light-weight Survey Data Visualization of New Pipeline Construction
- Test Cases
–Visualize survey data package using ESRI ArcGIS
–Visualize survey data package using open source GIS tool such as QGIS
–Facilitate programmatic coterminous component count (tally)
- Detailed discussion and feedback will be facilitated via a follow-up meeting in 4 weeks.