1. Metadata in a Hydro-meteorological Model Chain
Principal Scientist at HR Wallingford in Oxfordshire, UK
Chair of OpenMI Association
Metadata in a Hydro-meteorological Model Chain
3rd Workshop on Coupling Technologies for Earth System Models 21st April 2015; Manchester, UK.
Q.K.Harpham

2. Context: DRIHM

3. DRIHM Use Case

4. DRIHM Model Architecture
Meteorology
Hydrology
P-Interface
Oceanography
Hydraulics
Q-Interface
Coastal
Morphology

5. OpenMI Composition

6. Metadata, Documentation and Licence
Model MAP
Metadata, Documentation and Licence
Adaptors to common interface standards for I/O using controlled vocabularies
What must I do to my model?
You must MAP it.
This presentation refers to how metadata can enable this model chain.
Portability of model components

7. Metadata Nature and Purpose
Supports discovery of model instances.
Supports an initial assessment of a model’s suitability for use.
Supports validation of coupling across interfaces.
Derived from standards.
As simple and short as possible.

8. Derived from ISO19115 (Title, Abstract, Point of Contact etc.)
Metadata Formulation
Derived from ISO19115 (Title, Abstract, Point of Contact etc.)
Extension to describe numerical models including:
Language, platform, dimensions, run time
Inputs and outputs (including Name, Description, Format, Feature Type)
Position given as bounding box
Parameter given in controlled vocabulary

9. Input / Output Interfaces
Particular attention to model I/O interfaces:
Assumption of single coordinate reference system.
Overall model extent for main catalogue.
Bounding box for each I/O.
Parameter name and file path (to identify data location).
Time range.
Timestep type (regular / irregular); max and min interval.

10. Encoded Implementation

11. Usage
Generally accurate and comprehensive.
Spatial (bounding boxes) and temporal (bounds and timesteps) highly accurate.
Controlled vocabularies used if offered, sometimes failed at scientific boundaries.
Not of sufficient quality to support automation.
Uncertainty over necessity of listing all inputs and outputs.

12. Interface Validation
Not precise enough to completely automate the interface, but validates to a certain level:
receivingModel.input.parameterName=providingModel.output.parameterName
AND
receivingModel.input.parameterUnit = providingModel.output.parameterUnit
receivingModel.input.timeRange.minimumTime >=
providingModel.output.timeRange.minimumTime
AND
receivingModel.input.timeRange.maximumTime <=
providingModel.output.timeRange.maximumTime

13. Spatial validation using feature type and bounding box:
Interface Validation
Spatial validation using feature type and bounding box:
receivingModel.input.featureType = providingModel.output.featureType
providingModel.output.position contains receivingModel.input.position
or coordinate by coordinate:
providingModel.output.y-coordinate >= greatest receivingModel.input.y-coordinate
AND
smallest providingModel.output.y-coordinate <=
smallest receivingModel.input.y-coordinate
AND similar for x-coordinate…

14. Harpham, Q. K. and Danovaro, E. , 2015
Harpham, Q.K. and Danovaro, E., Towards standard metadata to support models and interfaces in a hydro-meteorological model chain, Journal of Hydroinformatics , IWA Publishing. doi: /hydro
Q.K.Harpham