www.csiro.au introduction to geosciml: standard encoding for transfer of geoscience information...
Post on 13-Dec-2015
219 Views
Preview:
TRANSCRIPT
www.csiro.au
Introduction to GeoSciML: standard encoding for transfer of geoscience information
Simon Cox
CSIRO Exploration and Mining
11 September 2006
Canada USA UK France
Germany
Korea
Japan
Denmark
Sweden
Finland
Netherlands Australia Poland Czech
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
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
WMSWFS
WMSWFS
WMSWFS
WMSWFS
WMSWFS
USGS
schema
BRGM
schema
GSC
schema
BGS
schema
SGU
schema
GA
schema
GeoSciML
GeoSciML
GeoSciML
GeoSciML
GeoSciML
GeoSciML
GAOracle, ESRI
SGU
BGS
BRGM
USGSESRI
GSCOracle,
ESRI
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
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
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
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
Example feature-type
<sa:Specimen gml:id="sp1" … >
<gml:description>Specimen test instance</gml:description>
<gml:name>Specimen test 1</gml:name>
<sa:location> … </sa:location>
<sa:sampledOn xlink:href="http://my.big.org/station/st13"/>
<sa:sampleTime ></gml:TimeInstant … /></sa:sampleTime >
<sa:material codeSpace=“urn:x-seegrid:lexicon:specimenType">chips</sa:material>
<sa:mass uom=“kg">0.35</sa:mass>
<sa:reportingSpecimen xlink:href="http://my.big.org/specimen/sp34"/>
<sa:processingStep> … </sa:processingStep>
<sa:processingStep xlink:href="http://my.big.org/pst/p98"/>
<sa:relatedObservation xlink:href="http://my.big.org/obs/m45"/>
</sa:Specimen>
Descriptions and occurrences
«FeatureType»GeologicFeature
+ age: GeologicAge [1..*]+ physicalProperty: CGI_PhysicalDescription [0..*]+ purpose: DescriptionPurpose = instance
«FeatureType»MappedFeature
«CodeList»DescriptionPurpose
+ definingNorm: + instance: + typicalNorm:
«FeatureType»SamplingFeature
+ responsible: CI_ResponsibleParty [0..1]
«Type»GM_Object
«FeatureType»GeologicUnit
«FeatureType»GeologicStructure
+ genesis: CGI_TermValue [0..1]
«ObjectType»ControlledConcept
+ preferredName: CharacterString
0..*
AlternativeClassification
+alternativeClassifier
0..*
+specification1
Description
+occurrence 0..*
0..*
PrimaryClassification
+classifier 1
+shape 1
+samplingFrame
1
Map polygon
Legend itemObservational setting
«DataType»CGI_TermValue
+ value: ScopedName
«DataType»CGI_TermRange
«DataType»CGI_NumericValue
+ minusDelta: Measure+ plusDelta: Measure+ principalValue: Measure
«DataType»CGI_Value
+ qualifier: ValueQualifierCode [0..1] = equalTo
«DataType»CGI_NumericRange
«DataType»CGI_PrimitiveValue
«DataType»CGI_Range
«Union»CGI_Term
+ range: CGI_TermRange+ value: CGI_TermValue
«Union»CGI_Numeric
+ range: CGI_NumericRange+ value: CGI_NumericValue
+upper 1 +lower 1
+lower 1+upper 1
+lower 1+upper
1
Descriptive values
e.g. “Usually 2mm to boulder-sized”
ScopedName = label + vocabulary reference Measure = number + uom
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
ChronostratigraphicUnit
BiostratigraphicUnitLithodemicUnit
LithostratigraphicUnit
AllostratigraphicUnit PedostratigraphicUnit
MagnetostratigraphicUnit
LithotectonicUnitPedoderm GeomorphologicUnit
GUPRelationRole
or
CompoundMaterial
GUPRelation
Proportion
GURole
GeologicUnitPart
<<IsA>>
0..*
2..n
0..*
2..n1..11..1
1..11..1
Rank
WeatheringCharacter
OutcropCharacter
GUGenesis
GeologicAge
Extent
Morphology
Color
MetamorphicGrade
GeologicUnit
<<IsA>>
0..10..1
0..10..1
0..10..1
0..*
2
0..*
2
0..*0..1
0..*0..1
1..11..1
0..10..1
0..*0..*
0..10..1
GeologicProcess
0..*
0..*
0..*
0..*
0..*
0..*
0..*
0..*
cd Unit
AbstractFeature
«FeatureType»CGI_Top::GeologicFeature
+ age: GeologicAge [1..*]+ purpose: DescriptionPurpose
«FeatureType»GeologicUnit
+ bodyMorphology: CGI_TermValue [1..*]+ exposureColor: CGI_TermValue [1..*]+ genesis: CGI_TermValue [1..*]+ grossChemistry: ChemicalCompositionClass+ outcropCharacter: CGI_TermValue [1..*]
«FeatureType»LithostratigraphicUnit
+ unitThickness: CGI_Numeric [1..*]+ beddingStyle: CGI_TermValue [1..*]+ beddingPattern: CGI_TermValue [1..*]+ beddingThickness: CGI_Value [1..*]
«FeatureType»LithodemicUnit
«FeatureType»LithologicUnit
+ rank: ScopedName+ weatheringCharacter: CGI_TermValue [1..*]+ structurePresent: CGI_TermValue [0..*]+ metamorphicGrade: CGI_Term [0..*]
logical model: GML-UML
<LithodemicUnit gml:id="GSV53"> <gml:description>Granite, syenite, volcanogenic sandstone, conglomerate, minor trachyte lava</gml:description> <gml:name>Mount Leinster Igneous Complex</gml:name> <purpose>typicalNorm</purpose> <age> <GeologicAge> <value> <CGI_TermRange> <lower> <CGI_TermValue> <value codeSpace="http://www.iugs- cgi.org/geologicAgeVocabulary">Triassic</value> </CGI_TermValue> </lower> <upper> <CGI_TermValue> <value codeSpace="http://www.iugs- cgi.org/geologicAgeVocabulary">Triassic</value> </CGI_TermValue> </upper> </CGI_TermRange> </value> <event> <CGI_TermValue> <value codeSpace="http://www.iugs- cgi.org/geologicAgeEventVocabulary">intrusion</value>physical model: GML-XML
conceptual model: no GML
GeoSciML 1.1
Progress to date
Use-case 1: query feature Query one map feature (e.g. a geologic unit) and return GeoSciML
Testbed results
Use-case 2: download features Download map features in view as GeoSciML
Testbed results
Use-case 3: re-classify features Use standard legend (symbols, terms) for rock types and ages
Testbed results
GML
Client
Community interoperability
WMS WFS
WMSWFS
WMSWFS
WMSWFS
WMSWFS
WMSWFS
USGS
schema
BRGM
schema
GSC
schema
BGS
schema
SGU
schema
GA
schema
GeoSciML
GeoSciML
GeoSciML
GeoSciML
GeoSciML
GeoSciML
GAOracle, ESRI
SGU
BGS
BRGM
USGSESRI
GSCOracle,
ESRI
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:
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
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
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
www.csiro.au
Thank You
CSIRO Exploration and Mining
Name Simon Cox
Title Research Scientist
Phone +61 8 6436 8639
Email Simon.Cox@csiro.au
Web www.seegrid.csiro.au
top related