Recommendations .1 Services Profile Contributors Role Introduction

O GC ® Surface wate r Inte rope rability Expe riment Final Re port 12 Copyright © 2012 Op en Geos pati al Consortium 7.6 Recommendations 7.6.1 Services Profile SWIE-compliant SOS-services need to be clear on the interpretation of the terms Offering and Procedure. Currently too much variation exists between services that use these items. This issue is dealt with in detail in use case 3. One of the other issues that arose during the IE was that WaterML2.0 requires GML 3.2, and SOS2.0. At the time of the IE, SOS2.0 was still under development, and the specification was not available for implementation. The IE, therefore, initially used SOS 1.0 for the SWIE. This recommendation is located in 9.3 SWIE SOS hydrology profile. 7.6.2 Issues and Recommendations R2: Any reduction of metadata transmission will be beneficial for incremental high frequency data exchange. R3: Additional research will be needed to e valuate to assess if binary encodings can overcome some of the poor performance problems from WaterML2 in full xml-encoding. O GC ® Surface wate r Inte rope rability Expe riment Final Re port Copyright © 2012 Op en Geos pati al Consortium 13 8 USE CAS E 3 – GLOBAL RUNOFF

8.1 Contributors Role

Contributor SOS Services KISTERS SOS Client KISTERS Data Provider GRDC Data Provider USGS Service Provider USGS Table 2: Contributo rs for Use Case 3.

8.2 Introduction

T he original plan for this use ca se was to provide calc ulated monthly and yearly volum e dischar ge estimates from a few lar ge rivers dischar ging to the oceans. T his was an am bitious plan in which processing tasks were to be include d as part of a workflow that would totalize the dischar ge mea surement for a selected year an d then display a ggre gated value s. Candidate locations for the experiment were to be selected from the Global Runoff Data Center GRDC database. T he plan was a djusted durin g the experiment as a result of t he slower than expected progress due to the difficulties with developing services conc urrently with the WaterML2.0 development. T he original plan for this use case can be seen in Appendix 2.

8.3 Moti vation and Goals