1. Meeting on ODV QC and DIVA Products
EMODnet Chemistry
Meeting on ODV QC and DIVA Products
Paris Sept 3rd 2014
SMHI – Baltic Sea
Technical Meeting, Sept 3, 2014 Paris, France 1

2. SYNTHESIS OF ODV USE FOR REGIONAL QC
EMODnet Chemistry
SYNTHESIS OF ODV USE FOR REGIONAL QC
Data set aggregation.
We want to implement the “SDN Aggregated ODV Collection” method. However all P01 codes are not yet mapped to P35.
A definition of common methodologies for QC is much desired.
We would like it to include common use of ODV built in methods for QC as well as guidelines for of how to implement the “QC-parameter_list” provided by Matteo.
Also the following questions should be answered:
Which flag are we using for which quality control, for example QF3 contra QF4 in “QC-parameter_list”?
Exactly what information is to be included in the QC report/Annex (flag from/to, reason for flagging etc.)?
Technical Meeting, Sept 3, 2014 Paris, France

3. INTERACTION WITH DATA PROVIDERS
EMODnet Chemistry
INTERACTION WITH DATA PROVIDERS
Latvia One profile with spike in pH. Mail conversation with LHI. Fault due to mistyping. Profile corrected.
Denmark 22 profiles with position (0,0) and 4 with bad values. Mail conversation with DMU, which is investigating it.
Finland Two profiles with bad values. Mail conversation with FMI, which is investigating it.
Russia 9 profiles with bad values. Mail conversation with RIHMI-WDC, which will update the files. If values matches the original documentations no changes will be made.
Germany Several bad profiles. Mail conversation with BSH, which explained that the reason is that two profiles are taken at slightly different times had been merged together during export. This should be fixed by now. Two bad profiles (salinity) from Pangaea. Mail conversation with BSH and Pangaea. The files are archived by Pangaea, which asked US to inform the PI. was sent to the PI expressing our wish to update the files. He is looking into it.
Poland Five profiles with bad values. Mail sent to IMWN MB. No response on progress yet.
Estonia profiles with missing depth variable were excluded from the ODV collection and never checked. Mail conversation with MSI about issues regarding mismatching header and semantic header have been sorted out and hopefully the files will be correct in the next harvest. Furthermore some profiles did not have any depth profile. Only min and max depth was included in the ODV-files. This should also be fixed by now.
Technical Meeting, Sept 3, 2014 Paris, France

4. EMODnet Chemistry DIVA PRODUCTS
We would like a general protocol with the basic options and setting and a guide with tips and remarks for regional specific setting.
In the DIVA var_list: Aggregated_pH have been analyzed as Aggregated_Phosphate. Hence, the parameter names in the var_list must be unique to avoid confusion during data extraction.
The results must be masked when error fields are too high. How big errors should be accepted?
Must the limits be parameter specific?
Can someone explain relative error and actual errors?
Should we have different error expectations for different parameters? How handle this within the project?
Technical Meeting, Sept 3, 2014 Paris, France

5. EMODnet Chemistry DIVA set-up
Year list: 1990 – 2012
Month list: January-February, July-August
Contour depth: 0, 20, 50, 100 meters
Qf list: 1,0,(7)
Ispec (error output) : 101, (clever poor man’s error)
Ireg (background field): 1
Driver set-up?
Technical Meeting, Sept 3, 2014 Paris, France