1. www.csiro.au Introduction to GeoSciML: standard encoding for transfer of geoscience information Simon Cox CSIRO Exploration and Mining 11 September 2006

2. Canada USAUKFrance Germany Korea Japan Denmark Sweden Finland Netherlands AustraliaPolandCzech Motivation International geologic map data interoperability  availability of technologies for open geospatial standards (OGC, ISO)  commitment to these standards by many national data providers  international collaboration initiated in Edinburgh 2003, under IUGS-CGI

3. Geologic map data schematic interoperability  develop a standard GML schema for data transfer in WFS and WMS  conduct a multi-country testbed  demonstrate the need for transfer standards for data content GML Client Goals of IUGS-CGI Interoperability Workgroup WMS WFS WMS WFS WMS WFS WMS WFS WMS WFS WMS WFS USGS schema BRGM schema GSC schema BGS schema SGU schema GA schema GeoSciML GA Oracle, ESRI SGU BGS BRGM USGS ESRI GSC Oracle, ESRI

4. Scope: information required for production and maintenance of geologic maps Mapped Features  units, structures Legend  unit description  stratigraphic column, other classifications  Geologic timescales Borehole data Field observations & measurements  structure measurements, material descriptions … Lab measurements  geochem, geochronology GeoSciML v1.1 (testbed) GeoSciML v2

5. Precursors NADM – US/Canada  geologic instances and classifications – UML BRGM – France  Boreholes, solid geology BGS – DGSM – UK  3D geology XMML - eXploration and Mining Markup Language  Mineral exploration data – GML

6. Scope Mapped Features  units, structures Legend  unit description  stratigraphic column, other classifications  Geologic timescales Borehole data Field observations & measurements  structure measurements, material descriptions … Lab measurements  geochem, geochronology GeoSciML v1.1 (testbed) GeoSciML v2 OGC sensor-web ~ NADM model, GML encoding ~ XMML, BGS, BRGM

7. Modelling methodology 1.Design using pictures UML class diagrams adopt and adapt existing & external standards, influence if possible 2.Prove it with Code Use sample XML documents to test the model as you go 3.Generate code (XML Schema) automatically maintain the model using the diagrams, not the validation tooling Compliant with ISO/TC 211 & Open Geospatial Consortium standards

8. Example feature-type Specimen test instance Specimen test 1 … chips 0.35 …

9. Descriptions and occurrences Map polygon Legend item Observational setting

10. Descriptive values e.g. “Usually 2mm to boulder-sized” ScopedName = label + vocabulary reference Measure = number + uom

11. Achievements GeoSciML 1.x defined (but not documented) Testbed 1 implemented (2 countries, 2 sites) Testbed 2 implemented (6 countries, 8 sites)  GeoSciML 2.0 scoped logical model: GML-UML Granite, syenite, volcanogenic sandstone, conglomerate, minor trachyte lava Mount Leinster Igneous Complex typicalNorm <value codeSpace="http://www.iugs- cgi.org/geologicAgeVocabulary">Triassic <value codeSpace="http://www.iugs- cgi.org/geologicAgeVocabulary">Triassic <value codeSpace="http://www.iugs- cgi.org/geologicAgeEventVocabulary">intrusion physical model: GML-XML conceptual model: no GML GeoSciML 1.1 Progress to date

12. Use-case 1: query feature  Query one map feature (e.g. a geologic unit) and return GeoSciML Testbed results

13. Use-case 2: download features  Download map features in view as GeoSciML Testbed results

14. Use-case 3: re-classify features  Use standard legend (symbols, terms) for rock types and ages Testbed results

15. GML Client Community interoperability WMS WFS WMS WFS WMS WFS WMS WFS WMS WFS WMS WFS USGS schema BRGM schema GSC schema BGS schema SGU schema GA schema GeoSciML GA Oracle, ESRI SGU BGS BRGM USGS ESRI GSC Oracle, ESRI

16. systems syntax schematic semantic interoperability GeoSciML (data structure) GeoOntology (data content, classifications and vocabularies) Geoscience GML (data syntax) WFS, WMS, WCS, … (data systems) OGC Geospatial interoperability stack Schematic and semantic interoperability in OGC framework:

17. Inclusive process IUGS Mandate “Regular” meetings  Edinburgh, 2003  Ottawa, Perth, 2004  Ottawa, 2005  Orleans, Bruxelles, 2006 New participants added  GA, BRGM, SGU in 2006 Web collaboration tools Interoperability Testbeds  includes COTS software  industry partnerships

18. Status and future plans GeoSciML v1.1 – for 2006 testbed GeoSciML v2.0 – work already commenced Documentation – 2006/07  will include conformance tests to assist procurement guidelines, and as guide to software developers  to be submitted for formal adoption by IUGS Vocabulary standardization  GeoSciML provides “structural” information model to house information  for full interoperability, property value-spaces must also be harmonized Portals and Registries  support discovery, service-chain composition https://www.seegrid.csiro.au/twiki/bin/view/CGIModel/GeoSciML

19. GeoSciML design team Boyan Brodaric, Eric Boisvert – GSC Steve Richard – Arizona GS Bruce Johnson – USGS John Laxton, Tim Duffy, Marcus Sen – BGS Bruce Simons, Alistair Ritchie – GSVic Ollie Raymond, Lesley Wyborn – GA Simon Cox – CSIRO + for testbed: Dale Percival – GA, Joost Van Ulden – GSC Francois Robida, Jean-Jacques Serrano, Christian Bellier, Dominique Janjou – BRGM Lars Stolen, Jonas Holmberg, Thomas Lundberg – SGU

20. www.csiro.au Thank You CSIRO Exploration and Mining NameSimon Cox TitleResearch Scientist Phone+61 8 6436 8639 EmailSimon.Cox@csiro.au Webwww.seegrid.csiro.au