GOSUD 5 th meeting Boulder, USA 2-4 May, 2006

Status GOSUD Meeting 2-4 May, 2006 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

Planned Data Flow GOSUD Meeting 2-4 May, 2006

Data Flow GOSUD Meeting 2-4 May, 2006 Number of Stations At GDAC Real-time (on GTS) To end of ,000610,000 In ,000110,000 In ,000275,000

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

Data Flow update GOSUD Meeting 2-4 May, 2006 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 There have been only a few real-time reports from Seakeepers.

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

GDAC Operations GOSUD Meeting 2-4 May, 2006 FTP server running WWW server came on-line ( Started to receive data directly from countries

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

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

Sample Analyses GOSUD Meeting 2-4 May, 2006

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

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

Southampton Actions - 1 TaskResponsibilityTarget Date 1MEDS and Coriolis to decide and implement how real-time data from GTS contribute to GOSUD MEDS does auto QC and ftps to Coriolis daily Keeley and CarvalNext meeting 2Investigate how to get Japanese and other data into GOSUD Informed that the only way is from the GTS Co-chairs, RickardsNext meeting 3Australia agreed to document data flow from their ships and provide to co-chairs Butler1 Jan AOML to notify MEDS when first data go out to the GTS for verification that they were received Chong, KeeleyNext meeting 5AOML to document delayed QC procedures and provide to GDAC for inclusion on web site Chong, KeeleyNext meeting 6AOML contact SAMOS in US to determine level or cooperation / duplication and to take appropriate actions and report to next meeting Chong, CookNext meeting 7Need to compare underway data available from WOCE DR V3 to what have been made available at GDAC, and WOD Petit de la Villeon, RutzNext meeting 8NODC to implement a long-term archive and mirror service of the GOSUD GDAC RutzNext meeting GOSUD Meeting 2-4 May, 2006

Southampton Actions - 2 TaskResponsibilityTarget Date 9Coriolis to provide a description of statistical tests prior to feeding data to modelers Carval, DelcroixNext meeting 10Identify the duplicates problem(s) needing solution, propose solution(s) and to begin implementation as possible. Keeley, Vladimir, Rutz, Petit de la Villeon Next meeting 11Products or documents of interest to GOSUD to be linked to from the GOSUD web pages All, Loic Petit de la Villeon On-going 12Set up a data subscription service Done? CarvalNext meeting 13Define how to distinguish data of RT or DM quality and resolution and how to indicate this easily to users. Rickards, Carval, Delcroix, Keeley Next meeting 14GDAC to prepare a document or help page that describes the various ways data can be accessed from the GDAC. CarvalNext meeting 15Keep under review how GOSUD data can be used by modelers. Co-chairsNext meeting 16Draft a reply to specific questions raised by metadata requirements proposed by SAMOS Keeley sent notes from the meeting – 5 Oct, 2004 Keeley, Delcroix, Rickards31 Oct, 2004 GOSUD Meeting 2-4 May, 2006

Southampton Actions - 3 TaskResponsibilityTarget Date 17Develop details of how SAMOS and GOSUD will cooperate Keeley, Delcroix, SAMOSNext meeting 18Keep GOSUD informed of developments in the FerryBox program RickardsNext meeting 19Complete 2003 Annual Report Done, & 2004 KeeleyDec, Provide information to Keeley on who is using GOSUD data, and statistics on data downloads All, Carval30 Nov, Provide comments on the proposed BUFR template for underway data Sent 5 Oct, 2004 Keeley31 Oct, Prepare poster for IODE meeting and if possible for GODAE meeting Completed Rickards, Keeley, Petit de la Villeon, Delcroix Apr, 2005 GOSUD Meeting 2-4 May, 2006

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 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.

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

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

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

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

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

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

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

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 GOSUD Meeting 2-4 May, 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 & SAMOS GOSUD Meeting 2-4 May, 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?