SAMOS-GOSUD Meeting. Boulder 2-4 May Potential collaboration between the Coriolis project and the Samos initiative L. Petit de la Villéon. Ifremer-France-

SAMOS-GOSUD Meeting. Boulder 2-4 May Plan Description of the Coriolis project and its 5 components Focus on the Data Centre component (The Coriolis data centre) Various sources of data Focus on the research vessels components Routine measurements Potential collaboration between the SAMOS initiative and the Coriolis project Could the Coriolis project being a partner of the SMOS / Aquarius cal-val process ?

SAMOS-GOSUD Meeting. Boulder 2-4 May Coriolis as a part of a global structure for operational oceanography: a french approach in an international context

SAMOS-GOSUD Meeting. Boulder 2-4 May IN SITU OBSERVATION Coriolis aims to be a one-stop shopping for ocean in-situ data: - near real-time (assimilation) - delayed-mode (validation) Validation Delayed mode SATELLITE OBSERVATION ASSIMILATION MODELS Model outputs Near real time Assimilation Products

SAMOS-GOSUD Meeting. Boulder 2-4 May IN SITU OBSERVATION There is a strong need of in situ data for cal- val purposes. Validation Delayed mode SATELLITE OBSERVATION ASSIMILATION MODELS Model outputs Near real time Assimilation Products Validation Database

SAMOS-GOSUD Meeting. Boulder 2-4 May How did Coriolis start to work on operational oceanography? With a 7 french research institutes partnership With a 5 components approach Science Data centre Floats deployments Research vessels operations Instrumentation

SAMOS-GOSUD Meeting. Boulder 2-4 May Coriolis data flow Coriolis-Database Quality Controls Products analyses, graphics, maps current estimates sensor drifts Argo Dacs Argo coriolis, gyroscope, Mersea,33 projects Provor, Apex, Nemo Météo-france Gts data Lagrangian buoys Research vessels xbt-ctd, tsg Atalante, thalassa, suroît, Beautemps-Beaupré, Marion-Dufresne, Meteor, VOS- merchant ships ORE SSS (IRD) T & S surface data Gtspp- Gosud Meds GTS US-nodc historical data GTS (Météo- France) argo web Clivar delayed mode data sets Mersea, Mercator Godae Other models soap (Shom- French Navy) Gtspp- Gosud real time flow delayed mode 12h 1 year ftp, opendap, las dynamic daily weekly annual daily*2 48h 1 year 12h Moorings Tao, Triton, Pirata

Data sources Argo floats Moorings Research vessels Merchant ships Sea mamals or sea elephants Gliders Drifting buoys

SAMOS-GOSUD Meeting. Boulder 2-4 May Vertical profiles from 26th April to 3rd May This is today !!! About new profiles every week

SAMOS-GOSUD Meeting. Boulder 2-4 May Coriolis project: routine measurements on board the research vessels - Consider the data collected on board the research vessels as a full part of a global and continuous component of the ocean observing system. Ships considered are mainly french vessels. Effort is made at an European level - Define and set up the data collection transmission protocols, evaluate the sensors drifts in relation with the science group, make the link between ship operators and data centre

SAMOS-GOSUD Meeting. Boulder 2-4 May Research vessels component Data considered: –T and S vertical profile data from XBT and CTD – surface T & S Data –Current data from VM-ADCP In the frame of : –national projects –european funded projects In relationship with international projects: – GOSUD (IODE)

SAMOS-GOSUD Meeting. Boulder 2-4 May Example: T & S surface data collected on board research vessels (thermosalinographs)

SAMOS-GOSUD Meeting. Boulder 2-4 May Example: XBT, CTD and ADCP data collected on board french and european research vessels

SAMOS-GOSUD Meeting. Boulder 2-4 May Directions for potential collaboration (1/5) Access to new sources of data (1/2) SAMOS collect data from US Research Vessels Both meteorological and oceanographic data (SST) Main interest on meteorological data CORIOLIS collect data from french research vessels (objective is to enlarge to european vessels) oceanographic data (SS-SSS) and meteorological data Main interest on oceanographic data –=> data exchange between the 2 projects –=> an pilot experience could be started on a SAMOS research vessel and on Atalante – => Coriolis ‘s Interest is on getting new data, receiving feedback on meteorological data quality –=> Gosud interest is obvioulsly to have access to new data Meteorological are available for about half of these locations

SAMOS-GOSUD Meeting. Boulder 2-4 May Directions for potential collaboration (2/5) Meteorological data Wet bulb temperature Sea Surface temperature Humidity Atmospheric pressure Dew Point Precipitation rate Solar Radiation True wind Speed and direction Apparent Wind Speed and direction Coriolis has no experience on QC such data and it is not our 1st objective to process them but they are available. Some of these parameters are transmitted on the GTS Parameters recorded on Coriolis research vessels Oceanographic data Sea Surface temperature Conductivity Water tank temperature

SAMOS-GOSUD Meeting. Boulder 2-4 May Directions for potential collaboration (3/5) Access to new sources of data (2/2) Coriolis is involved in the OceanSites project as a GDAC OceanSites relates to Open Ocean moorings and long time series and monitoring They are regular ship cruises planned for moorings maintenance Access to data collected by the vessels when they cruise to the moorings could also be an interesting way to investigate for potential collaboration Cruises data are full part of the OceanSites Project

SAMOS-GOSUD Meeting. Boulder 2-4 May Directions for potential collaboration (4/5) Share the data and distribute them (1/2) As the objectives of the 2 projects are quite different, it seems reasonable that: Meteorological data go to SAMOS Surface ocean data go to GOSUD The issue: to ensure that meteorological data and ocean data that are transmitted together, then splitted can be reconnected unequivocally Proposals: We have to define a common agreed unique tag based on the data (as it is already done within GTSPP) or based on the files transmitted (could assign a ship day tag: WMO/date) Data could be shared between the 2 projects through 2 DODS Servers –GOSUD data available on a DODS server as well as all the data hosted by Coriolis – In this scheme the GOSUD and SAMOS sites are not mirror sites. Is there a need for a final archiving centre or at least a common access to the data. To be also defined

SAMOS-GOSUD Meeting. Boulder 2-4 May Directions for potential collaboration (5/5) Share the data and distribute them (2/2) Coriolis has an experience on ocean data routine insertion on the GTS (Global Transmission NetWork). If we plan to receive the ocean data from SAMOS, Coriolis propose to do that for SAMOS data (if not yet done)

SAMOS-GOSUD Meeting. Boulder 2-4 May Summarizing Share the data between our 2 projects seems to be the 1st obvious step: Meteorological data « against » Ocean data Find an easy way to access collocated meteo and ocean data Define a data structure for that Which may include a common format or at least a compatible format As a conclusion for a SAMOS / CORIOLIS collaboration Routinely collecting data on research vessels is very valuable because Ships tracks are far from merchant routes Data are of high quality (because of being acquired by specialised staff) Sharing those data is important and using them as much as it is possible is also important. Feedback to the data originators must be done each time it is possible Another message : Coriolis is open to a collaboration for a centralised in situ ocean data access for satellite validation purposes

SAMOS-GOSUD Meeting. Boulder 2-4 May Contacts: