Top Banner
1 OPEN DATA STANDARD FOR EXCHANGE OF WATER INFORMATION NOAA/National Weather Service John Halquist
14

1 NOAA/National Weather Service John Halquist. 2 Why Standards? Accessibility Versatility Consistency Ensure correct use Remove ambiguity Leverage toolkits.

Dec 24, 2015

Download

Documents

Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: 1 NOAA/National Weather Service John Halquist. 2 Why Standards? Accessibility Versatility Consistency Ensure correct use Remove ambiguity Leverage toolkits.

1

OPEN DATA STANDARD FOR EXCHANGE OF WATER

INFORMATION

NOAA/National Weather Service

John Halquist

Page 2: 1 NOAA/National Weather Service John Halquist. 2 Why Standards? Accessibility Versatility Consistency Ensure correct use Remove ambiguity Leverage toolkits.

2

Why Standards?

• Accessibility• Versatility• Consistency• Ensure correct use• Remove ambiguity• Leverage toolkits

Page 3: 1 NOAA/National Weather Service John Halquist. 2 Why Standards? Accessibility Versatility Consistency Ensure correct use Remove ambiguity Leverage toolkits.

3

GEOSS Work plan

• DA-06-01 GEOSS Data Sharing Principles1. There will be full and open exchange of data, metadata,

and products shared within GEOSS, recognizing relevant international instruments and national policies and legislation;

2. All shared data, metadata, and products will be made available with minimum time delay and at minimum cost;

3. All shared data, metadata, and products being free of charge or no more than cost of reproduction will be encouraged for research and education.

• GEOSS Architecture Implementation Pilot– Proposed for future AIP

Page 4: 1 NOAA/National Weather Service John Halquist. 2 Why Standards? Accessibility Versatility Consistency Ensure correct use Remove ambiguity Leverage toolkits.

4

Hydrology DWG

• Hydrology Domain Working Group (HDWG)• Joint Working Group formed by the Open

Geospatial Consortium (OGC) and the World Meteorological Organization (WMO) Commission for Hydrology (CHy)

• Seeking technical and institutional solutions for describing and exchanging data describing the state and location of water resources.

Page 5: 1 NOAA/National Weather Service John Halquist. 2 Why Standards? Accessibility Versatility Consistency Ensure correct use Remove ambiguity Leverage toolkits.

5

Hydrology DWGhttp://external.opengis.org/twiki_public/HydrologyDWG/WebHome

• Developing WaterML 2.0 Candidate standard• Conducting OGC Interoperability Experiments

(IE) - demonstrate/validate standards and services– Groundwater IE (Completed 2010)– Surface Water IE (Completed 2010-2011)– Hydrologic Forecasting (Underway 2011-2012)– Future

• Groundwater IE Phase 2• Water Quality• Water Supply

Page 6: 1 NOAA/National Weather Service John Halquist. 2 Why Standards? Accessibility Versatility Consistency Ensure correct use Remove ambiguity Leverage toolkits.

6

Hydrologic Forecasting IE• Responsibilities

Description Mile-stone

Sponsor / Implementor(s)

O&M compliant WaterML 2

1CSIRO

WMS 1 USGS

WFS 1 USGS

SOS serving observed data 2

USGS / Deltares/NOAA, KISTERS

SOS serving forecast data

2Deltares/NOAA, KISTERS

Client1

Deltares/NOAA, KISTERS

SWE Notify server/client

3Deltares/NOAA

CSW NOAA

Page 7: 1 NOAA/National Weather Service John Halquist. 2 Why Standards? Accessibility Versatility Consistency Ensure correct use Remove ambiguity Leverage toolkits.

7

WaterML 2.0

• WaterML 2.0 is a candidate Open Geospatial Consortium encoding standard for the representation of in-situ hydrological observations data. WaterML 2.0 is implemented as an application schema of the Geography Markup Language version 3.2.1 and makes use of the OGC Observations and Measurements (O&M) standard and the OMXML GML Application Schema.

Page 8: 1 NOAA/National Weather Service John Halquist. 2 Why Standards? Accessibility Versatility Consistency Ensure correct use Remove ambiguity Leverage toolkits.

8

WaterML 2.0, continued

• OGC WaterML 2.0 will support encoding of hydrological and hydrogeological observation data in a variety of exchange scenarios.

• Example areas of usage are: exchange of data for operational monitoring and forecasting programs; supporting operation of infrastructure (e.g. dams, supply systems); exchange of observational and forecast data for surface water and groundwater; release of data for public dissemination; enhancing disaster management through data exchange; and exchange in support of national reporting.

Page 9: 1 NOAA/National Weather Service John Halquist. 2 Why Standards? Accessibility Versatility Consistency Ensure correct use Remove ambiguity Leverage toolkits.

9

WaterML 2.0 Examples

Page 10: 1 NOAA/National Weather Service John Halquist. 2 Why Standards? Accessibility Versatility Consistency Ensure correct use Remove ambiguity Leverage toolkits.

10

Use Cases

Page 11: 1 NOAA/National Weather Service John Halquist. 2 Why Standards? Accessibility Versatility Consistency Ensure correct use Remove ambiguity Leverage toolkits.

11

Use Cases

• Sensor Observation Service (SOS)– GetObservation– GetCapabilities– DescribeSensor

• Web Feature Service (WFS)– GetCapabilities– DescribeFeatureType– GetFeature

• Web Mapping Service (WMS)

Page 12: 1 NOAA/National Weather Service John Halquist. 2 Why Standards? Accessibility Versatility Consistency Ensure correct use Remove ambiguity Leverage toolkits.

12

Use Cases – Hydro Fcst IE

• Observation and Forecast data exchange

• Forecasts with projected infrastructure operation

• Infrastructure operation• Cross border data

exchange (International)• Notification services

Page 13: 1 NOAA/National Weather Service John Halquist. 2 Why Standards? Accessibility Versatility Consistency Ensure correct use Remove ambiguity Leverage toolkits.

13

What can you do?

• Review candidate standard and provide comments and/or questions

• Adopt WaterML 2.0 standard for use • Participate in future improvements and

modifications to the standard

• Watch OGC Website for status– www.opengeospatial.org/standards– www.ogcnetwork.net/standardtracker

Page 14: 1 NOAA/National Weather Service John Halquist. 2 Why Standards? Accessibility Versatility Consistency Ensure correct use Remove ambiguity Leverage toolkits.

14

Questions?