mors annual report 1984 2015
play

MORS Annual Report 1984-2015 (document 4-4) Minna Pyhl, HELCOM - PowerPoint PPT Presentation

MORS Annual Report 1984-2015 (document 4-4) Minna Pyhl, HELCOM Secretariat MORS EG 7-2017, Tallinn, Estonia, 2-4 May 2017 MORS Environmental data 1984-2015 Document 4-4 contains the basic graphs for verification of the MORS


  1. MORS Annual Report 1984-2015 (document 4-4) Minna Pyhälä, HELCOM Secretariat MORS EG 7-2017, Tallinn, Estonia, 2-4 May 2017

  2. MORS Environmental data 1984-2015 • Document 4-4 contains the basic graphs for verification of the MORS environmental data of 1984-2015. Data for 2015 has been included as far as reported by 4 April 2017 (noting that the reporting deadline was September 2016) • RU and LV submission of 2015 data was not received before 6 April 2017  Russia informed the Secretariat about preparation of 2013- 2014 data during 2017. • The updated database will be made available in HELCOM website (http://www.helcom.fi/baltic-sea-trends/data-maps/sea- environmental-status/radionuclide-concentrations/) for the contracting parties and the public after the verification. The used data format is MS Access database (accdb).

  3. QA of historical data • IAEA-EL has identified discrepancies and errors in the historical data of the MORS database when transferring to MARIS • The discrepancies/errors require checking and corrections with data providers. • The table in document 4-4 outlines the discrepancy/error and suggested actions to be taken by HELCOM Secretariat as data host of MORS environment database after MORS EG 7-2017 meeting • The Meeting is invited to consider and discuss the suggested actions for correcting the historical contents of the database and mandate the Secretariat to make the corrections. Name 5/3/2017 Surname 3

  4. Discrepences & suggested actions (1) Identified issue IAEA-EL quality assurance Suggested action Table BIO01, DW%, all records. The data type should be Secretariat to change data type to Number as detailed in the HELCOM-MORS guidelines, not Text Number and verify decimals which it currently is. Additionally, a comma is used as the decimal point, when a point should be used. Table BIO01, DW%, BSSSI2004012, 14, 15 & 17 are impossible Check the values with data provider numbers, maybe they are missing a decimal point. SSSI (Sweden) Table BIO01, HELCOM_SUBBASIN, BVTIG2010038, 9 have Secretariat to assign correct HELCOM entries of 0, which isn’t a valid HELCOM subbasin category. subbasin IDs Table BIO01, RUBIN, BVTIG2010054. I think there is a typo Secretariat to correct RUBIN code with this RUBIN code and should be ENGR EN C (RUBIN_ID 37). Table BIO01, RUBIN, 26 records have the Rubin code of MERL Secretariat to correct RUBIN codes MNG. Should these be MERL MER following the list of Rubin names in the HELCOM-MORS guidelines? Table BIO01, MONTH, BSTUK2011004, has an entry of 22, Secretariat to correct month should this be 11 following the date in the Date field? accordingly (11) 5/3/2017 4

  5. Discrepences & suggested actions (2) Identified issue IAEA-EL quality assurance Suggested action Table SEA01, LONGITUDE (ddmmmm), WSSSI2011001-008 and Secretariat to correct decimals WSTUK1998023-24 have a missing decimal after the degrees. Table SEA01, DATE, 188 records have a null entry, but could be Secretariat to populate date fields populated using the year, month, day fields. accordingly Table SEA01, MONTH, there are 31 entries of zero (0), not a Secretariat to populate month fields valid entry. accordingly, if available. If required contact data providers. Table SEA01, DAY, there are 38 entries of zero (0), not a valid Secretariat to populate day fields entry. accordingly, if available. If required contact data providers. Table SEA01, SALIN, WDHIG1998072, record is unrealistic Secretariat to check the values with (99.99). data provider WDHIG (Denmark) Table SEA01, TTEMP, 41 records have a temperature of 99.9, Secretariat to check the values with which are most likely incorrect. data providers Table SED01, DW%, has 198 values greater than 100%, which Secretariat to check the values with are unrealistic. data providers 5/3/2017 5

  6. Discrepences & suggested actions (3) Identified issue IAEA-EL quality assurance Suggested action Table SED01, SEDI, SDHIG1998244-8 have sediment types of 13, which Modify MORS guideline to be isn’t listed in the sediment type table of the HELCOM-MORS in line with sediment code list guidelines, but is listed in the SEDIMENT_TYPE table. in the database Table SED01, OXIC, 325 records are reported as a zero (0) when the Secretariat to check the values only valid entries should be the letter ‘A’ or ‘O’. with data providers Table SED01, DATE, 182 null records, 1 of these records Secretariat to check the dates (SLVEA2011019) could be updated with the records from the with data providers year/month/day fields, leaving 181 records with null dates. Table SED01, SEDI, SLEPA2015007 sediment type 73 is not a valid Secretariat to check the value entry. with data provider (Lithuania) Tables BIO02, SEA02, SED02, METHOD, many records have incomplete Check the values with data entries that do not link to the ANALYSIS_METHOD table. providers BIO02, BASIS, there are 25 records with “F”. This is not listed as an Secretariat to check the values option in HELCOM MORS guidelines (p30). with data providers BIO02, < VALUE_Bq/kg, there are 151 records with erroneous spaces. Secretariat to correct the errors, if needed check the values with data providers 5/3/2017 6

  7. Discrepences & suggested actions (4) Identified issue IAEA-EL quality assurance Suggested action SED02, < VALUE_Bq/m2, SSSSI2010006,7. There are erroneous Secretariat to correct the errors, if spaces in the fields. needed check the values with data providers SED02, < VALUE_Bq/m2, There are 20 records with values of 1- Secretariat to correct the errors, if 5, when the only valid entry should be “<”. needed check the values with data providers SED02, NUCLIDE, there are 25 entries with a nuclide of Bs-212 Secretariat to correct nuclide (should be Bi-212). This nuclide is missing from the NUCLIDE table. RUBIN_NAME, RUBIN_ID 18. It seems the scientific name Secretariat to review rubin code list doesn’t exist (ENCHINODERMATA CIM), even if E N CHINODERMATA is spelt conventionally. Any ideas what this species is supposed to be? The list of Rubin codes in the HELCOM-MORS guidelines. Secretariat to review rubin code list Should LAMI SACA be LAMI SAC? The latter will match the Rubin code convention (4 letters space 3 letters) and also match the records in BIO01, BBFFG1987150, BBFFG1988021, BBFFG1997017. 5/3/2017 7

  8. 5/3/2017 8

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend