Transcript Contribution to GEOSS AIP-3: GIGAS data interoperability Andrew Woolf (1), Simon Cox (2), Clemens Portele (3) (1) STFC Rutherford Appleton Laboratory (2) European Commission,

Contribution to GEOSS AIP-3:
GIGAS data interoperability
Andrew Woolf (1), Simon Cox (2), Clemens Portele (3)
(1) STFC Rutherford Appleton Laboratory
(2) European Commission, Joint Research Centre
(3) interactive instruments
GIGAS Final Review – 15.07.2010 – Brussels
Outline
GEOSS AIP-3
Target scenario
A harmonised model
Interoperability components
Open issues
GIGAS Final Review – 15.07.2010 – Brussels
GEOSS AIP-3
‘Architecture Interoperability Pilot’ Phase Three
March 2010 (kickoff) – Dec 2010 (final results)
Extends past GIGAS project end
Call for Participation topics:
Societal Benefit Area Alignment and Support
Component and Service Contributions
Architecture and Interoperability Arrangement Development
GIGAS contribution on Interoperability Arrangements:
Investigate a ‘Common Foundation’ between GEOSS and INSPIRE
Reconcile GEOSS ‘geophysical observations’ with INSPIRE ‘features view’
Identified as the first of seven interoperability opportunities, D2.3b
Contributors (Cox, Portele, Woolf) supporting the work beyond GIGAS
GIGAS Final Review – 15.07.2010 – Brussels
Target scenario
For a concrete use case, we adopt the GMES MyOcean scenario
In-situ (e.g. temperature, salinity) plus satellite observations (e.g. seasurface dynamic height)...
Often regarded as ‘geophysical observations’
...assimilated in a numerical model to produce analysis/forecast fields
Typically, large gridded (coverage) fields
Can the INSPIRE ‘feature-based’ framework apply to all these?
Aim to reconcile
these different views
AIP-3 Information Viewpoint
GIGAS Final Review – 15.07.2010 – Brussels
GEOSS – INSPIRE mapping
In reconciling the INSPIRE
GEOSS SBA
INSPIRE Annex theme
Disasters
Natural risk zones
approach with GEOSS
Health
‘geophysical observations’, it is
Human health and safety
Population distribution – demography
Energy
Energy resources
Climate
Atmospheric conditions
Agriculture
Land cover
Soil
Land use
Agricultural and aquaculture facilities
Ecosystems
Protected sites
Habitats and biotopes
Biodiversity
Bio-geographical regions
Species distribution
Water
Hydrography
Oceanographic geographical features
Utility and governmental services
Production and industrial facilities
Weather
Meteorological geographical features
interesting to map between the
GEOSS Societal Benefit Areas
and INSPIRE Annex themes
Good coverage of GEOSS SBAs in
INSPIRE
Cross-cutting themes include:
Elevation, Orthoimagery,
Environmental Monitoring Facilities
GIGAS Final Review – 15.07.2010 – Brussels
A harmonised model
Models of geographic information:
INSPIRE: adopts ‘feature-based’ view
GEOSS: geophysical observations / ‘coverage’ view
Both viewpoints valid
class Figure 2 - GFM - properties
Name:
Package:
Version:
Author:
class Figure 3 - Abstract cov erage
Figure 2 - GFM - properties
AIP-3
1.0
Simon Cox
«metaclass»
GF_FeatureType
+carrierOfCharacteristics
Name:
Package:
Version:
Author:
1
0..*
Figure 3 - Abstract coverage
AIP-3
1.0
Simon Cox
«metaclass»
GF_PropertyType
{root}
+
+
memberName
definition
CV_Coverage
+
+
+
domainExtent: EX_Extent [1..*]
rangeType: RecordType
commonPointRule: CV_CommonPointRule
+
+
+
+
+
evaluate(DirectPosition*, Sequence<CharacterString>*) : Record
evaluateInverse(Record*) : Set<CV_DomainObject>
find(DirectPosition*, Integer*) : Sequence<CV_GeometryValuePair>
list() : Set<CV_GeometryValuePair>
select(GM_Object*, TM_Period*) : Set<CV_GeometryValuePair>
+characterize 0..1
«metaclass»
GF_Operation
+
signature
+affectsValuesOf
0..*
0..*
0..*
+observesValuesOf
0..*
+triggeredByValuesOf +
0..* +
0..* +
«metaclass»
GF_AttributeType
AttributeOfAttribute
«metaclass»
GF_AssociationRole
+characterizeBy 0..*
valueType
valueDomain
cardinality
+
+
+collection
Domain
+domainElement
1..*
valueType
cardinality
+collection
Range
+rangeElement 0..*
CV_DomainObj ect
CV_AttributeValues
+
TemporalComposition
«metaclass»
GF_LocationalAttributeType
{leaf}
«metaclass»
GF_TemporalAttributeType
«metaclass»
GF_ThematicAttributeType
{leaf}
«metaclass»
GF_MetaDataAttributeType
0..*
+temporalElement
TM_Primitive
TM_GeometricPrimitiv e
«metaclass»
GF_SpatialAttributeType
{leaf}
+spatialElement
0..*
GM_Object
{root}
«metaclass»
GF_QualityAttributeType
{leaf}
‘General Feature Model’ (ISO 19109)
GIGAS Final Review – 15.07.2010 – Brussels
SpatialComposition
‘Coverage Model’ (ISO 19123)
values: Record
A harmonised model
There is considerable confusion in the community over the respective
roles of ‘features’ and ‘coverages’ in geospatial data modelling
Arises from the traditional GIS view of data as either ‘vector’ or ‘raster’
‘feature-based’ models are often (wrongly) equated with ‘vector’
(features may have coverage-valued properties)
‘coverage-based’ models are often (wrongly) equated with ‘raster’
(coverages are not defined only on grids)
In fact, there is no dichotomy, but there is a need for material which
clarifies the relationships
This GIGAS contribution attempts to fill the gap
GIGAS Final Review – 15.07.2010 – Brussels
A harmonised model
Numerous possible relationships
between features and coverages:
Coverage as a feature property
E.g. ‘the ocean’ has a property
‘temperature’ that varies in space
and time
Feature detection
E.g. identifying fronts and eddies
from gradients in temperature field
Coverages and sets of features
E.g. sets of temperature
measurements provide a discrete
point coverage
GIGAS Final Review – 15.07.2010 – Brussels
(From data.ncof.co.uk)
A harmonised model
ISO 19156 (‘Observations and Measurements’)
Ref. GIGAS recommendations (D3.3b)
An observation is an event that estimates an observed property of a
feature of interest, using a procedure, and generating a result
Sometimes ‘observed property’ and ‘feature of interest’ are conflated in
describing geophysical parameters (e.g. sea surface temperature)
class Figure 5 - Observ ation
Name:
Package:
Version:
Author:
Figure 5 - Observation
AIP-3
1.0
Simon Cox
GFI_Feature
OM_Process
+featureOfInterest
1
1
0..*
OM_Observation
+
+
+
+
+
phenomenonTime
resultTime
validTime [0..1]
resultQuality [0..*]
parameter [0..*]
1
Range
+observedProperty
GFI_PropertyType
+procedure
+generatedObservation
0..*
+propertyValueProvider
+result
Any
{root}
GIGAS Final Review – 15.07.2010 – Brussels
A harmonised model
Sampling
Often a sampling strategy is used to measure properties of a feature
In this case the feature of interest is a ‘sampling feature’
Directly related to the corresponding observations
class Figure 6 - Sampling
Name:
Package:
Version:
Author:
class Figure 7 - Sampling Manifold examples
Figure 6 - Sampling
AIP-3
1.0
Simon Cox
Name:
Package:
Version:
Author:
Figure 7 - Sampling Manifold examples
AIP-3
1.0
Simon Cox
SF_SpatialSamplingFeature
SamplingFeatureComplex
+
+relatedObservation
OM_Observ ation
role
SF_Process
0..*
Design
0..* +processingDetails
+relatedSamplingFeature 0..*
SF_SamplingCurv e
SF_SamplingPoint
SF_SamplingSurface
SF_SamplingSolid
SF_SamplingFeature 0..*
GFI_Feature
SF_Specimen
+
+
+
+
+
+sampledFeature
Intention
1..*
SF_SpatialSamplingFeature
+
materialClass
samplingTime
samplingMethod [0..1]
currentLocation [0..1]
specimenType [0..1]
Station
Traj ectory
Borehole
«estimatedProperty»
+ samplingLocation [0..1]
+ size [0..1]
positionalAccuracy [0..2]
Geometry
+shape
GM_Point
SF_SamplingCurv e
Geometry
+shape
GM_Curv e
SF_SamplingSurface
Geometry
+shape
GM_Surface
GIGAS Final Review – 15.07.2010 – Brussels
SF_SamplingSolid
Profile
Flightline
Trav erse
Geometry
+shape
GM_Solid
Scene
Observ ationWell
ShipsTrack
SF_SamplingPoint
Quadrat
Interv al
Sw ath
MineLev el
MapHorizon
Section
Mine
LidarCloud
A harmonised model
Bringing it together: ‘Sampling Coverage Observations’
Feature of interest is a ‘Sampling Feature’
Observation result is a ‘Coverage’
Reconciles features ↔ observations ↔ coverages
Ocean
sampled
feature
observed
property
SF_SamplingSurface
related
observation
feature of
interest
Sampling
Coverage
Observation
procedure
GIGAS Final Review – 15.07.2010 – Brussels
result
Interoperability components
GIGAS identified a number of interoperability components which must
be taken into account, e.g.:
application schemas
spatial and temporal aspects
governance
Controlled vocabularies are particularly important
require registers of terms
observed property
units of measure
GIGAS Final Review – 15.07.2010 – Brussels
Open issues
Many geophysical observations vary over space and time
Coverage domain must be a spatiotemporal geometry (ISO 19107:
spatial; ISO 19108: temporal)
Representation of coverage attribute in General Feature Model
Can use GF_ThematicAttributeType or GF_Operation, but might be better
to have a GF_CoverageAttributeType
Coverage encodings
Not normally encoded with GML (e.g. binary files – netCDF, TIFF, etc.)
Coverage types limited
ISO 19123 being revised; ‘minimal core’ may be best, with domainspecific extensions
GIGAS Final Review – 15.07.2010 – Brussels
Links to targeted Initiatives, Organisations and Projects:
The GIGAS Consortium
GIGAS Final Review – 15.07.2010 – Brussels