motiive:rise harmonisation advisory committee and project board

MOTIIVE : RISE HAC-PBEC, Brussels, 6th June 2007

© MarineXML 2006 Slide 1 of 16

MOTIIVE:RISEHarmonisation Advisory Committee and

Project BoardEuropean Commission

Brussels, BE 6th June 2007

Keiran Millard, HR Wallingford

Roger Longhorn, IDG



What is Motiive About• Premise (of call)

– GMES Service will be more cost-effective to deploy through the use and adoption of OGC/ISO Interoperability standards

– This interoperability will entail true ‘mix and match’ between (and amongst) ‘core’ and ‘downstream’ data processors.

• Scope (of Motiive)– How do you apply ISO/OGC Standards to the

coastal/marine community• Land:sea interaction (Marine Overlays on Topology)

– What do the standards look like and how does a ‘cost benefit’ manifest itself

– Work with RISE



Project Update• What is Motiive about?

– GMES and INSPIRE Context– ISO and OGC Standards

• What has Motiive achieved?– Community needs for harmonisation (need for FT and FTC)– Community Feature Types (published as UML and XSD)– FTC implementation (base catalogue services in place)– Cost-Benefit methodology

• Motiive, INSPIRE and OGC– Earth science perspective on Inspire– A catalogue for the Themes to lodge their FT’s

• What does Motiive still need to do? (Sept 2007)– Finalisation of catalogue deployment (ebRIM packges)– Submit FT specification as OGC Recommendation



Motiive Use CaseJane is contributing to the development of an integrated coastal management plan and needs access to a range of data concerning conditions in the littoral zone and offshore. Jane’s current concern is to investigate sediment transport and coastal erosion in the UK’s Thames estuary. Jane is working in an era of a harmonised spatial data infrastructure and is able to access on-demand a range of data across the internet.

Jane wishes to evaluate a variety of tidal models available to her by validating against historical tide gauge measurements. Helga (NO) and Willem (NL) both run tidal models and wish to make their datasets available for re-use – they employ standards-based interoperable web services for this purpose, and these are amongst the datasets available to Jane for evaluation.

Data from the selected model is used to generate plots of current and other tidal parameters. None of the data suppliers provide dedicated portrayal services for their data, but a third-party portrayal service is available for a range of compatible ‘base’ feature types. Moreover, another service provides feature-type transformation (defined as an operation on the source feature type) to facilitate direct model-observation inter-comparison.

Generic community needs to use data in a unambiguous way

Clear definitions of what data sets ‘are’

=>Clear declaration of Feature Types

Clear ‘use’ of datasets

=>Operations on Feature Types (binding to services)



View Feature Type

Motiive_WLdescription of Motiive_WL moreview services view parents

View FT parents, i.e. this page, but up one level in hierarchy

Search Results (for Water Level from 19115 catalogue)

Water Level – NERSC19115 description of the data available moreFT: Motiive_ModelGrid query get

Water Level – ARGOSS19115 description of the data available moreFT: Motiive_ModelGrid query get

Water Level – HRW19115 description of the data available moreFT: Motiive_Instrument query get

Query Feature Type

Motiive_ModelGriddescription of MotiiveGrid moreview services view parents

Get Feature Instance

DAQM_Motiive_WLFielded data query, including selection of services to be invoked e.g. visualisation. Assume also need to fill slots for the service

Invoke query

List of services afforded by the FT

Display Results return



ISO Scope• ISO 19101 introduces the Domain Reference

Model – an abstract information architecture for geospatial data infrastructures.

• At the core of the model is a geospatial Dataset. A Dataset contains Feature instances and related objects, and is described by Metadata.

• Feature type definitions may be stored for re-use in feature catalogues (ISO 19110).

• Geographic information services operate on a Dataset, while the logical structure and semantic content of a Dataset is described through an Application schema



What Motiive as done• Motiive has worked with RISE on a methodology for

developing a Data Product Specification (RISE Lead)• MOTIIVE followed this methodology and as output from

this process:– Established our community needs for data harmonisation– Formalised our community needs as use cases– Modelled our community Feature Types and realised them

as GML application schema– Established a Feature Type Catalogue to lodge the Feature

Types Established• The approach we followed will be useful to any

community where the datasets exchanged amongst and between members are inherently based on ‘representation on environmental phenomena’– water quality, air temperature, water flows ETC.



Community Harmonisation Needs• Coastal Managers (D7b)

– Mainly regional/national managers– Seamless Discovery of data sets– Seamless Use

• Meteorological (D9b)– WMO / UK Met Office– (flexible) chaining of services– Maintaining access to legacy data

• Integrated Coastal Mapping (D7a)– UKHO / IHO– Common definitions of ‘features’– Greater ‘quality assurance to a DPS’

• GSE– Marcoast – (flexible) chaining of services – Maintaining access to legacy data



GMES Service ‘Pyramid’

Data DataData Data

Hydrodynamics

WaterQuality

Component

ComponentComponent

Component

EO In-situ

Data Data

Model

ICZMR Customer

base

WFD Customer

baseHydrodynamic Data

(nowcasts, forecasts, hindcasts)Data

Typology Map

SustainabilityIndicators

Sediment Cell

Mapping

Shoreline Impact

Topography

WQ Indicators

Navigation Customer

Base

Component

NavigationCharts



Community Harmonisation Needs• Coastal Managers (D7b)

– Mainly regional/national managers– Seamless Discovery of data sets Feature Types– Seamless Use Feature Catalogue

• Meteorological (D9b)– WMO / UK Met Office – (flexible) chaining of services Feature Catalogue– Maintaining access to legacy data

• Integrated Coastal Mapping (D7a)– UKHO / IHO– Common definitions of ‘features’ Feature Catalogue– Greater ‘quality assurance to a DPS’

• GSE– Marcoast – (flexible) chaining of services Feature Catalogue– Maintaining access to legacy data



Community Feature Types

• Feature Types for ‘Environmental Observations’ – rather that ‘environmental constructions’

• CSML (Climate Science Modelling Language)– Feature types and storage descriptors

• Consistent with community practice– ESRI, UniData, NOAA



CSML FeaturesCSML feature type Description Examples

TrajectoryFeature Discrete path in time and space of a platform or instrument.

ship’s cruise track, aircraft’s flight path

PointFeature Single point measurement. raingauge measurement

ProfileFeatureSingle ‘profile’ of some parameter along a directed line in space.

wind sounding, XBT, CTD, radiosonde

GridFeature Single time-snapshot of a gridded field. gridded analysis field

PointSeriesFeature Series of single datum measurements.

tidegauge, rainfall timeseries

ProfileSeriesFeature Series of profile-type measurements.

vertical or scanning radar, shipborne ADCP, thermistor chain timeseries

GridSeriesFeature Timeseries of gridded parameter fields.

numerical weather prediction model, ocean general circulation model

Presently in Release 2



CSML Featurescd GridSeriesFeature

Cov erage Types::GridSeriesCov erage

+/ domainSet: GridSeriesDomain+/ rangeSet: Record [0..*]

CV_DiscreteCoverage

Discrete Cov erages::CV_DiscreteGridPointCov erage

+ find(DirectPosition*, Integer*) : Sequence<CV_GridPointValuePair>+ list() : Set<CV_GridPointValuePair>+ locate(DirectPosition*) : Set<CV_GridPointValuePair>+ point(CV_GridCoordinate*) : CV_GridPointValuePair

«FeatureType»GridSeriesFeature

AnyDefinition

«ObjectType»phenomenon::Phenomenon

ReferenceableGrid

«ObjectType»Domain geometries::

GridSeriesDomain

«type»Affordance::GridSeriesType

+ value: GridSeriesCoverage

+ extactPointCollection() : PointCollectionFeature+ extractGridFeature() : GridFeature+ extractGridSeriesFeature() : PointSeriesFeature+ extractPointFeature() : PointFeature+ extractPointSeriesFeature() : PointSeriesFeature+ extractProfileFeature() : Profi leFeature+ extractProfileSeriesFeature() : Profi leSeriesFeature+ extractSection() : SectionFeature

«realize»

+parameter

+value

«implement»

INSPIRE does not mandate operations for FTs – but most communities will require this



CSML Features

<Dataset>

</Dataset>

<csml:FeatureCollection>

</csml:FeatureCollection>

<csml:StorageDescriptor >

</csml:StorageDescriptor>

......

......

.....

......

......

.....

• Storage descriptors

In line XML or by reference to external storage, e.g. NetCDF, Grib



Feature Type Catalogues• Feature type definitions may be stored

for re-use in catalogues (ISO 19110). • Since features encapsulate important

data semantics within communities of practice.– Feature Type Catalogues may be

regarded as ‘semantics repositories’ within an overall information architecture.



Feature Type Cataloguecd Data Model

«FeatureType»CSML_PointSeries

- Operations: DAQM

«FeatureType»CSML_GridSeries

- Operations: DAQM

«FeatureType»WL_PointSeries

«FeatureType»Instrument_PointSeries

- SamplingFrequency: int

«FeatureType»Model_GridSeries

- IssueTime: float

GML

Instrument community

Numerical modelling community

Tidal Community (e.g. IHO)

Serv ices

«bind»

Semantics can be inherited from other communities –or from within your own. Plus the services that go with it



Feature Type Catalogue

Our analysis suggests that compliance to A.25 level is needed

ISO 19110 (211n2053 revision)



PostGresDatabase

WFS

Catalogue Browser

Client Application

Client Interface

water level time series

AnotherDatabase

AnotherDatabase

WCS WCS

water level grid Model#1

water level grid Model#2

Catalogue- Features

- Data

Third Party Viewer

Motiive test deployment



Feature Type Cataloguedd

Feature Type Catalogue

LisaSoft

CubeWerx

Web Registry Serv ice

Catalogue Serv ices

«document»

EbRIM Package

Interface

Present activities are defining ebRIM package

FTC BrowserProvides a way to view the FT's

Specialise

Motiive implementation of a web enabled FTC



Deployment Pieces• FTC (completed)

– Subcontract let to LisaSoft– WRS and Cat Services installed and tested– Prototype FTC browser

• FTC (to do)– ebRIM 19110 package implementation– Service binding to realise feature instances– Finalise FTC browser

• End of September is likely date for completion



Motiive and INSPIRE• Experience from Motiive submitted to the

INSPIRE Drafting Teams– Via calls for comment on Data Product Specification

guidance

• Ensuring needs of ‘Earth Science’ communities are represented– “Feature types for observations”

• Reference of Feature Type Catalogues– Feature Types will be defined for each of the INSPIRE

Themes.– Need a catalogue to put them in that is search able

amongst and between communities



Motiive and OGC

• Working closely to take things forward post-project

• Plan to submit FTC as a Recommendation to OGC

• Change requests to OGC for – Query model– Irregular grids in GML (ISO 19123)

• Non-quadrilateral grids?

motiive:rise harmonisation advisory committee and project board

Documents