Transcript 1. dia
Recent developments in database management and standardization in the GEOMIND project László Sőrés (ELGI, Hungary) Mikael Pedersen (GEUS, Danmark) Valdas Rapsevicius (ITG, Lithuania) Klaus Kühne (GGA, Germany) Jörg Kuder (GGA, Germany) Budapest, 2008.02.28 Standardization in Geophysics Introduction 1. Metadata standardization The Geomind Metadata Profile 2. Geophysical data standardization General Geophysical Data Model 3. Implementation possible database architectures & internet services Standardization in Geophysics Why ? Geophysical information is extremely polymorphic. Data access, exchange and use is limited due to the diversity of storage systems, data formats and the lack of general standards. (Though, geophysical methods related to oil industry do have specific standards) For who ? - individuals, who want to access geophysical data on the WEB - institutions, which want to provide geophysical data on the WEB - institutions, which want to have well organized data systems - interpreters, who works with many different methods - data experts, who wants to use more data types simultaneously (joint inversion) Standardization in Geophysics How ? Geomind project, WP6 : Specifications of standards for digital geophysical content Metadata level: Extend the ISO 19115 standard for geographic datasets >>> Geomind Metadata Profile Detailed data level: Create a General Geophysical Data Model >>> GGDM and a new XML based geophysical markup language >>> G.??ML (GML, GeoscienceML, WellLogML, WITSML, seismic XML is being defined ) Metadata Standardization dataType1 Appl.1 dataType2 Appl.2 dataType3 dataType4 App.3 Appl.4 Without standards, all data types must be handled differently by different specific applications Metadata Standardization dataType1 dataType2 MD MD Appl. dataType3 MD dataType4 MD With standards, all data types can be handled in a uniform way Metadata Standardization What is metadata ? Metadata is data about data citation/title metadata contact, point of contact, citation/responsible party metadata date stamp, citation/dates, time extent When geographic code, geographic description, bounding Where box, bounding polygon abstract, purpose Why data quality/lineage How From who distributor How to get distribution options How much distribution options/fees What Who Metadata Standardization Modification of the ISO19115 metadata standard (the GEOMIND profile) GEOMIND ISO19115 Meatadata for Profile geographic datasets ISO19115 core Extensions: • Added metadata classes (GO, GOS, REP, etc.) • Added codelist elemens (roles, dates, hyerarchy level, etc.) • New metadata section (geophysicalInfo) • New codelists (object types, object set types,devices etc.) Geophysical extensions Metadata Standardization Modification of the ISO19115 metadata standard (the GEOMIND profile) GE_GeophObject GE_GeophysicalInfo GG_Instrumentation GG_MeasuringConditions GE_GeophObjectSet GE_Report GG_parameterSet GG_parameterCatalogue New metadata section New specified classes ISO19115 MD_Metadata Metadata Standardization Geophysical Object Set Report Any kind ofofdocumentation Abstraction Collection for geophysical geophysical objects, related information to handled as grouped geophysical by acommon objects naturalor unit. properties object sets. or Measurement, constraints Map, Profile, Sounding, Model (1D, Text 2D, 3D, 4D) Project, Campaign, Coverage UML diagram of the three main classes Data Standardization Why are geophysical data systems so different ? Usually geophysical data systems are optimized for storage space, and performance. Geophysicists use different simplifications. Simple data structures do not require very sophysticated solutions and finally, it makes a big mess. Is it necessary ? With the increasing computing and storage resources size and speed optimization is not so crucial anymore. If we describe the measuring systems with more details it can be more general. Data Standardization What is common in measurements ? Real world data model entities Take the gears … instrumentation, devices Go out to the field … localCRS, origin, azimuth, elevation Position your equipments … layout, layoutComponent, box Start up the gears, collect data … parameterSet, recording, Processing & interpretation … measurement, model, inversion Document your work … metadata, geophObject, campaign, project General Geophysical Data Model measurement localCRS Origin spheric, chartesian azimuth elevation parameterSet layout layoutComponent parameterSet recording box size, position, orientation domainSet rangeSet regularSequence, irregularSequence measDataArray s Device parameterSet type, name, description General Geophysical Data Model Gravity station & a link of stations VES sounding The Big Puzzle A GGDM structure is very flexible. It can be as simple as a gravity station and as complex as a seismic profile TDEM sounding & sounding profile Borehole logs ( nG & VSP ) Seismic profile legend General Geophysical Data Model GGDM and XML • A GGDM relational database would contain about 80 tables • GGDM is object oriented and defined by XML schema definitions • Geophysical data can be transfered and stored as XML files, and can be validated against the GGDM schema. • XML aware database systems support XPATH indexing and provide fast document search. (Oracle, PostGIS, MySql, Apache Derby, Lucene) • Conversions to and from existing data formats can easily be done by XSL stylesheets. • Developement in XML based technologies is very fast UML diagram of the measurement class Implementation XML aware RDBMS or search engine metadata XML, or references gif, jpg shp Files identifiers geometry Metadata WEB service Distributed Database Architecture portal & dataprovider Metadata XML Data XML Data Relational DB Portal Data provider Implementation Services – Open Source portal & Intranet solution Metadata RDBMS or search engine browser GGDM RDBMS or search engine HTML shp WMS WFS WMS, WFS server Geoserver XML http javascript XSL AJAX client application mapbuilder, openLayers, GoogleMaps API Implementation Data Flow in Geomind Data order Distributor(authority) data WAF MD Data provider Data download Metadata upload, and harvesting Html maps, rendered metadata, search data MD Data provider Geomind Server User Standardization in Geophysics Conclusions 1. With the contribution of the EC eContentplus programme, an international geophysical information service, the GEOMIND portal is being set up. 2. As distributed systems require standardized data structures, geophysical standards were developed for metada and detailed data exchange. 3. The metadata standard, called the Geomind Profile, is an extension of the ISO19115 standard. 4. The detailed data standard is the schema based XML implementation of the General Geophysical Data Model (GGDM), developed by the consortium. 5. Using the new standards developing advanced geophysical information systems is more efficient and easier Thank You for your attention! Köszönöm a figyelmet!