html5-img
1 / 27

GOSUD

GOSUD. 5 th meeting Boulder, USA 2-4 May, 2006. Status. Review of progress has been extracted from the Annual Report prepared in early 2006 plus some additional updates. Comparison will be made to Project Plan prepared in early 2003. GOSUD Meeting 2-4 May, 2006. Planned Data Flow.

hinda
Télécharger la présentation

GOSUD

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. GOSUD 5 th meeting Boulder, USA 2-4 May, 2006

  2. Status • Review of progress has been extracted from the Annual Report prepared in early 2006 plus some additional updates. • Comparison will be made to Project Plan prepared in early 2003 GOSUD Meeting 2-4 May, 2006

  3. Planned Data Flow GOSUD Meeting 2-4 May, 2006

  4. Data Flow GOSUD Meeting 2-4 May, 2006

  5. Data Flow (2004) GOSUD Meeting 2-4 May, 2006

  6. Data Flow update In 2005: 260,000 stations were received in real-time from the GTS. To end of March 2006 received 8,692 stations (many more at GDAC) There has been a falloff of real-time reports in the first months of 2006. There have been only a few real-time reports from Seakeepers. GOSUD Meeting 2-4 May, 2006

  7. Data Flow update Note: These are data extracted from the GTS. Some data are coming directly to the GDAC through Inmarsat C GOSUD Meeting 2-4 May, 2006

  8. GDAC Operations • FTP server running • WWW server came on-line • (http://www.gosud.org/gdac.htm) • Started to receive data directly from countries GOSUD Meeting 2-4 May, 2006

  9. Archive - Apr, 2006 GOSUD Meeting 2-4 May, 2006

  10. Statistics (end 2004) GOSUD Meeting 2-4 May, 2006

  11. Sample Analyses GOSUD Meeting 2-4 May, 2006

  12. Quarterly Report Observing System Status: 2004, Q4 Sea Surface Salinity Sampling requirements: 1 observation Every 10 days In every 2 x 2 º BATHY (mostly XBTs) TRACKOB (surface underway data) TESAC (mostly Argo floats) BUOY (moored and drifting) Requirement: All boxes blue Goal: 100% Global Coverage GOSUD Meeting 2-4 May, 2006

  13. Real-time data flow (end 2005) GOSUD Meeting 2-4 May, 2006

  14. Southampton Actions - 1 GOSUD Meeting 2-4 May, 2006

  15. Southampton Actions - 2 GOSUD Meeting 2-4 May, 2006

  16. Southampton Actions - 3 GOSUD Meeting 2-4 May, 2006

  17. Real-time data assembly • Actions taken: • Data continue to come to MEDS and be forwarded to Coriolis • Inmarsat C data continue to come to LEGOS and be downloaded to Coriolis • Actions still to do: • engage other countries in direct provision of data • Develop a process to notify platforms of problems • Contact ocean and atmospheric modelers for advice on how they now use or could use underway data reported in real-time. Data Assembly • Delayed mode data assembly: • Actions taken: • Coriolis has been proactive in acquiring “historical” data from the same nations as for real-time plus some from US • Actions still to do: • Continue to engage other countries in direct provision of data GOSUD Meeting 2-4 May, 2006

  18. Archive & Processing • Actions taken: • Web site built • Actions still to do: • Ensure that the web site continues to be maintained and improved. • Ensure that data contributors are permitted to manipulate their own data only. • Ensure that archived data retain all agreed metadata for the Project. • Collaborate with WDCs to ensure the long term safekeeping of the data and information. • Determine what to do with historical ICES data. • Approach IODE, and JCOMM to assist in training (data management and instrumentation installation and maintenance) data contributors and group participants. GOSUD Meeting 2-4 May, 2006

  19. QC Processing • Actions taken: • Automatic QC Manual written and posted on web site. • MEDS Instituted an auto QC function. • Delayed mode data acquired from countries and auto QC’ed. • Actions still to do: • Develop a process to notify ships when problems are found in the data. • JCOMMOPS Technical Coordinator to help track underway data collected and resolve problems. GOSUD Meeting 2-4 May, 2006

  20. Duplicates • Actions taken: • Actions still to do: • Carry out the assignment of data identifiers as early as possible in the data collection process. • Verify that data received are new to the data system, before assigning a unique identifier. • Ensure that identifiers are carried and preserved in all data exchanges. • A standardized product showing the incidence and type of errors detected that is issued to data collectors. • Design and document the process of assigning unique identifiers • Coordinate the development of a standard product to show errors in data and notification of the platforms. GOSUD Meeting 2-4 May, 2006

  21. Products • Actions taken: • Project website is created with data and information • Contributions to JCOMM Quarterly Reporting • Actions still to do: • Ensure products generated specifically for the Project are labeled with a Project identifier. • Ensure each product identifies what data contributed to the product • Encourage integrated data products • Compile a list of publications that discuss analyses of data collected by the Project • Conduct a review of products issued to determine the most effective ones and areas where • products are missing. GOSUD Meeting 2-4 May, 2006

  22. Monitoring and Feedback • Actions taken: • Establish a connection to the GTS and acquire all underway data reported in TRACKOB or BUFR • Actions still to do: • Identify and contact platforms reporting data on the GTS but which are not reporting data to the global server to seek participation • Identify and contact platforms reporting data to the global server(such as the data coming by Inmarsat C) but which are not reporting data on the GTS to seek participation GOSUD Meeting 2-4 May, 2006

  23. Annual Reporting • Actions taken: • Annual reports for 2001-2004 complete • Actions still to do: • Publish 2005 report by mid 2006 GOSUD Meeting 2-4 May, 2006

  24. Other • BUFR • Template from Japan • JCOMM DMPA will be taking up the cause • Will review template and move this forward • MEDS BUFR decode for surface drifters in BUFR in testing • SAMOS • Collaboration is underway GOSUD Meeting 2-4 May, 2006

  25. GOSUD & SAMOS GOSUD and the organizers of the SAMOS, have agreed to pursue common strategies to streamline the handling of meteorological and oceanographic data collected by underway vessels. In order to accomplish this collaboration between the two projects, it is necessary to fill in details on a number of issues. These include such things as • 1. What is the required minimum metadata and how can users gain access? • 2. There has been agreement by SAMOS that they will accept the ocean data as well as the meteorological data, so that collectors will have one place to forward the data. There is an understanding that SAMOS would then forward the ocean data to the GDAC for their processing. What are the procedures to accomplish this? GOSUD Meeting 2-4 May, 2006

  26. GOSUD & SAMOS • 3. How will SAMOS and GOSUD ensure that the combined meteorological and oceanographic data that arrive in a single data stream can also be delivered back to a user in a single stream? • 4. Both SAMOS and GOSUD have quality control procedures for SST. Do these produce different results and what can be done to reconcile these differences? • 5. Some French oceanographic vessels currently collect meteorological data that though archived but no further processing takes place. Will SAMOS be prepared to accept these data and how soon? • 6. Is it sensible for SAMOS to run the automated QC procedures on behalf of GOSUD? • 7. What will be the process of data handling for meteorological data arriving at GOSUD first, or at NODC? • 8. Is it better for ocean data to go to GOSUD GDAC for delivery to ocean clients or simply ask SAMOS to serve it all? GOSUD Meeting 2-4 May, 2006

More Related