Ocean Data Interoperability Platform (ODIP) ODIP Background and Prototype 1 development EGU 2014 – ESSI 2.5 Session – Vienna – Austria – 1 st May 2014 Proposal : Call: FP7-INFRASTRUCTURES INFSO Activity: INFRA – International co-operation with the USA on common e-infrastructure for scientific data Dick M.A. Schaap - MARIS ODIP Technical Coordinator ODIP 1 leader

ODIP Rationale A very wide range of oceanographic and marine data Collected by thousands of organisations around the world Using a wide array of instrumentation and platforms Very considerable costs (e.g. in Europe 1.4 Billion Euro per year) => capture once – use many times However there are barriers to re-use of data, such as different formats, practices, standards, … 2

ODIP Rationale Great progress is being made with developing and establishing well founded and structured ocean and marine data infrastructures in many regions worldwide, such as in Europe, the USA, and Australia Also at global level development of such e-infrastructures is promoted by international organisations and initiatives, such as UNESCO‘s Intergovernmental Oceanographic Commission (IOC) and GEO  Initiative for Ocean Data Interoperability Platform (ODIP) 3

ODIP Objectives To establish an EU/USA/Australia/IOC-IODE co- ordination platform to facilitate the development of interoperability between the regional ocean and marine data management infrastructures and towards global portals To demonstrate this co-ordination through the development of several joint EU-USA-Australia prototypes that would ensure persistent availability and effective sharing of data across scientific domains, organisations and national boundaries. 4

ODIP Stakeholders Europe: SeaDataNet 2, Eurofleets 2, JERICO, EMODnet, Geo-Seas, MyOcean USA: R2R, US NODC, US IOOS, UNIDATA Australia: IMOS, AODN Represented by: Europe: NERC-BGS/BODC, MARIS, OGS, IFREMER, HCMR, ENEA, ULG, CNR, RBINS-MUMM, TNO USA: SDSC, SIO, WHOI, UNIDATA, LDEO, NOAA US-IOOS, NOAA US-NODC, NOAA NGDC, FSU- COAPS Australia: UTAS, CSIRO, AIMS, AADC, RAN, GA 5

ODIP Approach Identify and bring together standards and best practices in marine data management in the regions Organise Workshops to present and discuss standards and best practices and to consider development of common standards and interoperability solutions Develop and implement a number of prototypes Dissemination and promotion of activities and results, as well as exploitation by uptake in regional systems 6

Selected ODIP Prototype projects ODIP 1: Establishing interoperability between SeaDataNet CDI, US NODC, and IMOS MCP Data Discovery and Access services, making use of a brokerage service, towards interacting with the IODE-ODP en GEOSS portals ODIP 2: Establishing deployment and interoperability between Cruise Summary reporting systems in Europe, US and Australia, making use of GeoNetWork, towards interacting with the POGO portal ODIP 3: Establishing a prototype for a Sensor Observation Service (SOS) and common O&M and SensorML profiles for selected sensors (SWE), installed at vessels and in real-time monitoring systems 7

ODIP Prototype 1 - context Marine Data Discovery & Access services: Europe: Common Data Index (CDI) service, operated by SeaDataNet USA: Data Discovery and Access service, operated by US NODC Australia: Data Discovery and Access service, operated by AODN Global Data Discovery & Access services: GEOSS portal IODE Ocean Data Portal (ODP) 8

Base services – analysis 9

Base services - analysis Comparable approaches US NODC most developed in types of exchange services SeaDataNet fully distributed AODN follows distributed model US NODC federated and central databases SeaDataNet only one with AAA services for data access Concept of Collections and Granules All able to share metadata and data links following common protocols (CS-W, REST, SOAP, WMS, WFS, ….) 10

Target services - analysis 11 GEOSS ODP

Data brokerage concept GEO-DAB 12

ODIP 1 – agreed approach Europe, USA and Australia agree to contribute to the global IODE Ocean Data Portal (ODP) and the GEOSS portal.  Making use of the GEO-DAB Brokerage Service that will harmonise the 3 regional services to a common level that can interact with IODE - ODP respectively GEOSS.  start at metadata level, but proceed with data access, including providing solutions for possible AAA systems  excellent synergy with GEOSS and wider EU - US cooperation (BCube) and long term perspective. 13

Possible ODIP 1 exchange set-up 14 Note: given protocols for exchange are possible examples!

ODIP 1 – Start with SeaDataNet Common Data Index (CDI) metadata at granule level is based upon ISO – 19139, is INSPIRE compliant, and makes use of SeaDataNet Controlled Vocabularies Present coverage: > 1.5 million CDI entries from > 90 connected data centres 15

ODIP 1 – SeaDataNet web service SeaDataNet has set-up a web service with collections of CDI metadata entries, following the CDI ISO19115 – Schema Collections made by aggregation on Discipline (SDN vocab P08), Data centre (SDN EDMO-code), and geometric type (point / track / surface) Circa 1.5 million CDI granules are resulting in circa 400 CDI collections, each with URL to CDI service for details REST web service (IP – IP protected) to provide these collections in XML cdi-aggr-seadatanet_v3.xml 16

ODIP 1 – GEOSS Brokerage service CNR is operating the GEO-DAB Brokerage Service It has harvested the SeaDataNet CDI collections and converted these to a Generic Brokerage Reference Schema, adopting SeaDataNet vocabs 17

ODIP 1 – GEOSS Brokerage service CDI collections now available by 2 public web services as provided by CNR via the Brokerage: OGC Catalogue Service for the Web (CSW) Version Service – HTTP POST method:–– OAI-PMH interface, at: Metadata format: ISO

ODIP 1 – SeaDataNet in GEOSS GEO-DAB Brokerage Service has populated SeaDataNet CDI collections in GEOSS portal Test Client at CNR (ESSI lab) : 19

ODIP 1 – SeaDataNet in ODP RIHMI-WDC, operator of IODE ODP portal, has harvested SeaDataNet CDI collections and included in ODP CSW gave issues with GeoNetwork; OAI protocol worked with jOAI harvester as also used in WIS 20

ODIP 1 – next activities Testing and finetuning of SeaDataNet -> GEOSS and SeaDataNet -> ODP Including a trigger for automatic updating of whole chain in case of CDI updating at SeaDataNet service Extending activities towards including US NODC and AODN services: 1 st at Brokerage level from US NODC and AODN 2 nd Brokerage towards GEOSS and ODP 3 rd between SeaDataNet, US NODC and AODN Proceeding with data access, including providing solutions for possible AAA systems 21

22 QUESTIONS?