Collaboration for Beijing and Tokyo GISC prototypes

1

Collaboration for Beijing and Tokyo GISC prototypes

Akira Nakamori

JMA

ET-WISC-III 11-13.Jun.2008

2

List of content

1. Background

2. Overview

3. Providing datasets

4. Metadata synchronization

5. Remote data request

6. Internet portal

7. Web feed (ATOM)

8. Plan

3

1. Background

1. Background

2. Overview




6. Internet portal

7. Web feed (ATOM)

8. Plan

4

Background of the collaboration (1)

• The WIS implementation teams at CMA and JMA started to see an appropriate collaboration scheme in October 2005.

• CMA and JMA agreed to establish a framework of collaboration alliance between two GISC prototypes in Beijing and Tokyo and announced it at ICG-WIS-3 in 2006 (at ICG-WIS-4 in 2007 afterwards).

5

Background of the collaboration (2)

• The coordinated implementation started in March 2007.

• Administrator of CMA and Director-General of JMA met in Beijing in July 2007 and agreed that the WIS development was included in cooperative activities between CMA and JMA.

• First meeting of both WIS teams was held in Beijing, Nov 2007, to discuss technical details of the collaboration.

6

2. Overview

1. Background

2. Overview




6. Internet portal

7. Web feed (ATOM)

8. Plan

7

The overview of WIS activity

Remote data request

8

Content of cooperation

• CMA and JMA cooperate on the WIS development to implement interconnection and interoperation as follows.– Metadata exchange & synchronization– Remote data request & data access

9


1. Background

2. Overview




6. Internet portal

7. Web feed (ATOM)

8. Plan

10

Data Specification

General description Area Type Volume per day duration key1 key2Global-exchangedbulletins received atRTH-Tokyo (updated 2times / hour)

Region (1-6),Mobile,Antarctica

SYNOPSHIPTEMPPILOT

40MB/10000Bulletins13MB/3500Bulletins 1week

WMOheading

SYNOPSHIPTEMPPILOT

General description File Type Volume per day durationMTSAT full diskimagery (hourly)

J PG, GIF,SATAID

IR channel 1-4VIS channel

19GB/2550files 1week - - - -

Data Specification (in Data Pool)Observation

Sattelite

Selection Method (on Portal)

General description File Element duration key1 key2 key3TIGGE products GRIB2 10days EPS TIGGE GRIB2

CMA T213 GlobalModel products GRIB

height,temperature,wind, pressure,relative humidity,vertical velocity,vorticity,divergence. 10days NWP T213 GRIB

General description Area Type duration key1 key2Global-exchangedbulletins received atRTH-Tokyo (updated 2times / hour)

Region (1-6),Mobile,Antarctica

SYNOPTEMPCLIMATCLIMAT TEMP 2month

WMOheading

SYNOPSHIPTEMPPILOT

General description File Type duration key1 key2 key3

FY-2C, 2D CloudMotion Vectors BUFR

2D infra- redchaanel andwater vapourchannel 10days

SATELLITE FY-2C

2D CMVsBUFR

Sattelite

Selection Method (on Portal)Nwp Products

Data Specification (in Data Pool)

Observation

CMA

JMA

11

Metadata Specification

• Make metadata of operational data routinely

• Type of Metadata for synchronization– SYNOP, TEMP, ...

• Frequency of updating metadata– 4times / day

• WMO core metadata profile ver. 0.2

12


CMA JMAMetadata synchronization

1. Background

2. Overview




6. Internet portal

7. Web feed (ATOM)

8. Plan

13

Metadata synchronization

• CMA and JMA implemented the metadata exchange.– STEP1 : FTP get (PULL)

• CMA and JMA also plan to implement on metadata exchange in future.– STEP2 : OAI-PMH*

• OAI-PMH* : The Open Archives Initiative Protocol for Metadata Harvesting

14

Example (metadata synchronization)CMA

JMA

15


CMA JMARemote data

request

1. Background

2. Overview




6. Internet portal

7. Web feed (ATOM)

8. Plan

16

Remote data request

• CMA and JMA agreed with protocol and interface

• Users can get the data provided only at the CMA(JMA) site by sending request to the JMA site without visiting the CMA site.

17

Request for JMA data to CMA

• Remote request performed when CMA’s server have no data for user’s request.

CMA JMA

Data Portal

Service node

CMA data sources

Cached data

Service node

JMA data sources

Yes

(1)

(2)(3)

(4)

(5)(6)

(7)(8)

Data Portal

User

(9)

Catalogue node

locate the data

Request File (XML)

Requested data

Result Description File

User can check request processing result at CMA portal

No(*)

(*) : If JMA data is available in CMA cache, Service node of CMA reply without sending request to JMA note.

Cached data

18

6. Internet portal

1. Background

2. Overview




6. Internet portal

7. Web feed (ATOM)

8. Plan

19

Beijing WIS Portal (Search & Directory)

• Users can search Metadata by keyword and directory hierarchy. Display Metadata

Show original XML

directory hierarchy

Keywords & Period search

20

Tokyo WIS Portal (Search)

• Users can search Metadata by keyword.

Display Metadata

Show original XML

Keywords such as SYNOP global, SATAID,US, BABJ, typhoon

21

Beijing WIS Portal for retrieve

• Users can easily get data such as a GTS bulletin.

Archive file

22

Tokyo WIS Portal for retrieve

• Users can easily get data such as a satellite image.

Invertible between data and metadata

23

7. Web feed (ATOM)

1. Background

2. Overview




6. Internet portal

7. Web feed (ATOM)

8. Plan

24

Web feeds (Atom)

• Users can check for updates from Feed.

Subscribe the feed by feed reader (Aggregator)

25

ATOM Feed reader example• Users can check for updates of the

Metadata from Feed.

• Users can also get such Keyword as ‘SM’

26

8. Plan

1. Background

2. Overview




6. Internet portal

7. Web feed (ATOM)

8. Plan

27

Plan for Collaboration

• Metadata synchronization– FTP get (PULL) : 2008, 2Q (Done)– OAI-PMH : 2008, 3Q

• Remote data request– Remote data request : 2008, 2Q

28

Thank you

Collaboration for Beijing and Tokyo GISC prototypes

Documents

Transcript of Collaboration for Beijing and Tokyo GISC prototypes