Post a comment on the text below

swPrioritySubstanceCausingFailure - Required. (YesNoCode_Enum)

Indicate if the priority substance is causing failure to achieve good chemical status.

Information on exceedances from ubiquitous substances should be reported.

For substances for which EQS were made more stringent in the 2013 amendment of the EQS Directive (Anthracene, Brominated diphenylethers, Fluoranthene, Lead and its compounds, Naphthalene, Nickel and its compounds and Polyaromatic hydrocarbons (PAH)), exceedances of either the 2008 EQS or the 2013 EQS, or both, should be reported here. Exceedances of the latter should be reported even when swChemicalStatusValue is good on the basis of the less stringent 2008 standards, in order to enable the reporting of swPrioritySubstanceExceedanceType and, if appropriate, of swChemicalExemptionType and swChemicalExemptionPressure. The substances causing exceedances to the 2013 EQSs but not to the 2008 EQSs should also be reported under schema element swEffectStatusNewThresholds. See table at the end of this section of the guidance on different scenarios for these substances and the corresponding reporting values.

Previous comments

  • ES - Spain (invited by kristpet (disabled)) 19 Mar 2019 16:00:57

    We propose to add a new Quality check

    the guidance states:

    If swChemicalStatusValue is ‘3’, at least 1 substance should be reported as ‘Yes’ in swPrioritySubstanceCausingFailure.

    The previous check is insufficient because it only ensures consistency in one direction (from 'SurfaceWaterBody' to 'SWB_SWPrioritySubstance'), but it is also necessary to ensure it in the opposite direction(from 'SWB_SWPrioritySubstance' to 'SurfaceWaterBody'), that is:

    Every surfacewaterbody being reported as ‘Yes’ in this element must be reported as swChemicalStatusValue=‘3’.

    This field swPrioritySubstanceCausingFailure should be='No' if

    • swChemicalStatusValue <>'3' 
    • RO - Romania1 (invited by kristpet (disabled)) 25 Apr 2019 09:27:33

       

      We propose to add a new Quality check

      the guidance states:

      If swChemicalStatusValue is ‘3’, at least 1 substance should be reported as ‘Yes’ in swPrioritySubstanceCausingFailure.

      The previous check is insufficient because it only ensures consistency in one direction (from 'SurfaceWaterBody' to 'SWB_SWPrioritySubstance'), but it is also necessary to ensure it in the opposite direction(from 'SWB_SWPrioritySubstance' to 'SurfaceWaterBody'), that is:

      Every surfacewaterbody being reported as ‘Yes’ in this element must be reported as swChemicalStatusValue=‘3’.

      This field swPrioritySubstanceCausingFailure should be='No' if

      • swChemicalStatusValue <>'3' 

      In our opinion, it is not necessary to add other quality check. Surface water body code is included in both table, so it is enough for quality check.

  • SE - Sweden (invited by kristpet (disabled)) 22 Mar 2019 12:08:28

    It would be easier to have one reporting element for status according EQSD 2008 and another according EQSD 2013

    • HU1 - Hungary (invited by kristpet (disabled)) 03 May 2019 13:56:35

       

      It would be easier to have one reporting element for status according EQSD 2008 and another according EQSD 2013

       

      HU: Agreed, Hungary supports and in addition if new amendments will be adopted than this rule should be consequently applied.

  • BG - Bulgaria (invited by kristpet (disabled)) 22 Mar 2019 14:27:53

    We suggest to change the text, considering the fact that the 2021 chemical status should be assessed according to the 2013 EQS, e.g exceedances of the 2013 EQS should be reported

  • LU - Luxembourg1 (invited by kristpet (disabled)) 19 Apr 2019 12:11:30

    In order to be able to compare the data reported by the MS, it would be helpful do add the information if the PS leading to the failure of good status had been monitored in water or biota (e.g. add a new schema element or add the option "Biota EQS" in schema element "swPrioritySubstanceExceedanceType").

You cannot post comments to this consultation because you are not authenticated. Please log in.