Class: QualityElement(child of SurfaceWaterBody)
- Please include here any comments which apply to all the schema elements in this Class.
- In addition to those general schema element level comments, we welcome your views on: a) whether you think this Class can be simplified; and b) whether you think the linkages with other reporting Classes or Schemas can be improved, and how;
Previous comments
In order to simplify the reporting, we suggest to:
Also we suggest that the structure of this table be similar to the one from the WISE – 1stRBMPlan (SWEco_StatusorPotential) where the information was presented in the column and not in the rows in order to be easier for visualing and tracking.
GENERAL COMMENT
In order to better understand and use the database, the quality or optimization of the database design must be sacrificed a little, giving more weight to its logical understanding.
The concepts of the WFD: Ecological status SW, Chemical status SW, Quantitative status GW, Chemical status GW should have a similar treatment in the database.
In this case the class QualityElement for SW EcoStatus should be equivalent to SWPrioritySubstance for SW ChemStatus.
In the case of GW the equivalent classes should be GWPollutant for GW chemical status and an equivalent class for GW quantitative status that doen't exist as the information related to quantitative satatus is directly stored in the class GroundWaterBody.
The design is not incorrect but really difficult to be undestood.
It is required to “select in turn each of the quality elements”; not only the relevant QE at SWB level.
We suggest to simplify this Class - only the QEs, relevant for the SWB-type, to be reported ( to avoid the reporting of “not applicable” QEs - for BG Danube RBD these records form 31,5% out of all 4864 records).
Surface water bodies classified by grouping should not be included in this Class that should be compiled only for monitored quality element. The status derived by grouping should be assigned to the surfacewaterbody and not to each QE.
We can keep it as it is, since we just pull the data from the database, though we get many rows - 536598 in all