© MarineXML 2005 Slide 1 of 19 Geospatial Standards for Earth System Science Data Edinburgh,...

Geospatial Standards for Earth System Science DataEdinburgh, Scotland, 6th-8th September 2005

© MarineXML 2005 Slide 1 of 19

MarineXML & MOTIIVE

Keiran Millard



Scope• MarineXML initiative• INSPIRE, GMES and global services

– What is INSPIRE hoping to do?

• Marine community and interoperability– What standards are in place– Open source standards

• MOTIIVE– Tangiable steps to using OGC specifications

for marine/coastal data exchange



MarineXML initiaitives

IOC/ICES Study Group

National Marine Data Centres

EU MarineXML

National Marine Data CentresPrivate companies

Research OrganisationsGovernment Agencies

MarineXML.net

IODE

EU Motiive

Private companiesResearch OrganisationsGovernment Agencies



User Context

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



Summary of Issues

• INSPIRE implementation (presently) raises more questions than it answers

• Unclear how (or if) realtime applications benefit from INSPIRE – WMO/JCOMM

• Unclear how GMES Services make use of INSPIRE and the benefits delivered

• MOTIIVE is set-up to solve these issues



Standards and Met/Ocean data• IOC and 19110/19136

– MarineXML• IHO and 19110 (‘Navigation GML’)

– GML encoding of S-57 v3.1 & S-57 v4• IOC and IHO

– Collaboration intent of wider deployment of ‘Marine Feature Catalogue’ (IOC/IODE XVIII, 2005)

• WMO and 19110/5– COST-719 & WMO 19115 Core Profile

• NDG/SEEGrid and 19110/19136 (‘Science GML’)– NDG/SEEGrid is informing GML development– Climate Science Mark-Up Language (CSML)



Interoperability• Where does it need to happen?

– Level of processing (measurement, data, product)– Between which organisations/communities?– Closed v open

• Standards promote interoperability (ISO/OGC)– Standards framework is always a good place to start

to realise interoperability.– “Interoperability provides the freedom to mix and

match information system components without compromising overall success” ISO 19101: Geographic information Reference model

• Therefore there is a (business) test for what level of interoperability works



GOOSGOOS

WMOWMO

Interoperability in the Marine Community

Met

MetMet

Met

Ocean

Ocean

Ocean

SciencePhysicalChemical

Biological

Navigation

Dredging & Extraction

Conservation

FisheriesAquaculture

Water Quality

Energy

ForecastsHindcasts

Closed interoperability in communities are optimised for operations. Open interoperability needed when exchanging outside of communities (optimised for exchange)



Feature Types• Feature Types (ISO 19110) are the primary

language component for a spatial community to define real world phenomena.

• Although ISO19136 provides a route for the encoding of Feature Types in XML, it does not provide a route-map for defining the features themselves.

• The level of granularity for Feature Types has to be based on the governance model. If no-one is prepared to put in place a process to define semantics, interoperability has reached its limits.



MarineXML & Feature Catalogues

Physical - Chemical - Biological

• There is no single ‘Marine Feature Type’. – Given the diversity of the marine community, what is

needed is a mechanism to represent what needs to be exchanged

• Different sub-communities take responsibility for their feature types. – It becomes wholly impractical for any single organisation,

such as IOC, to manage and maintain all the Feature Types that the marine community could require.

– Different parts and operations of the marine community need to subscribe to their own data standards as these are integral to their operations.



Strong & Weak Feature Types• Weaker:

– Greater flexibility so that we can accommodate a large a number of features via the use of different domain vocabularies to specify types.

– There is less control by the feature type specification, thus less conformance checking at that level.

– The user is “on their own” to detail the specifics of the features which they need to use.

– A smaller, less detailed specification, providing a framework.• Stronger

– The approach is more rigid, so that it becomes harder to accommodate new features.

– There is more control in the structural checking– More aid can be given to the user on the choice of feature type.– A larger more detailed specification is given, providing much more

data



Strong & Weak Feature Types

Features

Strong ‘Physical’

Weak ‘Data’

Gridded data of bathymetry

Bathymetry for

navigation

Community Domains



Feature Types defined by CSML

Includes wrapper for NetCDF, GRIB, NASAAmes

Seven Feature Types

CSML feature type principles:•offload semantics onto parameter type•offload semantics onto CRS•‘sensible plotting’ as useful discriminant



XM

L P

arser

SeeMyDENC

Data Dictionary

S52 Portrayal Library

SENC

MarineGML

(NDG) Feature

Types

XML

XML

XML

Biological Species

Chl-a from Satellite

ModelledHydrodynamics

XSLT

XSLT

XSLT

For each XSD (for the source data) there is an

XSLT to translate the data to the Feature

Types (FT) defined by CSML. The FT’s and

XSLT are maintained in a ‘MarineXML registry’ The FTs can then

be translated to equivalent FTs for

display in the ECDIS system

XSLT

Features in the source XSD must be present in

the data dictionary.

XSD

XSD

XSD

XML

XML

The result of the translation is an encoding that contains the

marine data in weakly typed (i.e. generic) Features

XSLT

XSLT

Phenomena in the XSD must have an associated

portrayal

ECDIS acts as an example client for

the data.

Data from different parts of the marine

community conforming to a variety of schema

(XSD)

MeasuredHydrodynamics

S-57v3 GML

XML

XSD

XML

XSD

Feature described using S-57v3.1Application

Schema can be imported and are equivalent to the same features in CSML’



Biological sampling station with attributes for the species sampled at each

Grid of Chl-a from the MERIS instrument on ENVISAT

Predicted and measured wave climate timeseries (height, direction and period)

Vectors of currents from instruments

MarineXML Testbed



The Concept of re-using Features

Here structured XML is converted to plain ascii text in the form required for a numerical model

HTML warning service pages are generated ‘on the fly’XML can also be converted to SVG to display data graphically

Here the same XML is converted to the SENC format used in a proprietary tool for viewing electronic navigation charts.

New opportunities through OGC standards (WxS) to provided bespoke geo-information products by combing data from different sources.

All this requires agreement on standards



WMS for Hydrolographic Data

WFS for S-57 3.1 data produced by UHKO / Galdos.



MOTIIVE

Physical - Chemical - Biological

• (How to) Implement of OGC services in the marine domain– ‘Ocean Features’ with ‘Elevation’– Based on the ‘building blocks’ presented here

• Cost:benefit of using open standards interoperability– Where is this postive/negative?

• Registry infrastructure for standards and servcies– IHO & IOC

• Due to start…NOW!– Links with RISE



Conclusions• Significant contribution internationally to the

development and trialling of standards framework for met/ocean data

• A “pre-standardisation level” has been established for using XML for marine data exchange based on IS019000 standards– IHO and IOC Plans

• Met/ocean community is informing ISO developments– ISO 19111 (Spatial referencing by coordinates) –

proposal for ‘parametric’ vertical datum actively being pursued.



Conclusions

• Marine community cannot be served by a single Feature Catalogue– Ontology to map features to catalogues – Evolutionary process

• Test-bed phase demonstrated one Feature Type Catalogue for general purpose data interchange– Now released as CSML– Proof of concept for interoperability with S-57

• IODE to continue ‘MarineXML’ steering role• MOTIIVE – INSPIRE pilot project, and follow-on

from MarineXML

tkm

Andrew, is there something particular you would like to add about this?



Working with MarineXMLIf you would like to support the development of

MarineXML, please go to the IOC interoperability website.

www.marineXML.net

or

www.motiive.net

The findings from the EU MarineXML project now form the basis of the EU project Motiive that looks at open standards for the

development of INSPIRE and GMES. Motiive is undertaken under the auspices of IOC’s MarineXML initiative

© MarineXML 2005 Slide 1 of 19 Geospatial Standards for Earth System Science Data Edinburgh,...

Documents

Transcript of © MarineXML 2005 Slide 1 of 19 Geospatial Standards for Earth System Science Data Edinburgh,...