1. Third Plenary Meeting of SeaDataNet Bob Keeley Integrated Science Data Management, (ISDM) Canada March, 2009

2. SeaDataNet Mar 2009 Overview 1.General comments 2.Some information about other activities Canada USA 3.Observations on work reported at this meeting 4.General observations 5.Suggestions 6.Now and after SDN

3. SeaDataNet Mar 2009 General Comments 1.Advantage and disadvantage of a yearly snapshot of the project. I see progress but miss details. 2.Overall, as last year, I am very impressed with the progress and achievements. 3.You have done a lot to further the setting of standards and this is very important. 4.You have the base of a full distributed system that has largely defeated the duplicates problems that plague us.

4. SeaDataNet Mar 2009 What is happening in Canada? 1.DFO is responsible for a much of the oceanographic data collected. 2.Most research data come from the Science Sector of DFO in which ISDM is sited. 3.4 years ago, Science reorganized so that data management gained a much higher profile and resulted in increased funding 4.We now have a national committee to coordinate activities and roughly 1 million CAD each year for projects (no guarantees into future). 5.Objective is to knit together a whole data system from 7 distinct (largely independent) pieces.

5. SeaDataNet Mar 2009 Scope of projects 1.Fisheries data from trawl surveys, ecosystem work, larval fish, hydroacoustics, … for lots of species. 2.Biological data including plankton measurements, marine mammal and other species tracking. 3.Lots of chemistry and physical oceanography 4.Data rescue projects from both marine and freshwater. 5.Digital images (videos, stills, microarray spectra, …) 6.Web services 7.Data catalogue and metadata (MCP) 8.Gridded bathymetric product served through web services 9.Use of taxonomy (ITIS) 10.Physical sample preservation and tracking.

6. SeaDataNet Mar 2009 Data at ISDM 1.Physical oceanography: delayed mode and lots received in real-time from GTS including from ships, profiling floats, surface drifters, wave buoys, tide gauges. 2.Biological: Invasive species, plankton 3.Chemical: contaminants, nutrients, etc. 4.Bathymetric: all hydrographic charts for Canada plus ENC delivery

7. SeaDataNet Mar 2009 Data Volumes 1.Largest physical oceanography comes from surface drifters. Archive holds global measurements with > 75 million reports and growing at ~ 1 million/month 2.Global real-time profiles (Argo, ships, moorings, …): > 8 million stations and growing about 3 million/year (last year) 3.Wave spectra: ~ 10 million, adding 300,000/year 4.Tide gauges: ~ 4 million variable-days, adding 120,000/year 5.Bathymetry: lots and lots of individual soundings!

8. Surface drifter Map SeaDataNet Mar 2009 Was ~ 33 million in 2004, now is 75 million.

9. Summary SeaDataNet Mar 2009 1.If nothing else, we have large data volumes to deal with though the variety at ISDM is perhaps less than some of you have. Including the data at regional institutes, we have lots of variety. 2.We have the same issues about placing large archives on-line for download. Some of our requests are very large. 3.We have same issues of adopting/creating standards. 4.We need a robust architecture to deal with additional kinds of data. 5.We need to serve increasingly more varieties of data on-line.

10. What is happening in U.S.? SeaDataNet Mar 2009 1.DMAC activity in the US has been reinvigorated in last 18 months 2.They have also been pursuing standards some (many?) of which are different from yours 3.They are also are building a distributed, interoperable system without (I believe) an equivalent of CDI, CSR, etc.

11. Observations on work reported at this meeting - 1 SeaDataNet Mar 2009 1.There seems to have been some intercomparisons of QC at least with WODB. Has there been a check of internal consistency? I would like to see a document. 2.The CDI at present is roughly 1/2 million records. How will the performance scale when this is 10X, 100X larger? (Roy says no problem). 3.Some partners already deal in real-time / operational data and from a variety of sources. This starts to look like the real-time data we process. Does SDN want to open this door further? 4.It will be interesting to propose ODV/DIVA to ICOADS.

12. Observations on work reported at this meeting - 2 SeaDataNet Mar 2009 5.The download limitation of 500 records / transaction is a (near) future problem. Perhaps a solution is to allow larger single transactions but treat them as you do requests for data from centres without the download manager? (i.e. off-line, off peak processing) 6.Climatology generation needs careful validation. WOA is used extensively and so you should prove your results against that (and OI from CORIOLIS). Do sensitivity analyses of results to CL, S/N. 7.Andrew Wolf provided a favourable review of SDN. Did he comment on IT security issues? Can others use his comments to assure their own IT staff of precautions taken to secure the system? A document outlining these precautions would be nice.

13. Observations from this meeting SeaDataNet Mar 2009 1.Up until now, SDN has (rightly) focused inwards on getting your project running. I see that though not complete, you have a base running. 2.I would suggest it is time to begin to look outward for a couple of reasons: Your standards developments are important to more than yourselves. As SDN completes, this is a way to grow what has been produced and sustain the initiative into the future.

14. Suggestions to Consider SeaDataNet Mar 2009 1.DMAC and SDN are diverging. Send someone to the next possible DMAC meeting to do a presentation. 2.Share your standards work with the world. Use the OceanDataStandards web site and process to do this. (see http://oceandatastandards.org )http://oceandatastandards.org 3.JCOMM and IODE are developing the ODP in support of a funded pilot project from WMO. But ODP and SDN seem to be on different development paths. What can be done to remedy this? Do you want 2 systems in Europe?

15. Now and after SDN - 1 SeaDataNet Mar 2009 1.SDN provides the funding to build a distributed system, but the “glue” that keeps these together is the coordination activities. After SDN, without this coordination, the system risks breaking. 2.Use the international systems, IODE, JCOMM, to help continue the coordination into the future even if you secure more EU funding. 3.When funding ends, what will other partners do if one drops out? 4.OceanObs’09 will take place in September this year. A plenary paper will set out the 10 year objective for ocean data management. You want to have a voice.

16. Now and after SDN - 2 SeaDataNet Mar 2009 5.The WDC system is undergoing a large change right now. Given that SDN is a distributed system that preserves data in the long term, what do you want from the WDCs? 6.What is the relationship between SDN and the various DACs that now exist? 7.What connections would you want to make to the various data collection panels that operate under JCOMM? 8.What do you want from and what do you want to contribute to IODE and JCOMM?