Establishing geological map and mineral occurrence data exchange

Establishing geological map and mineral occurrence data exchange standards Bruce Simons Geo. Science Victoria Geoscience data standards

Outline • Data exchange requirements (Interoperability) • Exchange standard for geological data (Geo. Sci. ML) • Testing the Geo. Sci. ML standard • The Mineral Occurrence extension • The Future Geoscience data standards

Delivering Government Digital Geoscience Data The problem • access to Government geoscience information is fragmented and inefficient 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 Geoscience data standards

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” Geoscience data standards

Interoperability Requirements interoperability semantic Data Content (Ontologies, Vocabularies) schematic Data Structure (Geo. Sci. ML, Mineral. Occurrences, O&M) syntax systems Data Language (GML, XML) Data Services (WFS, WMS, WCS) Geoscience data standards

Systems Agreement 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 Geoscience data standards

Syntax 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 Geoscience data standards

Interoperability Requirements interoperability semantic Data Content (Ontologies, Vocabularies) schematic Data Structure (Geo. Sci. ML, Mineral. Occurrences, O&M) syntax systems Data Language (GML, XML) Data Services (WFS, WMS, WCS) Geoscience data standards

Schematic Agreement Compound. Material «Type» Earth. Material: : Rock + consolidation. Degree: CGI_Term + lithology: Controlled. Concept [1. . *] Victoria lithology South Australia Geoscience data standards

Interoperability Requirements interoperability semantic Data Content (Ontologies, Vocabularies) schematic Data Structure (Geo. Sci. ML, Mineral. Occurrences, O&M) syntax systems Data Language (GML, XML) Data Services (WFS, WMS, WCS) Geoscience data standards

Semantic Agreement • Select geologic features where age = “xxx” Cainozoic? Late? Early? Archaean? Palaeozoic? Bolindian? Eastonian? Gisbornian? Geoscience data standards

Semantic Agreement • 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 Geoscience data standards

Interoperability Requirements Summary § availability of appropriate technologies - OGC, ISO, W 3 C § common data structure § software independence - CGI-IUGS § common data content § commitment to these standards - INSPIRE, GGIC Geoscience data standards

Interoperability Benefits • Open data standards • Efficiencies for government • Efficiencies for industry • Benefits for the wider geoscience community Geoscience data standards

What is Geo. Sci. ML? 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 Geo. Science Markup Language • the markup language delivers the model to web services • is machine readable Geoscience data standards

Geo. Science Markup Language Australia USA Committee for the Management and Application of Geoscience Information Interoperability Working Group Canada UK France Sweden Japan Italy Geoscience data standards

The Geo. Sci. ML Data Model Presented as a series of class diagrams which show the properties of, and relationships between, geological features Geological unit features • unit types (lithostratigraphic, chronostratigraphic) • age and geological history (events) • unit parts (child/parent relations) Metadata entity set information: : MD_Metadata {n} +metadata 0. . 1 +occurrence Description 0. . 1 +metadata +specification Any. Definition + + identifier: Scoped. Name name: Localized. Generic. Name [1. . *] + + observation. Method: CGI_Term. Value [1. . *] positional. Accuracy: CGI_Value 0. . * 1 «Feature. Type» Geologic. Feature: : Geologic. Feature «Type» Vocabulary: : Controlled. Concept + + «Feature. Type» Geologic. Feature: : Mapped. Feature +metadata observation. Method: CGI_Term. Value [1. . *] purpose: Description. Purpose = instance +geologic. History «Feature. Type» Geologic. Age: : Geologic. Event 0. . * +feature +preferred. Age 0. . 1 + + + event. Age: CGI_Value event. Environment: CGI_Term. Value [0. . *] event. Process: CGI_Term. Value [1. . *] +classifier 0. . 1 + • composition (earth materials) • • • metamorphism weathering character • spatial representation • • vocabularies metadata physical properties «estimated. Property» + body. Morphology: CGI_Term. Value [0. . *] + composition. Category: CGI_Term. Value [0. . 1] + exposure. Color: CGI_Term. Value [0. . *] + outcrop. Character: CGI_Term. Value [0. . *] + rank: Scoped. Name [0. . 1] role: Scoped. Name «estimated. Property» + lithology: Controlled. Concept [1. . *] + material: Compound. Material [0. . 1] + proportion: CGI_Value «Feature. Type» Geologic. Unit: : Geologic. Unit 0. . * «Data. Type» Geologic. Unit: : Composition. Part 0. . * +composition «estimated. Property» +contained. Unit «Data. Type» Geologic. Unit: : Geologic. Unit. Part 1 + +part 0. . * role: Scoped. Name «estimated. Property» + proportion: CGI_Value +metamorphic. Character +weathering. Character 0. . 1 «estimated. Property» + metamorphic. Facies: CGI_Term. Value [0. . *] + metamorphic. Grade: CGI_Term. Value [0. . 1] + peak. Pressure. Value: CGI_Numeric. Value [0. . 1] + peak. Temperature. Value: CGI_Numeric. Value [0. . 1] + protolith. Lithology: Earth. Material [0. . *] «Data. Type» Geologic. Unit: : Weathering. Description «estimated. Property» + environment: CGI_Term [0. . *] + weathering. Degree: CGI_Term [0. . 1] + weathering. Process: CGI_Term [0. . *] + weathering. Product: Earth. Material [0. . *] +physical. Property «Data. Type» Geologic. Unit: : Metamorphic. Description «Feature. Type» Geologic. Unit: : Lithologic. Unit «Feature. Type» Geologic. Unit: : Chronostratigraphic. Unit 0. . * «Data. Type» Geologic. Unit: : Physical. Description «estimated. Property» + bedding. Pattern: CGI_Term. Value [0. . *] + bedding. Style: CGI_Term. Value [0. . *] + bedding. Thickness: CGI_Value [0. . *] + defining. Age: CGI_Value + unit. Thickness: CGI_Numeric [0. . *] «estimated. Property» + density: CGI_Numeric [0. . 1] + magnetic. Susceptibility: CGI_Value [0. . 1] + permeability: CGI_Value [0. . 1] + porosity: CGI_Value [0. . 1] «Feature. Type» Geologic. Unit: : Lithodemic. Unit «Feature. Type» Geologic. Unit: : Lithostratigraphic. Unit «estimated. Property» + bedding. Pattern: CGI_Term. Value [0. . *] + bedding. Style: CGI_Term. Value [0. . *] + bedding. Thickness: CGI_Value [0. . *] + unit. Thickness: CGI_Numeric [0. . *] Geoscience data standards

Geological 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 Geoscience data standards

Geo. Sci. ML Benefits § a standard GML schema for geological data GSC schema WMS WFS G eo Sc USGS schema WMS WFS i. M L Ge o. S ci. M L BGS schema GSV schema WMS WFS Geo. S c i. ML GML Client ci. ML Geo. S L i. M c o. S Ge GA GA schema WMS WFS Geoscience data standards

Testing the Geo. Sci. ML 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 Geo. Sci. ML v 1. 1 Testbed 2 Use cases § display map, query one feature, return attributes in Geo. Sci. ML § query several map features, return Geo. Sci. ML file for download § reclassify map features based on Age or Lithology Geoscience data standards

Geo. Sci. ML Testbed 2 Accessing Geo. Sci. ML data using a web client in Canada Vancouver, CA Keyworth, UK Ottawa, CA Uppsala, SV Orleans, FR Reston, VA Portland, OR Canberra, AU Geo. Sci. ML Geoscience data standards

Lessons Learnt from Testbed 2 • 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 Geoscience data standards

Testbed 3 (in progress) 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 Geologic. Units of Silurian age”) • Use Case 4 – Data transport for import/export from applications • • GSI 3 D, Geo. Modeller, ESRI, d. B to d. B Use Case 5 – Register of Web, Vocabulary, Symbology services Delivery at IGC 33, August 2008 – Oslo, Norway Geoscience data standards

The Mineral Occurrences extension • GGIC established standard • Extension of Geo. Sci. ML • Data exchange model for mineral occurrences • Develop a standard model that includes reserves and resources • Standardised vocabularies Geoscience data standards

Mineral Occurrences Model «Feature. Type» Geologic. Age: : Geologic. Event +geologic. History +feature «Feature. Type» Geologic. Feature: : Geologic. Feature 0. . * + event. Age: CGI_Value + event. Environment: CGI_Term. Value [0. . *] +preferred. Age + event. Process: CGI_Term. Value [1. . *] + observation. Method: CGI_Term. Value [1. . *] 1 + purpose: Description. Purpose = instance Description 0. . 1 Mineral Deposit Model Earth «Feature. Type» Resource Earth. Resource 0. . * «Data. Type» Mineral. Deposit. Model Deposit Model +classification 0. . * 0. . 1 «estimated. Property» + mineral. Deposit. Group: Scoped. Name [1. . *] + mineral. Deposit. Type: Scoped. Name [0. . *] 1 «Data. Type» Endowment Reserve Endowment 0. . * Resource Product «Data. Type» Resource «estimated. Property» + commodity. Amount: CGI_Numeric [0. . 1] + cut. Off. Grade: CGI_Numeric [0. . 1] + grade: CGI_Numeric [0. . 1] 0. . * Reserve «Data. Type» Reserve + category: Resource. Category. Code + category: Reserve. Category. Code + includes. Reserves: Boolean 0. . * 1 1. . * + depth: CGI_Numeric [0. . 1] + material: Earth. Material [0. . *] + type: CGI_Term. Value [0. . 1] +supergene. Modification +composition 0. . * «Data. Type» Material Earth Resource Earth. Resource. Material + earth. Resource. Material. Role: ERMaterial. Role. C + material: Earth. Material +deposit «Data. Type» Earth Resource Material Raw. Material + material: Earth. Material + raw. Material. Role: Raw. Material. Role. Code Mineral. Occurrence «Data. Type» Commodity. Measure +commodity. Of. Interest +child 0. . * Earth Resource «Feature. Type» Commodity +ore. Amount +measure. Details + calculation. Method: Character. String + date: TM_Geometric. Primitive 1 1. . * + dimension: Earth. Resource. Dimension [0. . 1] + proposed. Extraction. Method: CGI_Term. Value [0. . 1] + source. Reference: CI_Citation [1. . *] «estimated. Property» + ore: CGI_Numeric «Data. Type» Supergene. Processes + source. Reference: CI_Citation [0. . *] 1 «estimated. Property» + dimension: Earth. Resource. Dimension [0. . 1] + expression: CGI_Term. Value [0. . *] + form: CGI_Term. Value [0. . *] + linear. Orientation: CGI_Linear. Orientation [0. . *] + planar. Orientation: CGI_Planar. Orientation [0. . *] 1 + shape: CGI_Term. Value [0. . *] 1 +source «Data. Type» Ore. Measure + observation. Method: CGI_Term. Value [1. . *] + positional. Accuracy: CGI_Value +parent 0. . 1 +genetic. Description + association. Type: CGI_Term. Value + includes. Reserves: Boolean + includes. Resources: Boolean 0. . * Mapped Feature «Data. Type» Mineral System Mineral. System Resource Mapped Feature «Feature. Type» Geologic. Feature: : Mapped. Feature +specification+occurrence «estimated. Property» + type: Mineral. Occurrence. Type. Code +composition 0. . * +resource. Extraction 1. . * +source. Commodity «Feature. Type» Commodity 0. . * 1 + commodity. Group: Scoped. Name [0. . *] + commodity. Name: Scoped. Name «estimated. Property» + commodity. Importance: Importance. Code [0. . 1] + commodity. Rank: Integer [0. . 1] Mining Activity 0. . * Mining Activity «Feature. Type» Product +commodity. Description 0. . * «Feature. Type» Mining. Activity + activity. Duration: TM_Period + product. Name: CGI_Term. Value 1 + activity. Type: Mining. Activity. Type. C 1. . * + source. Reference: CI_Citation [1. . *] + ore. Processed: CGI_Numeric [0. . 1] «estimated. Property» +produced. Material 1. . * +related. Activity + grade: CGI_Numeric [0. . 1] 0. . * + production: CGI_Numeric [0. . 1] + recovery: CGI_Numeric [0. . 1] 0. . 1 +associated. Mine «Feature. Type» Mine +related. Mine 0. . 1 + + + end. Date: TM_Instant [0. . 1] mine. Name: Mine. Name. Preference [1 source. Reference: CI_Citation start. Date: TM_Instant [0. . 1] status: Mine. Status. Code Geoscience data standards

Mineral Occurrences • Describes Earth Resources independent of associated human activities • Caters for descriptions of Earth Resources • Utilises Geo. Sci. ML Mapped. Feature to describe spatial representation • Utilises Geo. Sci. ML Earth. Material to describe host and associated materials • Deliver mineral occurrence data through the Australian Geoscience Portal • Real time access to the latest data Geoscience data standards

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 Geo. Sci. ML, Mineral Occurrence and Observation & Measurements data transfer standards Geoscience data standards

Where to from here? One. Geology 1: 1 million digital world geology of 87 nations Australia – 1: 2. 5 M and 1. 1 M (east) Other Geoscience “ML’s” currently under development • • • Landslides Geochronology Geochemistry Water Hydrogeology Earthquakes Geoscience data standards

Questions? Web sites CGI Home http: //www. cgi-iugs. org/ Geo. Sci. ML 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/Test. Bed 3 Use. Cases Geoscience data standards