1 / 18

Metadata Concepts for Hydrology

Page 1. Metadata Concepts for Hydrology. Michael Piasecki Department of Civil, Architectural, and Environmental Engineering Drexel University AGU Fall Meeting San Francisco December 13, 2004. Drexel University, College of Engineering. Page 2. Background.

mostyn
Download Presentation

Metadata Concepts for Hydrology

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Page 1 Metadata Concepts for Hydrology Michael Piasecki Department of Civil, Architectural, and Environmental Engineering Drexel University AGU Fall Meeting San Francisco December 13, 2004 Drexel University, College of Engineering

  2. Page 2 Background Consortium of Universities for the Advancement of the Hydrologic Sciences, Inc. Hydrologic Information Systems Group The objective of HIS is: • a hydrologic information system prototype of mapping and hydrologic data from the Neuse basin. These data will be served via the CUAHSI GeonGrid node at be operated at SDSC • a structure for the hydrologic data model • a hydrologic metadata definitionthat is compatible with the hydrologic data model and is interoperable with other Metadata profiles • conduct hydrologic case study in interpretation and visualization to estimate and represent streamflow and rainfall continuously in space and time across the stream network in the Neuse basin Drexel University, College of Engineering

  3. Numerical Models Prediction HSPF Sensor Arrays NGDC NWS NCDC USGS NWIS NCEP Air-Q MM5 Individual Samples Data Centers Page 3 The Demands METADATA Drexel University, College of Engineering

  4. DC ANZLIC FGDC Distribution – url, identification Coverage – temporal, spatial, location keywords Personnel – name, role, address Attributes – parameters, source, sensor, discipline, keywords, status, originator DIF ADN ISO Page 4 Metadata Standards ISO 19115 International Standard Organisation DIF Data Interchange Format, NASA ANZLIC Australia New Zealand Land Information Council DC Dublin Core FGDC Federal Geographic Data Committee ADN ADEPT, DELESE, NASA Drexel University, College of Engineering

  5. Page 5 Related Markup Languages Drexel University, College of Engineering

  6. Page 6 Meta-Semantics Categorization of Metadata Elements “search” “use” Drexel University, College of Engineering

  7. Page 7 Semantics: Problem1 Metadata Standards lack domain specific elements They do not suggest if area and outlet location should be defined when a watershed is being described ? They do not incorporate a list of possible stations and variables related to surface water collected by a particular Hydrologic Information Community, HIC Drexel University, College of Engineering

  8. e.g. search for Stage Height Metadata repository Page 8 Semantics: Problem 2 Metadata Standards do not resolve semantic heterogeneities Metadata (ISO) about dataset X keyword = Stage Height thesaurusName = GCMD Metadata (FGDC) about dataset YTheme_Keyword = Gage Height Theme_Keyword_Thesaurus= USGS Finds only data set X and not data set Y Drexel University, College of Engineering

  9. Approach 1 (static) • develop <<CodeLists>> to suit hydrologic domain • extend ISO 19115 to include community specific elements • try to map to other standards and develop Metadata Interchange Formats (MIF) • provide utility to fill out metadata sets to describe your data Approach 2 (dynamic) • Develop a hydrologic ontology that defines the common words and concepts (the meaning) used to describe and represent an area of knowledge. • Ontologies enable you to specify the semantics of your domain, your enterprise, or your community, or across many communities, in great and arbitrary greater detail • utilize specific technologies and tools to tie hydrologic ontology into the Semantic Web. • utilize ontology to define a Controlled Vocabulary in a Restricted Domain to be used in the <<CodeList>> environment Page 9 Semantics: Solution Drexel University, College of Engineering

  10. Hydrologic Metadata Hydrologic Metadata Semantic WEB Semantic WEB A consistent suite of geographic information schemata that will allow Geographic information to be integrated with information technology. ISO norm 19115. Hydrologic Ontology Definition: The Semantic Web is the representation of data on the World Wide Web. It is based on the Resource Description Framework (RDF), which integrates a variety of applications using XML for syntax and URIs for naming. http://www.w3.org/2001/sw/ www.isotc211.org "The Semantic Web is an extension of the current web in which information is given well-defined meaning, better enabling computers and people to work in cooperation." Page 10 Ontologies Drexel University, College of Engineering

  11. Metadata specifications Hydrologic vocabulary Metadata (ISO) about dataset X keyword = Stage Height thesaurusName = GCMD FGDC GCMD Mapper Metadata (FGDC) about dataset Y Theme_Keyword = Gage Height Theme_Keyword_Thesaurus= USGS Mapper ISO USGS Page 11 Resolve Semantic Heterogeneity e.g. search for Stage Height Finds data set X and Y Metadata repository Drexel University, College of Engineering

  12. Page 12 CUAHSI – Profile V.1.0 • Extend ISO • Set as core (Metadata elements selected to be used by CUAHSI) • Controlled Vocabulary • Create domain list to fit needs Express in machine readable format OWL/XML fully interoperable with original ISO Drexel University, College of Engineering

  13. Page 13 CUAHSI – Profile V.1.0 1) Extend ISO 19115 ISO 19108 ISO 19107 ISO 19110 ISO 19115 CUAHSI Profile In progress Features-Profile TimeSeries-Profile … HUC … Drexel University, College of Engineering

  14. Page 14 CUAHSI – Profile V.1.0 2) Set as core Using: “flag” to mark the core elements <owl:AnnotationProperty rdf:ID="core"> core = true Drexel University, College of Engineering

  15. Page 15 CUAHSI – Profile V.1.0 3) Controlled Vocabulary Ontologies Labels Annotations TOOLS Drexel University, College of Engineering

  16. Page 16 CUAHSI – Profile V.1.0 4) Set New Codelists • MD Classification Code for security Constraints • World • Group • Owner MD Classification Code for “Observation” Metadata based on SensorML, HydroML, … Drexel University, College of Engineering

  17. Page 17 CUAHSI-Core • Metadata Version 1.0: • selected 77 descriptive elements that are CUAHSI core, i.e that are mandatory for any data set within CUAHSI • made available online for review and comments • output is in SDSC formats MTF: template format MIF: interchange format • created a CUAHSI controlled vocabulary based on Global Change Master Directory • entire ISO 191xx family of metadata norms is also available for inclusion in CUAHSI profile http://loki.cae.drexel.edu/~how/tree/ Drexel University, College of Engineering

  18. Page 18 Thank you Questions? Drexel University, College of Engineering

More Related