1. Implementing distributed geoscience information systems using Open GIS Web Services Simon Cox CSIRO Exploration & Mining http://www.em.csiro.au

2. 30/06/2016 2 Outline  Information Services  Information Communities  XML for geoscience  Service chains

3. Information Services HTTP is a lot more than web-pages

4. 30/06/2016 4 Evolution of web-page delivery  Static webpages  http://my.big.org/people/fred.html  URL maps to disk-file  Dynamically generated webpages  http://my.big.org/catalogue?item=358  URL maps to a local procedure call  Each site encodes query differently  unique UI  Result only accessible to humans

5. 30/06/2016 5 Web services  Information services  XML(?) packets of re-usable data  minimal latency  Computational services  bigger parameter set  latency acceptable  Federated databases  Service chains?

6. 30/06/2016 6  Open GIS® Consortium & ISO/TC 211  Information models and service interfaces  Service implemented as a set of request-response message pairs  Fine-grained  Spatial Data Infrastructures Web Feature Service Standards for geospatial data

7. 30/06/2016 7 WFS in detail …  Standard request syntax:  e.g. GetFeature  Standard response:  FeatureCollection encoded using a GML application language http://wfs.my.big.org& SERVICE=WFS& VERSION=1.0.0& REQUEST=GetFeature& PROPERTYNAME=xmml:collarLocation,xmml:logs& TYPENAME=xmml:Borehole& BBOX=135.1,-34.0,135.2,-33.9 … … …

8. 30/06/2016 8 Private vs. public schemas  WFS is a façade to a DB or GIS WFS Client WFS Server  Data-store organised for custodian’s requirements  esp. maintenance  Published view should match community expectation

9. Information Communities Meaningful discourse requires shared information models

10. 30/06/2016 10 Information model  Basic feature model  to be extended for specific applications  class name = feature-type  borehole  mineral occurrence  gravity measurement  fault  attribute & association names = properties of this feature-type

11. 30/06/2016 11 Information transport  Serialised form  Based on Geography Markup Language  element name == feature-type  content == properties of this feature-type  GML is required for WFS compatibility Exploration hole north_r_679... 0.15 Lithology log … <xmml:categoryList property="#lith" codeSpace="#unitcodes“> CANIS FH PL2 PL3 AQ AQL T1 T2 C1 C2 GCWS...

12. 30/06/2016 12 Geography Markup Language  GML 3.0 provides:  Geometry/topology temporal coordinate reference systems (ISO 19107, 19108, 19111)  Coverages & grids (ISO 19123), Observations, Dynamic features, Definitions, Units of measure, essential basic datatypes

13. 30/06/2016 13  2 aspects to be defined:  The principle elements - in a “Feature-type catalogue”  formalise using XML Schema  based on GML to ensure WFS compatibility  Vocabularies of valid property values – several methods  enumerations in XML Schema  allows validation, but not extensible  URL instances: e.g.  http://my.big.org/classifications/lithology/komatiite http://my.big.org/classifications/lithology/komatiite  http://my.big.org/classifications/lithology/greywacke http://my.big.org/classifications/lithology/greywacke  offline … Implementing a community language

14. eXploration & Mining Markup Language Standards-based language for earth sciences information

15. 30/06/2016 15 XMML Feature Catalogue  Borehole  Observation (OGC SensorWeb)  Gravity measurement (GA)  Geochemistry/Assay result (ADX)  Geological material (NORTON)  Geological timescale (IUGS)  Mineral occurrence (GA)  Procedure, Project, Station, Specimen, Tenement, Instrument (GGIPAC, etc)  Point, Curve, Surface, Solid with properties (Fractal)  Time-series (ASEG)  Structural geology elements  Mine components?  Finite element model (FLAC, FastFlo)  Simulation/model state (pmd*CRC)  [General “coverage”, including tensor fields, directly from GML]

16. 30/06/2016 16 Design method  Iterate between XML instances, XML Schema, UML model, harmonising with current state of suite of schemas  Adapt existing standard  e.g. GGIPAC, ASEG  Private model from dominant data provider  e.g. Geoscience Australia  Sponsor requirements  e.g. Fractal Technologies, CSIRO/pmd*CRC, BGS, Snowdens/WMC/Newmont  Consultation with stakeholders  TWiki

17. 30/06/2016 17

18. 30/06/2016 18 Deployment requirements  Develop GML Application Language  serialisation of community information model  WFS server-side software  Easy to configure mapping from private to public data models  Client applications  desktop software must have WFS client back-end  applets in standard portals  Middleware  data-source catalogues, service registries, brokering

19. 30/06/2016 19  Common encoding == interoperability within the community WFS Client (e.g. visualisation) WFS Server WFS Client (data mining) WFS Client/ Server WFS Client (simulation) WFS Server Sensor Use community standards at the interface

20. 30/06/2016 20 Project schedule  Commenced at CSIRO 2000  Sponsors joined progressively  MERIWA funded phase concluded June 2003  Extensions through GGIPAC, pmd*CRC, AcQuire  Maintenance  OGC schema repository  OGC RFC late 2003  Geoscience Australia, British Geological Survey, BRGM?  Submit to IUGS mid 2004