geoscience data standards establishing geological map and mineral occurrence data exchange standards...

Geoscience data standards

Establishing geological map and mineral occurrence data exchange standards

Bruce Simons

GeoScience Victoria


OutlineOutline

• Data exchange requirements (Interoperability)

• Exchange standard for geological data (GeoSciML)

• Testing the GeoSciML standard

• The Mineral Occurrence extension

• The Future


The problem• access to Government geoscience information is fragmented and inefficient

Delivering Government Digital Geoscience Data

Delivering Government Digital Geoscience Data

2004 Minerals Exploration Action Agenda …

• existing information is distributed across eight state and federal agencies

• each with its own information management systems and data formats

• up to 80% of time acquiring pre-competitive data is taken up by reformatting disparate data from government sources

• a disincentive to exploration


Why is it so hard?

• 8 Australian jurisdictions provide digital geoscience map data

• 8 data structures and delivery systems

• 2 (at least) proprietary software specific data formats

• cannot access more than one agency’s data at a time

The Solution is “Interoperability”• Establish a software-independent DATA TRANSFER STANDARD

“the ability of software and hardware on different machines from different vendors to

share data”


systems

syntax

schematic

semantic

interoperability

Data Structure (GeoSciML, MineralOccurrences, O&M)

Data Content (Ontologies, Vocabularies)

Data Language (GML, XML)

Data Services (WFS, WMS, WCS)

Interoperability RequirementsInteroperability Requirements


Agree to use Web Services (WFS, WMS, WCS)

Software capabilities are limited to simple data models

• Existing vendor and open source software aim to support OGC

web service specifications (e.g. GML and complex features)

• Ongoing collaborative work with software developers to serve the

complex feature model needed for geological information

Not all required OGC standards properly specified and

tested

• E.g. Registries, binding WFS to WMS, handling xpath/href links

Systems AgreementSystems Agreement


How do you convert standard representations of complex

data models (UML) to standard schema (GML)?

• Need to establish UML rules (single inheritance, associations

must have role names, etc)

• Need to establish conversion rules (what to do with Union,

interface classes etc)

• Establish name spaces

Need software to enable automatic generation of schema

Syntax AgreementSyntax Agreement


systems

syntax

schematic

semantic

interoperability







Victoria

South Australia

Schematic AgreementSchematic AgreementCompoundMaterial

«Type»

EarthMaterial::Rock

+ consolidationDegree: CGI_Term+ lithology: ControlledConcept [1..*]

lithology


systems

syntax

schematic

semantic

interoperability







Cainozoic?

Palaeozoic?

Archaean?

Bolindian?Eastonian?Gisbornian?

Late?Early?

Semantic Agreement Semantic Agreement • Select geologic features where age = “xxx”


• Geological data is largely text-based and interpretive. Simple

numerical data is rare.

• Compliance to many controlled vocabularies is not a trivial exercise

• Compliance to vocabularies is crucial to be able to construct

standardised requests on distributed data

• Establish language independent identifiers that local terms and

languages can be mapped to

• GGIC Controlled Vocabularies Working Group and CGI

Geoscience Concepts Task Group

Semantic Agreement Semantic Agreement


availability of appropriate technologies

common data structure

software independence

common data content

commitment to these standards


- OGC, ISO, W3C

- CGI-IUGS

- INSPIRE, GGIC

Summary


• Open data standards

• Efficiencies for government

• Efficiencies for industry

• Benefits for the wider geoscience community

Interoperability BenefitsInteroperability Benefits


A Geological Data Model• based on real world concepts

• represents the complexity of geology (hierarchical, relational)

• tells users what geological information goes where

• developed by the scientific community

• internationally agreed

• builds on established standards such as GML (Geographic Markup

Language)

• uses the ISO ‘feature’ model

GeoScience Markup Language • the markup language delivers the model to web services

• is machine readable

What is GeoSciML?What is GeoSciML?


Committee for the Management and Application of

Geoscience Information

Committee for the Management and Application of

Geoscience Information

Australia

USA

Canada

France

UK

Sweden

Italy

Japan

Interoperability Working Group

GeoScience Markup LanguageGeoScience Markup Language


«FeatureType»GeologicFeature::MappedFeature

+ observationMethod: CGI_TermValue [1..*]+ positionalAccuracy: CGI_Value

«FeatureType»GeologicFeature::GeologicFeature

+ observationMethod: CGI_TermValue [1..*]+ purpose: DescriptionPurpose = instance

«FeatureType»GeologicUnit::GeologicUnit

«estimatedProperty»+ bodyMorphology: CGI_TermValue [0..*]+ compositionCategory: CGI_TermValue [0..1]+ exposureColor: CGI_TermValue [0..*]+ outcropCharacter: CGI_TermValue [0..*]+ rank: ScopedName [0..1]

«DataType»GeologicUnit::GeologicUnitPart

+ role: ScopedName

«estimatedProperty»+ proportion: CGI_Value

«DataType»GeologicUnit::MetamorphicDescription

«estimatedProperty»+ metamorphicFacies: CGI_TermValue [0..*]+ metamorphicGrade: CGI_TermValue [0..1]+ peakPressureValue: CGI_NumericValue [0..1]+ peakTemperatureValue: CGI_NumericValue [0..1]+ protolithLithology: EarthMaterial [0..*]

«FeatureType»GeologicUnit::ChronostratigraphicUnit

«estimatedProperty»+ beddingPattern: CGI_TermValue [0..*]+ beddingStyle: CGI_TermValue [0..*]+ beddingThickness: CGI_Value [0..*]+ definingAge: CGI_Value+ unitThickness: CGI_Numeric [0..*]

«FeatureType»GeologicUnit::LithologicUnit

«FeatureType»GeologicUnit::LithostratigraphicUnit

«estimatedProperty»+ beddingPattern: CGI_TermValue [0..*]+ beddingStyle: CGI_TermValue [0..*]+ beddingThickness: CGI_Value [0..*]+ unitThickness: CGI_Numeric [0..*]

«FeatureType»GeologicUnit::LithodemicUnit

«DataType»GeologicUnit::PhysicalDescription

«estimatedProperty»+ density: CGI_Numeric [0..1]+ magneticSusceptibility: CGI_Value [0..1]+ permeability: CGI_Value [0..1]+ porosity: CGI_Value [0..1]

«DataType»GeologicUnit::WeatheringDescription

«estimatedProperty»+ environment: CGI_Term [0..*]+ weatheringDegree: CGI_Term [0..1]+ weatheringProcess: CGI_Term [0..*]+ weatheringProduct: EarthMaterial [0..*]

«DataType»GeologicUnit::CompositionPart

+ role: ScopedName

«estimatedProperty»+ lithology: ControlledConcept [1..*]+ material: CompoundMaterial [0..1]+ proportion: CGI_Value

AnyDefinition

«Type»Vocabulary::ControlledConcept

+ identifier: ScopedName+ name: LocalizedGenericName [1..*]

Metadata entity set information::MD_Metadata

{n}

«FeatureType»GeologicAge::GeologicEvent

+ eventAge: CGI_Value+ eventEnvironment: CGI_TermValue [0..*]+ eventProcess: CGI_TermValue [1..*]

+specification 1

Description

+occurrence

0..*

+part

0..*

+containedUnit

1

+metamorphicCharacter

0..1

+physicalProperty

0..*

+weatheringCharacter

0..1

+composition«estimatedProperty»

0..*

0..*

+classifier

0..1

+metadata

0..1

+metadata0..1

+metadata

0..1

+preferredAge 0..1

+feature

+geologicHistory

0..*

Presented as a series of class diagrams which show the properties of, and relationships between, geological features

The GeoSciML Data ModelThe GeoSciML Data Model

Geological unit features

• composition (earth materials)

• metamorphism

• weathering character

• physical properties

• spatial representation

• unit types (lithostratigraphic, chronostratigraphic)

• age and geological history (events)

• unit parts (child/parent relations)

• vocabularies• metadata


Geological Data Model BenefitsGeological Data Model Benefits

• data providers need only “map” their own local data

structures to the data transfer structure

• data providers don’t need to change their local

database structures to use the transfer standard

• allows language independent terminology to be used

(i.e. controlled vocabularies)

• is open source

• software vendor independent


GeoSciML BenefitsGeoSciML Benefits

GML

Client

WMS WFS

WMSWFS

WMSWFS

WMS WFS

GeoSciML

GeoSciML

GeoSciML

GeoSciML

GA

GSV

BGS

USGS

BGS

schema

GSV

schema

GA

schema

USGS

schema

a standard GML schema for geological data

WMS WFS

GeoSciML

GSCGSC

schema


Testing the GeoSciML standardTesting the GeoSciML standard

Testbed 1 2005 - A borehole demonstrator between UK and France

Testbed 2 2006 – A six nation demonstrator delivering geological

map data from globally distributed sources using GeoSciML v1.1

Testbed 2 Use cases

display map, query one feature, return attributes in GeoSciML

query several map features, return GeoSciML file for download

reclassify map features based on Age or Lithology


GeoSciML

Vancouver, CAVancouver, CAUppsala, SVUppsala, SV

Canberra, AUCanberra, AU

Ottawa, CAOttawa, CA

Reston, VAReston, VA

Keyworth, UKKeyworth, UK

Portland, ORPortland, OR

Orleans, FROrleans, FR

Accessing GeoSciML data using a web client in CanadaAccessing GeoSciML data using a web client in Canada

GeoSciML Testbed2GeoSciML Testbed2


• Successfully demonstrated WMS/WFS delivery, display and download of distributed data sources and simple query functions

• Not previously attempted with such a complex model

• Identified capabilities and limitations of WFS and OGC

standards

• Highlighted technical challenges to be able to deliver and

consume complex features using WFS• Highlighted the need to establish well-defined limits for any

web data services • Reinforced the importance of documentation of the data model

to guide participants

Lessons Learnt from Testbed2Lessons Learnt from Testbed2


Wide ranging and ambitious use cases

• Use Case 1 – Render a geological map from multiple data sources

• symbols based on age or lithology• language dependent legend

• Use Case 2 – Return GML for mapped features in bounding box

• service profiles may vary to deliver sampling features, mapped features of geologic structures, links to composition or a stratigraphic lexicon

• Use Case 3 – User defined query (eg “all GeologicUnits of Silurian age”)

• Use Case 4 – Data transport for import/export from applications

• GSI3D, GeoModeller, ESRI, dB to dB

• Use Case 5 – Register of Web, Vocabulary, Symbology services

Delivery at IGC33, August 2008 – Oslo, Norway

Testbed 3 (in progress)Testbed 3 (in progress)


• GGIC established standard

• Extension of GeoSciML

• Data exchange model for mineral occurrences

• Develop a standard model that includes

reserves and resources

• Standardised vocabularies

The Mineral Occurrences extensionThe Mineral Occurrences extension


Mineral SystemMineral Deposit Model

Earth Resource

Mapped Feature

Earth Resource Material

MineMining Activity

Commodity

Product

Resource

Reserve

Endowment

«FeatureType»GeologicFeature::GeologicFeature

+ observationMethod: CGI_TermValue [1..*]+ purpose: DescriptionPurpose = instance

«FeatureType»GeologicFeature::MappedFeature

+ observationMethod: CGI_TermValue [1..*]+ positionalAccuracy: CGI_Value

«FeatureType»EarthResource

+ sourceReference: CI_Citation [0..*]

«estimatedProperty»+ dimension: EarthResourceDimension [0..1]+ expression: CGI_TermValue [0..*]+ form: CGI_TermValue [0..*]+ linearOrientation: CGI_LinearOrientation [0..*]+ planarOrientation: CGI_PlanarOrientation [0..*]+ shape: CGI_TermValue [0..*]

«DataType»SupergeneProcesses

+ depth: CGI_Numeric [0..1]+ material: EarthMaterial [0..*]+ type: CGI_TermValue [0..1]

«FeatureType»MineralOccurrence

«estimatedProperty»+ type: MineralOccurrenceTypeCode

«DataType»MineralSystem

+ associationType: CGI_TermValue

«DataType»MineralDepositModel

«estimatedProperty»+ mineralDepositGroup: ScopedName [1..*]+ mineralDepositType: ScopedName [0..*]

«DataType»EarthResourceMaterial

+ earthResourceMaterialRole: ERMaterialRoleCode+ material: EarthMaterial

«FeatureType»MiningActivity

+ activityDuration: TM_Period+ activityType: MiningActivityTypeCode+ oreProcessed: CGI_Numeric [0..1]

«FeatureType»Mine

+ endDate: TM_Instant [0..1]+ mineName: MineNamePreference [1..*]+ sourceReference: CI_Citation+ startDate: TM_Instant [0..1]+ status: MineStatusCode

«FeatureType»Product

+ productName: CGI_TermValue+ sourceReference: CI_Citation [1..*]

«estimatedProperty»+ grade: CGI_Numeric [0..1]+ production: CGI_Numeric [0..1]+ recovery: CGI_Numeric [0..1]

«FeatureType»Commodity

+ commodityGroup: ScopedName [0..*]+ commodityName: ScopedName

«estimatedProperty»+ commodityImportance: ImportanceCode [0..1]+ commodityRank: Integer [0..1]

«DataType»OreMeasure

+ calculationMethod: CharacterString+ date: TM_GeometricPrimitive+ dimension: EarthResourceDimension [0..1]+ proposedExtractionMethod: CGI_TermValue [0..1]+ sourceReference: CI_Citation [1..*]

«estimatedProperty»+ ore: CGI_Numeric

«DataType»Endowment

+ includesReserves: Boolean+ includesResources: Boolean

«DataType»Reserve

+ category: ReserveCategoryCode

«DataType»Resource

+ category: ResourceCategoryCode+ includesReserves: Boolean

«FeatureType»GeologicAge::GeologicEvent

+ eventAge: CGI_Value+ eventEnvironment: CGI_TermValue [0..*]+ eventProcess: CGI_TermValue [1..*]

«DataType»CommodityMeasure

«estimatedProperty»+ commodityAmount: CGI_Numeric [0..1]+ cutOffGrade: CGI_Numeric [0..1]+ grade: CGI_Numeric [0..1]

«DataType»RawMaterial

+ material: EarthMaterial+ rawMaterialRole: RawMaterialRoleCode

1

+producedMaterial

1..*

1

+measureDetails

1..*

+feature+geologicHistory

0..*

+preferredAge

0..1

1

+oreAmount

0..*

0..*

+commodityOfInterest 1..*

0..*

+composition 0..*

0..*

+sourceCommodity

1

+relatedActivity1..*

+associatedMine0..1

0..*

+relatedMine0..1

1

+composition

0..*

0..*

+classification

0..1

0..*

+geneticDescription

0..1

1+supergeneModification

0..*

+child0..*

+parent0..1

+resourceExtraction 0..*

+deposit1

+specification

1 Description

+occurrence

0..*

+source1

+commodityDescription

1..*

Mineral System

Mineral Deposit Model

Earth Resource

Mapped Feature

Earth Resource Material

Mine

Mining Activity

Commodity

Product

Resource Reserve

Endowment

Mineral Occurrences ModelMineral Occurrences Model


• Describes Earth Resources independent of associated human activities

• Caters for descriptions of Earth Resources• Utilises GeoSciML MappedFeature to describe

spatial representation• Utilises GeoSciML EarthMaterial to describe host

and associated materials• Deliver mineral occurrence data through the

Australian Geoscience Portal• Real time access to the latest data

Mineral OccurrencesMineral Occurrences


Where to from here?Where to from here?

Within Australia…

An Australian Geoscience Portal

• All government geoscience map data

• Data served from distributed state and

federal sites to a single portal

• Using the GeoSciML, Mineral

Occurrence and Observation &

Measurements data transfer standards


OneGeology1:1 million digital world geology of 87 nationsAustralia – 1:2.5M and 1.1M (east)

Other Geoscience “ML’s” currently under development

• Landslides

• Geochronology

• Geochemistry

• Water

• Hydrogeology

• Earthquakes

Where to from here?Where to from here?


Questions?

Web sites CGI Home

http://www.cgi-iugs.org/

GeoSciML Data Model Working Group home

http://www.cgi-iugs.org/tech_collaboration/data_model/downloads.html

CGI Data Model Collaboration twiki

https://www.seegrid.csiro.au/twiki/bin/view/CGIModel/

Testbed 3 Use Cases

https://www.seegrid.csiro.au/twiki/bin/view/CGIModel/TestBed3UseCases

geoscience data standards establishing geological map and mineral occurrence data exchange standards...

Documents