GeoSciML = GeoScience Markup Language An international (IUGS) application of GML3.1.1 (an XML schema= Geography Markup Language) for sharing geologic information Interoperability Working Group IUGS Commission for the Management and Application of GP12

1
The benefits of developing GeoSciML to the
global geoscience community Tim Duffy John
Laxton, BGS Edinburgh European Geoinformatics
Workshope-Science Institute 7 March 2007
2
Objectives

• Developing international standards for the
  structure of geological information (i.e. data
  model standards) to enable interoperability,
  particularly among national geological survey
  agencies.
• More specific objectives are
• to develop a conceptual model of geoscientific
  information drawing on existing data models
• to implement an agreed subset of this model in an
  agreed schema language
• implement an XML/GML encoding of the model subset
• develop a testbed to illustrate the potential of
  the data model for interchange
• identify areas that require standardised
  classifications in order to enable interchange

3
Participating Organisations

• BGS, UK
• BRGM, France
• CSIRO Exploration Mining, Australia
• GSC, Canada
• Geological Survey of Arizona, USA
• GeoScience Australia, Australia
• GeoScience Victoria, Australia
• SGU, Sweden
• USGS, USA

4
GeoScience Markup Language (GeoSciML)
Current activities

• Use cases Requirements Task Group
• develop technical goals for GeoSciML by
  describing new use-cases and requirements
• Design Task Group
• Design GeoSciML as a Geography Markup Language
  (GML) schema for sharing geological information
• Implementation Testbed Task Group
• Demonstrate GeoSciML using Web Feature and Web
  Mapping Services
• Service Architecture Task Group
• Develop the formal architecture required to
  implement services that deliver the use cases
• Outreach Technical Assistance
• Responsible for providing advice and assistance
  to direct collaborators, assisting them to deploy
  conformant GeoSciML services
• Concept Definitions Task Group
• Design the vocabulary (content) services that
  meet the schema requirements

5
becoming mainstream
6
What does one need to achieve interoperability?
ResponsibleCommunity
Interoperability
semantic
(data content)
Ontology
GeoscienceCommunity
schematic
(data structure)
GeoSciML
Geography Markup Language
syntax
(data language)
OpenGISCommunity
Web Feature Services, Web Mapping Services
systems
(data systems)
7
What is GeoSciML?

• 1. Conceptual Data Model
• scientifically robust
• structured attribute data
• based on existing models
• UML schema expressed as an application of GML
  3.1.1

• Geologic units
• lithological units

• Earth Materials
• rocks

• Structures
• contacts, faults

• Vocabularies
• lookup tables, authority tables

8
What is GeoSciML?

• 2. Data Exchange Language
• generated from UML
• based on GML

9
One service many uses
GML-based data can be .
Rendered into a queryable map
formatted into a report or .
read and used by any WFS/GML enabled
application
10
What is GeoSciML Testbed 2?

• It demonstrates delivery of Geological Data
  using
• Web Feature Services (WFS)
• Web Mapping Services (WMS)
• GeoSciML
• Based on international standards (ISO, OGC)

11
GeoSciML Testbed2 architecture
Databases, digital maps with local data structures
Sweden
USA
Canada
UK
Data sources
12
Remember

• Service not designed to work with any specific
  software package (eg ESRI)
• Uses open community defined standards (ISO,
  OpenGIS)
• Uses a rich scientific data model
• Complex Feature GML 3.1
• Not traditional flat GIS data structures
• About exchange of data (not use of data)

13
USE CASE ONEGet Feature Information

• Display map
• Query one feature (a geometry)
• Return attributes in GeoSciML format
• Bonus - Return attributes as HTML formatted
  GeoSciML

14
(No Transcript)
15
(No Transcript)
16
(No Transcript)
17
(No Transcript)
18
(No Transcript)
19
(No Transcript)
20
USE CASE TWOGeoSciML Data Download

• Display map
• Select several features
• Return attributes of the selected features as
  GeoSciML file for download

21
(No Transcript)
22
(No Transcript)
23
(No Transcript)
24
(No Transcript)
25
USE CASE THREEThematic Mapping

• Reclassify map features based on
• Lithology
• Geological Age
• Essentially produce two thematic maps

26
(No Transcript)
27
(No Transcript)
28
(No Transcript)
29
(No Transcript)
30
OTHER WORK Boreholes (from Testbed 1)

• Developed by UK (BGS) and France (BRGM)
• Delivery of Boreholes data

31
OTHER WORKBoreholes BRGM Client

• Display Boreholes points from WFS
• Select Borehole
• Display borehole attributes as
• GeoSciML/XMML
• HTML based on GeoSciML
• Graphic Log based on GeoSciML

32
(No Transcript)
33
(No Transcript)
34
(No Transcript)
35
(No Transcript)
36
(No Transcript)
37
(No Transcript)
38
(No Transcript)
39
Conclusions

• Many geological surveys have now specified
  GeoSciML as the geoscience data exchange standard
• Committed to delivering this data using OGC web
  services
• National and international uses include
• INSPIRE
• Delivering data to customers in non-proprietary
  format
• Making datasets available for WWW combination
  with other datasets (WMS) through tools like
  GoogleEarth
• Proposed global 11 Million geology map
  (OneGeology)

40
Acknowledgements

• The work described here is the result of the
  efforts of many different individuals in
  different organisations but in particular we
  would like to acknowledge
• Bruce Simons (GSV), Christian Bellier (BRGM),
  Eric Boisvert (GSC), Boyan Brodaric (GSC), Simon
  Cox (CSIRO), Jonas Holmberg (SGU), Dominique
  Janjou (BRGM), Bruce Johnson (USGS), Dale
  Pewrcival (GA), Steve Richard (AGS), Oliver
  Raymond (GA), Alistair Ritchie (GSV), Francois
  Robida (BRGM), Marcus Sen (BGS), Jean-Jacques
  Serrano (BRGM), Lars Stolen (SGU), Lesley Wyborn
  (GA)
• BGS input to this work has been supported by the
  Information Systems Development Programme

41
Questions?
For further information on GeoSciML https//www.s
eegrid.csiro.au/twiki/bin/view/CGIModel/GeoSciML