Keynote for HIC 2014 – 11th International Conference on Hydroinformatics, New York, USA August 17 – 21, 2014
Time, Change and Habits in Geospatial-Temporal Information Standards
Time and change are fundamental to our scientific understanding of the world. Standards for geospatial-temporal information exist but new needs outstrip current standards. Geospatial-temporal information includes capturing change in features and coverages and modeling the processes that inform change. Key standards for time, calendars, and temporal reference systems are in place. Time series modeling from the WaterML standard is a recent advance of high value to hydrology. The OGC Moving Features standard will establish an encoding format for changes in “rigid” features. Interoperability standards are needed for Coverages with values that change based on observations, analytical expressions, or simulations. Applying a coverage model to time-varying, fluid Earth systems was the topic of the ground breaking GALEON Interoperability Experiment. Standards developments for spatial-temporal process models is progressing with WPS, OpenMI and ESMF - supporting a Model Web concept. A robust framework for sharing geospatial-temporal information is now coming into place based on developments captured in standards by ISO, WMO, ITU, ICSU and OGC - including the newly established OGC Temporal domain working group. The new framework will enable capabilities in expressing and sharing scientific investigations including research on the emergence of forms over time. With these new capabilities we may come to understand Peirce’s observation that over time “all things have a tendency to take habits.”
10. “A coverage is a feature that associates positions within a bounded
That is to say -- a collection of features that share a common regular
geometry
OGC®
Coverages
space to feature attribute values”
Copyright (c) 2009 Opengeospatial Consortium
• Examples
– Raster image
– Polygon overlay
– Digital elevation matrix
Latitude -->
Longitude -->
21. class Figure 2: Observ ation Core
«FeatureT ype»
OM_Process
1 +procedure
ProcessUsed
«FeatureT ype»
OM_Observ ation
+ parameter: NamedValue [0..*]
+ phenomenonTime: TM_Object
+ resultTime: TM_Instant
+ validTime: TM_Period [0..1]
+ resultQuality: DQ_Element [0..*]
constraints
+metadata 0..1
{observedProperty shall be a phenomenon
associated with the type of the feature of interest}
{procedure shall be suitable for observedProperty}
{result type shall be suitable for observedProperty}
{a parameter.name shall not be used more than
once}
«instanceOf»
«FeatureT yp...
GFI_Feature
«T ype»
GFI_PropertyType
Domain
1
Range
+theGF_FeatureType 1
OGC®
MD_Metadata
«type»
Any
{root}
«metaclass»
GF_FeatureType
{root}
«metaclass»
GF_PropertyType
{root}
«DataT ype»
NamedValue
+ name: GenericName
+ value: Any
Observ ationContext
+ role: GenericName
Phenomenon
+observedProperty
1
+propertyValueProvider
0..*
+featureOfInterest
0..*
+relatedObservation
0..*
+generatedObservation
0..*
Metadata
«instanceOf»
+result
+carrierOfCharacteristics
0..*
WaterML2 Part 1: Time series data
22. OGC/WMO Hydrology Domain Working Group
4-Year International Effort – WaterML
Hydrology Domain Working Group formed
OGC at WMO Commission for Hydrology
November 2009
A time series for one variable at one location
Technical Meetings Each 3 Months
Four Interoperability Experiments
(Surface water, groundwater, forecasting)
Annual week-long workshops
Involvement by many countries
Acknowledgements: OGC, WMO, GRDC, NWS,
CUAHSI, BoM/CSIRO, USGS, GSC, Kisters, …….
2008 2009 2010 2011 2012
23. International Standardization of WaterML
• Hydrology Domain Working Group
– standards for water data: WaterML 2.0 suite
– organizing Interoperability Experiments (IEs)
focused on different sub-domains of water
• Chairs:
– Ilya Zaslavsky (USA)
– Tony Boston (Australia)
– Silvano Pecora (Italy)
OGC®
Iterative Development
http://external.opengis.org/twiki_public/bin/view/HydrologyDWG/WebHome
24. HydroDWG: Suite of Water Information Standards
OGC®
WaterML2Part5:
River Channel
(RiverML, under
development)
WaterML2Part1:
Water Quantity
Observation
(OGC10-126r4)
WaterML2Part2:
Gauging
Observation
(OGC13-021rX)
WaterML2Part3:
Water Quality
Observation
(OGC14-003rX)
CSML3:
Atmospheric-water
component
SoilML:
Soil-water
component
WaterML2Part4:
Groundwater
(GWML2, under
development)
TimeSeriesML
(under
development) Suite of Water Information Standards:
towards the identification, observation
and representation of hydrologic
features using standards
HY_Features,
common hydrologic
feature model
(OGC11-039r3)
26. What is the OpenMI?
• An interface standard (API) for:
• run time (in memory) data exchange between
models, databases & other components
• Whose purpose is to:
• improve ability to model complex scenarios
Application
User interface
Input data
Hydraulics
Output data
Application
User interface
Input data
Rainfall/Runoff
Output data
OpenMI
28
27. Linking modelled quantities
Rainfall Runoff Model River Model
Accepts Provides
Rainfall
(mm)
Runoff
(m3/s)
Temperature
(Deg C)
Evaporation
(mm)
Accepts Provides
Upstream Inflow
(m3/s)
Outflow
(m3/s)
Lateral inflow
(m3/s)
Abstractions
(m3/s)
Discharges
(m3/s)
28. What?
When? Where?
10:00 12:30
1.0 1.0
1.0
1.5
1.0
1.0
1.2
1.1
1.2
1.0
e1
e2
e3
e4
e5
t1 t2
The data model
30
29. Current status of OpenMI
• OpenMI 2.0 available and in use since 2010
http://sourceforge.net/projects/openmi/files/Version_2.0.0.0/
• OpenMI 2.0 submitted to OGC for acceptance
– Approval Date: 2013-12-06
– Publication Date: 2014-05-26
• http://www.opengeospatial.org/standards/openmi
– Document 11-014r3
31
32. Model Interoperability - An Evolution
(Source: S. Nativi, CNR, GEOSS Future Products Workshop)
OpenMI
ESMF
33. Model Web and Sensor Web in GEOSS
Societal
Benefits
Decision Support
Assessments
Sensor Web
• Remotely-sensed
• In situ
Policy
Decisions
On-going feedback to optimize value and reduce gaps
Model Web
• Oceans
• Ice
• Land
• Atmosphere
• Solid Earth
• Biosphere
Interoperability
and standards