2014
DOI: 10.2166/hydro.2014.061
|View full text |Cite
|
Sign up to set email alerts
|

Towards standard metadata to support models and interfaces in a hydro-meteorological model chain

Abstract: This paper seeks to move towards an un-encoded metadata standard supporting the description of environmental numerical models and their interfaces with other such models. Building on formal metadata standards and supported by the local standards applied by modelling frameworks, the desire is to produce a solution, which is as simple as possible yet meets the requirements to support model coupling processes. The purpose of this metadata is to allow environmental numerical models, with a first application for a … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
14
0

Year Published

2014
2014
2021
2021

Publication Types

Select...
5
3
1

Relationship

2
7

Authors

Journals

citations
Cited by 26 publications
(14 citation statements)
references
References 16 publications
0
14
0
Order By: Relevance
“…Each model provided on DRIHM is accompanied by a metadata record, an extended ISO19139 dataset (Harpham and Danovaro, ) and stored in an accompanying catalog (DRIHM Model Catalogue, ).…”
Section: Methodsmentioning
confidence: 99%
“…Each model provided on DRIHM is accompanied by a metadata record, an extended ISO19139 dataset (Harpham and Danovaro, ) and stored in an accompanying catalog (DRIHM Model Catalogue, ).…”
Section: Methodsmentioning
confidence: 99%
“…We started from the ISO19115 metadata standard for describing spatial datasets and adopted an extension described in [13]. To grant consistency, we rely on two complementary techniques: unified storage of experiment parameters among model UIs, so that the generated configurations (usually as textual namelists) are shared among models and coherent; and metadata describing experiment steps, the associated model, the required input files and the expected outputs, file format and some constraints on the geographical domain, and the time frame described by the outputs.…”
Section: Experiments Configurationmentioning
confidence: 99%
“…This allows to provide general information (such as a title, an abstract, owning organization or contact details, execution platform, link to sources or binaries) but also, for each input and output: Name, Description, Format, whether it is mandatory. In [19] we further extended the set of metadata by: File full pathname of the input/output file (if any). Feature Type a description of the spatial / temporal structure of the data, such as PointSeries, GridSeries, .…”
Section: Workflow Data Model and Metadatamentioning
confidence: 99%