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
20
Embed
Recent developments in database management and standardization in the GEOMIND project László Sőrés (ELGI, Hungary) Mikael Pedersen (GEUS, Danmark) Valdas.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
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)
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
• 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,