1. IV-3.1 JCOMMOPS SOT Technical Coordinator

2. 2 JCOMMOPS structure Programmes currently supported –Ship Observations Team (30% Mathieu Belbeoch) –Argo Profiling Float Program (70 % Mathieu Belbeoch) –Data Buoy Cooperation Panel (70 % Hester Viola) –OceanSITES reference station network (30 % Hester Viola) Technical coordinator activities include –User assistance –JCOMMOPS - information system operations & maintenance (database, new web server, metadata uploads and reporting) –Production of monthly maps –Production of annual Line Sampling reports

3. 3 Website and audience JCOMMOPS IT infrastructure upgraded during inter-sessional period –New web server –Metadata loading and processing scripts transitioned to replacement server –Web / FTP server and GIS software upgrades –Changes to ensure compliance with Argos system upgrades The upgraded Web server is generally stable –Some delays twice a day due to data loading –CLS monitoring team are able to restart JCOMMOPS web services if required

4. 4 Website and audience Usage statistics are now collected for all JCOMMOPS sites 2008 web site usage data all JCOMMOPS sites –~80 visits/day, –~400 visits/week, –~1500 visits/month –18,862 visits in 2008, from 138 countries –74,748 pages viewed These statistics will help –determine usage levels and audience for the site and –identify requirements for future JCOMMOPS web services

5. 5 Monthly maps and products JCOMMOPS reporting and monitoring includes –Monthly map of XBT profiles reported on the GTS –Monthly map of sub-surface temperature profiles –Annual SOOP line sampling report (Survey), available on JCOMMOPS website –Monthly SOOP BATHY report, now only available at: ftp://ftp.jcommops.org/SOOP/Reports/ ftp://ftp.jcommops.org/SOOP/Reports/ Some reports have been discontinued due to under-utilisation or obsolescence –JJXX / JJYY : report on use of old JJXX / JJYY formats on the GTS discontinued as only one recent use of the format (May 2007, EMPIRE STATE, Call sign : KKFW) –Creation of Upper Ocean Thermal data maps by country - used to be produced biannually, but not up to date currently. Data captured in monthly map at http://wo.jcommops.org/cgi-bin/WebObjects/JCOMMOPS.woa/wa/map?type=GTSM_SZ http://wo.jcommops.org/cgi-bin/WebObjects/JCOMMOPS.woa/wa/map?type=GTSM_SZ

6. 6 Monthly maps and products Redevelopment of Map layer (GIS) file production across JCOMMOPS, for easier maintenance Monthly SOOP maps now include information about XCTD and TSG observations –PDF versions of all maps now available allowing layers to be toggled on or off to show different observations separately Google Earth files now available Feedback on these reports is requested from panel members – are the reports useful and appropriate?

7. 7 SOOP Annual sampling report SOOP annual sampling reports complete for 2006 and 2007 –2006 SOOP Line Sampling Report - finalised and metadata made available in the final SOOP report http://www.jcommops.org/FTPRoot/SOT/SOOP/Survey/2006-Jan-Dec.zip http://www.jcommops.org/FTPRoot/SOT/SOOP/Survey/2006-Jan-Dec.zip and on the website at http://wo.jcommops.org/cgi-bin/WebObjects/SOOPIndicatorshttp://wo.jcommops.org/cgi-bin/WebObjects/SOOPIndicators –2007 SOOP Line Sampling Report - finalised and XBT metadata made available in the final SOOP report http://www.jcommops.org/FTPRoot/SOT/SOOP/Survey/2007-Jan-Dec.zip http://www.jcommops.org/FTPRoot/SOT/SOOP/Survey/2007-Jan-Dec.zip and on the website at http://wo.jcommops.org/cgi-bin/WebObjects/SOOPIndicatorshttp://wo.jcommops.org/cgi-bin/WebObjects/SOOPIndicators All SOOP annual metadata from the past 7 years is being exported to text files e.g. –http://www.jcommops.org/FTPRoot/SOT/SOOP/Survey/2006_metadata_soop.txthttp://www.jcommops.org/FTPRoot/SOT/SOOP/Survey/2006_metadata_soop.txt –http://www.jcommops.org/FTPRoot/SOT/SOOP/Survey/2007_metadata_soop.txthttp://www.jcommops.org/FTPRoot/SOT/SOOP/Survey/2007_metadata_soop.txt

8. 8 SOOP Annual sampling report SOOP reports now include links to the relevant information on the SOOP website (not all data is included in the report itself) –http://wo.jcommops.org/cgi- bin/WebObjects/SOOPIndicators.woa/wa/summary?line=PX40&year=2007&month=12http://wo.jcommops.org/cgi- bin/WebObjects/SOOPIndicators.woa/wa/summary?line=PX40&year=2007&month=12 Submission of metadata by many SOOPIP data managers has been improved which speeds up report generation Some discrepancies were identified (in 2005) between the metadata provided for the SOOP Annual Sampling Report and the data reported on the GTS for the 12 months –Some Navy XBT (non-SOOPIP) data going onto the GTS –Some data delayed too long to appear on the GTS More details of recent results of XBT sampling along SOOP lines are given in the following slides A comparison of SOOP sampling success from 2002 – 2007 is also provided

9. 9 2007 SOOP Sampling report XBT Drops by country for the period January to December 2007

10. 10 2007 SOOP Sampling report XBT Line Sampling Success - January to December 2007

11. 11 2008 SOOP Sampling report Preliminary results available for 2008 Line Sampling Report –Almost all XBT metadata has now been submitted for 2008 (19,350 drops) –timely submission of metadata is no longer a real problem –Initial results appear slightly better than 2007 Number of metadata records for drops submitted by SOOP Operators to JCOMMOPS for 2007 and preliminary 2008

12. 12 Trends in SOOP Line Sampling success Analysis of Line sampling 2002 - 2007 indicates that –11 of 45 lines were consistently well-sampled / had improved over the period –8 lines were consistently under-sampled / not sampled –15 lines have decreased their sample quality over the period i.e. gone from being relatively well sampled to ~50% sampled or from ~50% sampled to being under sampled Summary of Sampling Success for UOT lines between 2002 and 2007 (Draft results for 2008)

13. 13 Trends in SOOP Line Sampling success Analysis of the 2002 – 2007 data highlights potential areas for improvement SOOP line sampling performance trends 2002 - 2007

14. 14 Communication & Deployments Argo and Drifting Buoys : Optimal number of platforms attained, however some gaps in networks identified in SOT TC report Members requested to provide information on deployment opportunities from ships operating on SOOP lines SOOP Lines which could be used to deploy Argo floats or drifting buoys in areas required are: Lines which have been active in the SOOPIP, which go through areas that have been consistently without drifting buoys VOS operators may also be able to provide details of ships which regularly go through areas of interest. –Any information should be passed to the Technical Coordinator

15. 15 JCOMMOPS Future plans Redesign of JCOMMOPS website –Improve ease of use and integration across all programs –Improve quality control feedback mechanisms (VOS, Argo, DBCP) Coordinate updates to Best Practice documents for all SOT programs Become actively involved in definition of BUFR template requirements Address requirement for new resource to work on Cruise Planning Address need for improved products to track deployment opportunities for SOT vessels

16. 16 Recommendations Team members to provide feedback on SOOPIP and JCOMMOPS websites and reports –Identify requirements for any new reports –Evaluate usefulness of existing reports and any requirements for modifications In particular the monthly SOOP BATHY report (decide whether to retain it) JCOMMOPS to receive copies of Publication 47 submissions from the WMO Please address all correspondence to: support@jcommops.org support@jcommops.org