GO-SHIP Executive Group and Committee video conference

Date: 15 May 23:00 (Paris summer time)
Duration: 2 hours
Attendance: Aida F. Rios, Bernadette Sloyan, Elaine McDonagh, Greg Johnson, Kumiko Azetsu-Scott,Lynne Talley, Martin Kramp, Mike Williams, Rik Wanninkhof, Steve Diggs Takeshi Kawano, Toste
Tanhua.

Bernadette, Rik and Martin welcomed everyone to the meetingi)

Coordinator update•••Martin requested that those who have outstanding input to the February respond to his request
so that he can finalize the meeting minutes. Regarding the national reports it was reported thatthe US Arctic sections is likely to be referred to as ARC01.
Action item: Everyone to submit report information if it is outstanding.
JCOMM are developing a new web site with GIS viewer. The new tools will allow for a crossprogramme view on the different panels coordinated by JCOMMOPS (Argo, DBCP, SOT,OceanSITES, GO-SHIP). A software engineer will be hired shortly and be tasked with thedevelopment and implementation.
Martin had a very successful meeting with CCHDO. Issue discussed included tracking timely
delivery of data to CCHDO and CDIAC. GO-SHIP data can now be browsed as a program atCCHDO. GO-SHIP will emulate the data discovery table as provided on the US Hydro web site forthe international program.

Action item: Work with CCHOD to develop data link and include in the GO-SHIP web site.
ii)

Terms of Reference: Co-Chairs, Executive Group, Committee Coordinator update•iii)

This was an issue that is a carry-over from the February meeting. Bernadette has not progressed
this further.
Action Item: Bernadette to write draft of Terms of Reference and circulate to the Executive
Group for comment prior to next meeting.
Data management: ERDDAP•iv)

There was a recent meeting in Toulouse with other data managers, with a good discussion
towards a common interface from all web sites for data searches. NOAA introduced ERDDAP,
which is a data server which gives a simple, consistent way to download subsets of gridded andtabular scientific datasets in common file formats and make graphs and maps. JCOMMOPS andCCHDO will investigate how to benefit from ERDDAP, in cooperation with NOAA.
GOOS: performance measurement•v)

GO-SHIP has been asked to define our metric of status of the program. This metric is used by
GOOS to gauge the completion of the program. Bernadette and Rik provided input to Martin
regarding a metric. After some discussion it was agreed that we begin with a simple metricbased on the on-time occupation of decadal repeats with complete level 1 measurement foreach section in the program. We acknowledge that this is a simple metric for use by high level
GOOS and other forums. However, within GO-SHIP we develop other means to track a more
complete appraisal of the program, that is, from funding proposal to submission of data at dataservers.
Action item: Martin, with Bernadette and Rik to produce a map of metric and send tocommittee for comment.
Network: additional sections•We have been approached from Penny Holliday (UK) regarding the inclusion of the UK Extended
Ellett line as a GO-SHIP section (http://projects.noc.ac.uk/ExtendedEllettLine/). Elaine
McDonagh commented that she thought that this may already be included in the UK
contribution to GO-SHIP.
Action item: Elaine to speak with Penny regarding this section and comment back to committee
if this is already a UK contribution or if not recommendation for inclusion as a part of GO-SHIP.

•Kumiko also mentioned that there are some sections maintained by Canada that could beincorporated into GO-SHIP.

•More generally the committee discussed how to deal with these and future requests. Anyrequest must fulfill the requirements of GO-SHIP; trans-basin coast-to-coast (sea ice);measurements requirement; data timeliness and temporal frequency. We must not allow ‘scope
creep’ of GO-SHIP. It was agreed that formal application (via a letter) must be sent to GO-SHIP.
The GO-SHIP committee will then consider the merits of the request, with particular attention towhether the additional section fulfills the requirement of GO-SHIP. To this end we need toinclude information on the data requirement (level 1, 2,and 3), data submission time lines andopen access to data.
Action item: Martin to add measurement and data submission requirements to the web site.
vi)

Joint Argo, Go-SHIP and IOCCP science workshop•Bernadette provided an update on the discussions that Brian King had at the Argo meeting. TheArgo committee was in principle in favor of a joint science workshop. Brian’s report is below
2015 was thought to be a good timescale.
Combining it with, eg, IUGG/IAPSO was thought NOT to be a good idea.
Some agencies see a meeting like IUGG and set limits on the number of national participants,(for example CSIRO did this for Ocean Sciences in February) so if this is regarded as the same
meeting as IUGG, we may reduce participation rather than increase it.
Initial names of flag-carriers who have stepped up from Argo areBrian King
Howard Freeland
Megan Scanderbeg (for those who don't know Megan, among her many Argo-related activities
are providing enormous executive support for Argo, based in Dean Roemmich's group at SIO)
Possible venue is Galway, Ireland.
We need to get this moving if it is going to happen
Action Item: Elaine McDonagh will take the lead for GO-SHIP, with Toste and Greg Johnson
offering help.

vii)

Web site overhaul•viii)

It was generally agreed that the web site, although somewhat dated, is still functioning
appropriately and doesn’t need a design overhaul. However, we do need to update somecontent.
Action Item: Bernadette, Rik and Martin to work together to update web site content.
Other business•AtlantOS: This EU project has moved into the second round. The proposal is due mid-June.

•Funding for Coordinator Position: (1) Australia has committed $20K and this will be sent in May;
(2) NOAA has money for Go-SHIP; (3) Japan has money and will organize paper work to makethe transfer; (4) There are no funds in Canada.
Next WebEX meeting planned for 15-24 September. Martin to step up doodle poll to find mostconvenient date/time