DH telecon: November 19th, 2010

posted Nov 17, 2010, 4:52 AM by Hervé Caumont   [ updated Nov 19, 2010, 8:18 AM ]
Telecon summary
- Review of contributions to the AIP-3 DHWG Engineering Report
(QA4EO, GIGAS project, CSIRO, PML, Aston Univ., Munster Univ., Coordination with other AIP-3 WGs and with GEO Tasks)
- First update for the Engineering Report Table of Content (here)


Dan Cornford - Aston University
Jorge Mendes - PML
Hervé Caumont - OGC / ERDAS


Aston University
Dan will continue the discussion on the Aston Univ. Wiki
Include links towards AIP-3 Google site pages (also AIP presentation to CEN Workshop)
Create an executive summary onto the GEOSS Best Practices Wiki
Probably also some links to identified requirements from UncertWeb project (integration requirements related to Data Harmonization)
Keep track also of the ISO metadata discussion.
Components and services : no further thing within the AIP-3 timeframe (so far we have registered : TBC)

2 main use cases contributed through the NetMar project:
  • Use Case 1: Relationships between physical and biological variables
  • Use Case 2: Ecosystem model validation
Goal for the DH WG Engineering report would be to identify Data Harmonization Requirements out of these use cases (to be discussed with Peter)
Hervé to provide template for the part of the report to be addressed

  • The « Integrated Water Information Systems Theme » : near real-time situation awareness of river flow in regional catchments, and how emerging standards for Sensor Web Enablement (SWE) being developed by the Open Geospatial Consortium (OGC) can be applied
  • The South Esk Hydrological Sensor Web and the profiling of SWE information models and web service interfaces, to allow correct encoding and transmission of water information
  • The Data Harmonization requirements from the water resource management use cases in the South Esk Hydrological Sensor Web :
    • DH Requirements from the Kepler Scientific Workflow System to process observations provided by the various SOS instances (time-series harmonization, data spikes issues, gridded rainfall surfaces computation…)
    • DH requirements from usage of points-of-truth for calibration, and potential linkages with uncertainty management
    • DH requirements from forecast models like the DH/DPIPWE/HT flow model, or the CCAM 48 hour rainfall forecasts model
Also, the part related to « register services and components that have implemented these use cases in functioning systems » is well presented in your provided slides & video, and I think I would integrate this in a quite straightforward way :
  • HydroSOS profile supporting WaterML 2.0
  • SOS output of Flow forecast model
  • And maybe a Word on real-time quality assurance, as part of the provenance management framework for Hydrological Sensor Webs (?)