1 / 28

Collaboration for Beijing and Tokyo GISC prototypes

Collaboration for Beijing and Tokyo GISC prototypes. Akira Nakamori JMA ET-WISC-III 11-13.Jun.2008. List of content. Background Overview Providing datasets Metadata synchronization Remote data request Internet portal Web feed (ATOM) Plan. 1. Background. Background Overview

camden-patterson
Télécharger la présentation

Collaboration for Beijing and Tokyo GISC prototypes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Collaboration for Beijing and Tokyo GISC prototypes Akira Nakamori JMA ET-WISC-III 11-13.Jun.2008

  2. List of content • Background • Overview • Providing datasets • Metadata synchronization • Remote data request • Internet portal • Web feed (ATOM) • Plan

  3. 1. Background • Background • Overview • Providing datasets • Metadata synchronization • Remote data request • Internet portal • Web feed (ATOM) • 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 • Background • Overview • Providing datasets • Metadata synchronization • Remote data request • Internet portal • Web feed (ATOM) • 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. 3. Providing datasets • Background • Overview • Providing datasets • Metadata synchronization • Remote data request • Internet portal • Web feed (ATOM) • Plan

  10. Data Specification 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. JMA CMA Metadata synchronization 4. Metadata synchronization • Background • Overview • Providing datasets • Metadata synchronization • Remote data request • Internet portal • Web feed (ATOM) • 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. JMA CMA 5. Remote data request Remote data request • Background • Overview • Providing datasets • Metadata synchronization • Remote data request • Internet portal • Web feed (ATOM) • 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. User User can check request processing result at CMA portal locate the data CMA JMA (1) Catalogue node Data Portal Data Portal (9) JMA data sources Request File (XML) (3) (2) Yes (6) Service node (5) Service node CMA data sources No(*) (4) (7) (8) Requested data Cached data Cached data Result Description File (*) : If JMA data is available in CMA cache, Service node of CMA reply without sending request to JMA note.

  18. 6. Internet portal • Background • Overview • Providing datasets • Metadata synchronization • Remote data request • Internet portal • Web feed (ATOM) • Plan

  19. Beijing WIS Portal (Search & Directory) • Users can search Metadata by keyword and directory hierarchy. Display Metadata Keywords & Period search directory hierarchy Show original XML

  20. Tokyo WIS Portal (Search) • Users can search Metadata by keyword. Keywords such as SYNOP global, SATAID,US, BABJ, typhoon Display Metadata Show original XML

  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) • Background • Overview • Providing datasets • Metadata synchronization • Remote data request • Internet portal • Web feed (ATOM) • 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 • Background • Overview • Providing datasets • Metadata synchronization • Remote data request • Internet portal • Web feed (ATOM) • 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

More Related