1 NODC, Russia GISC & DCPC developers meeting Langen, 29 – 31 March E2EDM technology implementation for WIS GISC development S. Sukhonosov, S. Belov

2 NODC, Russia History E2EDM was originated as one of the JCOMM/ETDMP pilot projects in 2003 MetOffice, UK IFREMER, France VLIZ, Belgium NODC, Russia

3 Pilot project data sources The following data sources are involved in the E2EDM prototype Historical marine meteorological data Historical ocean cruise data Real-time GTS ocean (BATHY and TESAC) data Real-time GTS ocean (TESAC/ARGO data) Real-time GTS (SHIP) data Monthly climatic fields of ocean parameters (imageries) Ocean SST satellite data Geographic area – North Atlantic (test-area)

4 Scope NODC, Russia E2EDM provides following functionality: Wrapping local data by means of E2EDM components Mapping mechanisms (codes, structures) Data search and retrieving from distributed data sources on user requests (real-time and scheduled) Data obtaining and further processing, visualization and exchange E2EDM is integrating operational and delay-mode time scale data; across oceanographic and marine meteorological disciplines; from multiple data source formats and multiple data providers in different geographic regions.

5 NODC, Russia Basis NODC, Russia Concept model Namespace Data exchange protocol

6 NODC, Russia E2EDM concept model NODC, Russia Providing formalization, identification, description and interpretation for model objects. Model is based on the following semantic objects: Element Class (set of elements) Record (set of classes) In terms of the model each technological object is described by means of listed semantic objects. E.g. object called “Resource” is record, which contains features – classes. Each resource record (or description) contains granularity structures for the source data, e.g. first level of granularity – platform, second level – date and time, third – measurements (sea surface temperature, water salinity, etc.).

7 NODC, Russia E2EDM namespace NODC, Russia Defines metadata and data structures. Within E2EDM consists of two sub-namespaces: global and conceptual (thematic). Global namespace – structures for the model objects Conceptual (thematic domain) namespace – list of thematic elements dealing with some discipline, e.g. meteorology, and available for discovery and exchange. Both based on XML Schema. 1.Global XML Schema (ISO WMO Core Metadata) 2.Concept XML Schema (DiGIR)

8 NODC, Russia E2EDM data exchange protocol NODC, Russia Data exchange protocol is responsible for searching and data retrieving. Request message (XML, DiGIR-protocol) Response message (XML, DiGIR-protocol) Transport data file (NetCDF)

9 NODC, Russia <request xmlns=" xmlns:e2edm=" xmlns:xsi=" xsi:schemaLocation=" T14:47:52+03: search false Request message example

10 NODC, Russia Response message example T15:35:17+04:00 search result.nc 7

11 NODC, Russia E2EDM prototype components 1.E2EDM prototype specifications -- structures, metadata/data formats, codes and other means of data unification from the local data systems 2.E2EDM Prototype software – E2EDM Data Provider system and E2EDM Integration Server

12 NODC, Russia Functionality: Integration server Data discovery (through resource catalog) Monitoring of distributed data sources Request/reply mechanism Data distribution from the multiple data sources Metadata synchronization Data Provider Request handling Access to the local data source (DBMS, files) Data extraction based on search criteria Transport data file generation Diagram of prototype

13 NODC, Russia General scheme User Integration Server Interface layer (HTTP, Web-services) request Data Provider Request message reply Transport data file Response message

14 NODC, Russia Integration Server user web-interface Resource catalogue Parameters Additional search options

15 NODC, Russia Integration Server user web-interface (cont.) Search status

16 NODC, Russia E2EDM Web site E2EDM Integration Server - IODE Project Office (VLIZ) RIHMI-WDC (mirror) Integration Server user web-interface (cont.) Point data grid data profile data

17 NODC, Russia Current status Released technical specification document Builded software framework using SOA Extended community of national Data Providers Solved performance problems (e.g. response time) Implemented caching mechanism Defined user policy

18 NODC, Russia Future… It is important to develop administrative services for component management and maintenance To build up predefined queries, push/pull and notification mechanisms System metadata mapping into WMO Core Metadata Profile To develop web-services in order to improve compatibility with other systems

19 NODC, Russia Thank you! Questions?

20 NODC, Russia