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 standardizationThe Geomind Metadata Profile

2. Geophysical data standardizationGeneral Geophysical Data Model

3. Implementationpossible 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 >>> GGDMand a new XML based geophysical markup language >>> G.??ML(GML, GeoscienceML, WellLogML, WITSML, seismic XML is being defined )

dataType1

dataType2

dataType3

dataType4

Appl.1

Appl.2

App.3

Appl.4

Without standards, all data types must be handled differently by different specific applications

Metadata Standardization

dataType1

dataType2

dataType3

dataType4

With standards, all data types can be handled in a uniform way

MD

MD

MD

MD

Appl.

Metadata Standardization

Metadata Standardization

What is metadata ?

Metadata is data about data

What citation/titleWho metadata contact, point of contact,

citation/responsible partyWhen metadata date stamp, citation/dates, time extentWhere geographic code, geographic description, bounding

box, bounding polygonWhy abstract, purposeHow data quality/lineageFrom who distributorHow to get distribution optionsHow much distribution options/fees

ISO19115 Meatadata for geographic datasets

ISO19115 core Geophysical extensions

GEOMIND Profile 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.)

Modification of the ISO19115 metadata standard (the GEOMIND profile)

Metadata Standardization

ISO19115 MD_Metadata

GE_GeophObject

GE_GeophObjectSet

GE_Report

New

spe

cifie

d cl

asse

s

GG_MeasuringConditions

GG_Instrumentation

GG_parameterSet

GG_parameterCatalogue

GE_GeophysicalInfo

New

met

adat

a se

ctio

n

Modification of the ISO19115 metadata standard (the GEOMIND profile)

Metadata Standardization

Metadata Standardization

Geophysical Object

Abstraction for geophysical information handled as a natural unit. Measurement, Model (1D, 2D, 3D, 4D)

Geophysical Object Set

Collection of geophysical objects, grouped by common properties or constraints Project, Campaign, Coverage

Report

Any kind of documentation related to geophysical objects or object sets. Map, Profile, Sounding, Text

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 ?

Take the gears … instrumentation, devices

Go out to the field … localCRS, origin, azimuth, elevation

Real world data model entities

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

sDevicetype, name, description

localCRS

Originspheric, chartesian elevation

azimuth

layout

layoutComponent

domainSetregularSequence, irregularSequence

recording

rangeSetmeasDataArray

parameterSet

boxsize, position, orientation

parameterSet

parameterSet

legend

Gravity station & a link of stations

VES sounding

TDEM sounding & sounding profile Borehole logs

( nG & VSP ) Seismic profile

General Geophysical Data Model

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

• 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

GGDM and XML

General Geophysical Data Model

UML diagram of the measurement class

Distributed Database Architecture portal & dataprovider

Implementation

identifiersgeometry

metadata XML,or references

Relational DB

XML aware RDBMS or search engine

Metadata XMLData XML

Portal Data provider

Data

gif, jpgshp

Files

Met

adat

a W

EB

ser

vice

javascript

AJAX client applicationmapbuilder, openLayers, GoogleMaps API

XMLhttp

XSL

WMS, WFS server Geoserver

WFS

WMS

HTML

browser

Implementation

Metadata RDBMS or

search engine GGDMRDBMS or

search engine

Services – Open Source portal & Intranet solution

shp

data

Data Flow in Geomind

Data provider

User

WAF

Distributor(authority)

Data order

Html maps,rendered metadata, search

Data download

data

MD

Data provider

MD Metadata upload, and harvesting

Geomind Server

Implementation

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!