1. WFD RBMP user training 2009 WISE GIS/IT workshop BfG, Koblenz 18/19-05-2009 Jon Maidens, Atkins Danmark a/s

2. Overview

3. Who are Atkins? Commission contract from October 2008 to support reporting on River Basin Management Plans Main activity up until now reporting tools Core team: Jon Maidens Mette Wolstrup Claire Allaway

4. Goals of this mornings session Understanding of the RBMP reporting process Introduction to tools built to support reporting (parallel to user guidance) NOT to go through all the schemas but an overview on how to interpret or get help

5. Context Testing period June - September Schemas and tools available for testing Early support to help set up the information flow Official deadline 22nd March 2010

6. Sessions (I) Session 0: Overview Reporting process Supporting the process Session 1: Schemas Reporting sheets to schemas Understanding the schemas Change of schemas Final schemas Help resources Session 2: XML and MS Access DB Access database Conversion tool

7. Sessions (II) Session 3: QA/QC Rules Desktop validation tool ReportNet Session 4: Workflow Desktop ReportNet Session 5: Reporting GeoData Overview Good practice

8. Sessions (III) Session 6: Support User guidance Online resources Helpdesk Session 7: Phase 2 testing Overview

9. The reporting process

10. Submission workflow EEA/ Commission

11. Schemas

12. Schemas (I) Administrative arrangements (Schema RBDSUCA) Surface Water Bodies (Schema SWB) Groundwater Bodies (Schema GWB) Register of Protected areas (Schema ProtArea) Surface Water and Groundwater Methodologies which is divided into: (Schema SWBMethods for Surface Water Bodies) and (Schema GWBMethods for Groundwater Bodies) River Basin Management Plans and Programmes of Measures (Schema RBMP_POM) There is a WFDCommon schema which provides common elements to the other schemas which is not tested on its own.

13. Schemas (II) WRc CIS Working Group D, WISE GIS Group Reporting sheets do not provide all the technical specifications needed to develop the data exchange formats nor provide guidance to the data provider. These technical specifications may lead, where necessary, to adaptations of reporting requirements in order to facilitate the electronic data exchange. All Reporting sheets agreed with the Member States and involved in the WFD reporting process for 2010 have now been consolidated into ‘Guidance Document No. 21: Guidance for reporting under the Water Framework Directive’

14. Schemas (III) Streamlining of previous Articles 3 and 5 schemas Article 8 schemas – field names and enumeration lists Articles 11 and 13 schemas – translation and expansion of reporting sheets agreed summer 2008 Varying levels of complexity and information requirements

15. Schema testing 2009 First phase of schema testing in February todetermine issues or problems with population of schemas at technical level, such as: Bugs Bugs generated in translation of Reporting Sheets Misinterpretations by MS populating schema Volunteer MS (comments from AT, DE, FR, HU, SE, UK) Appr. 60 comments received Update to schemas made for the second phase and inclusion of Economics reporting sheets

16. Schema reporting RBD level except for RBDSUCA which is at national level

17. What to report? Given the time since 2005 reporting and the process to update and streamline the content of reporting, the Commission expects Member States to update all the information in 2010. Article 8 exception, as long as information not changed

18. Schemas dealing with Administration Areas, Water Bodies, Monitoring Stations and Protected Areas Objects

19. Objects(I) Each Surface Water Body has statuses for Biological, Hydromorphological and Physicochemical Quality Elements (QEs) that can change over time. For each Surface Water Body that fails to reach good status the QE causing the failure (exceedance) should be defined. Surface Water Bodies have statuses for Pollutant, Pesticide and Chemical quality elements that can change over time. For each Surface Water Body that fails to reach good status, the QE causing the failure (exceedance) should be defined together with any exemptions.

20. Objects(II) Each Groundwater Body has a status for Chemical QE that can change over time. For each Groundwater Body that fails to reach good Chemical Status the reason for failure should be defined by recording the chemicals that cause the failure. Each Good Chemical status needs to define the Background levels for the Groundwater Body. Each Groundwater Body has a status for Good Qualitative Status that can change over time. For each Groundwater Body that fails to reach good status, the QE causing the failure (exceedance) should be defined together with any exemptions. A Groundwater body has a set of trend status. These statuses can change over time.

21. Objects(III) Surface Water Bodies and Goundwater Bodies may be influenced by pressures (impacts). Each pressure and impact is of a pre-defined type. Surface Water Bodies and Groundwater Bodies may be linked to a number of Protected Area types

22. Schemas dealing with Methodologies Methods

23. Methods (I) For each River Basin District the method for identifying Surface Water Bodies and Groundwater Bodies is required based on the various categories of Water Body. For each River Basin District the typologies being used for Surface Water Bodies need to be defined. If System B typology has been used then different information is required for each category of Surface Water Body as well as a common definition for “Other System B types”. For each River Basin District the Surface Water Classification methodologies need to be defined..

24. Methods (II) For Surface Water Biological, Hydromorphological and PhysicoChemical Quality Element Classification an entry is required for each Quality Element sub-division, its boundaries and the typologies and intercallibration types that the boundaries apply to. For Surface Water Pollutant, Pesticide and Chemical Quality Elements an entry is required for each Quality Element that is being measured. If the national standard differs from the European Standard then details of the national standard is required. For each River Basin District the Groundwater Classification methodologies need to be defined for each pollutant or indicator that is used.

25. Methods (III) For each River Basin District the methods for identifying Pressures and Impacts for both Surface Water Bodies and Groundwater Bodies must be defined broken down by the Pressure Types. For each River Basin District the methods for applying exemptions for both Surface Water Bodies and Groundwater Bodies must be defined broken down by the various exemption types. For each River Basin District the way in which the results are to be interpreted for Surface Water and Groundwater Body Statuses must be described. For each River Basin District any data gaps are identified for both Surface Waters and Groundwaters

26. Schema dealing with River Basin Management Plan and Programme of Measures Plans

27. Plans (I) A River Basin Districts submits many River Basin Management Plans over time. Each River Basin District Plan defines a number of key dates and describes a Public Participation Schedule. A number of Reference Documents are associated with each River Basin District Management Plan. Each River Basin District must report on their Basic Measures, their Other Basic Measures and declare any Supplementary Measures if they exist. Each River Basin District will declare any high-level Pressures that require Supplementary Measures. None may exist.

28. Plans (II) Each River Basin District declares the specific Basic and Supplementary Pressure that are being applied to each specifically declared Pressure. A Supplementary Measure can embrace more than one Supplementary Pressure and vice versa. All Pressures are of a given Type. A River Basin District Management must define the costs of the Measures broken down into sub-divisions

29. Plans (III) If any Significant Surface Water pressures exist these are defined at a Sub-Unit level for each River Basin District. Load details are required for Significant Point Source and Diffuse Source Pressures. Extraction volumes are required for each Significant Abstraction Pressure. If any Relevant Main Groundwater Pressures exist these are defined at the RBD level. Load details are required for Relevant Point and Diffuse Source Groundwater Pressures. Extraction volumes and details are required for each Relevant Abstraction Pressure. Recharge volumes and details are required for each Relevant Recharge Pressure. Economics

30. Recognising the schema linkages

31. Reading the schemas

32. Structure of information asked for Structure: Simple v complex Data types: String, numeric, lat/long, Mandatory, optional, choice Codes: Defined in WFDCommon or in the schema itself

33. Reading the schemas

34. Guidance Streamlined schema user guidance available online (developed by WRc) Breaks down the schemas by element Associated annotations and enumeration lists Important notes/narrative/explanations/warnings also included

35. Summary Version 2.0 of the schemas available for second phase of testing over June Read the guidance Explore the schemas using a visual tool (e.g XMLSpy)

36. Access database

37. WFD database Databases managed at RBD level Database structure which supports the schemas Organising information for submission XML conversion tool links to database to create XML schemas Import datasets or manual entry

38. Database No forms Database tables Internal keys to hold the information together Portable

39. User support Naming convention Required information marked with asterisk (*) but not enforced Annotations in table field description (character limitation) Faithful to field type and size (exceptions) Code lists

40. Database design

41. Access Database Design

42. Table dependencies

43. Table design

45. Schema to tables

46. Simplifying the structure

47. Database map

48. Manual data entry – levels of data 1 4 3 2

49. Level 4 - Internal IDs for data management Input each previously reported Protected Area code (i.e. previously reported, before March 2010, under other directives). For each newly reported Protected Area input a code and use PROT_AREA schema to provide details.

50. Manual data entry Top down approach Database maintains refential integrity Code lists from parent table to help entry Multiple column code lists at level 4

51. Issues for testing Database design Database size Ease of data import

52. Data update Historic data management Need to maintain linkages Separate schema for submitting

53. Documentation RBMP user guidance will include database diagrams around each schema User guidance

54. XML conversion tool

55. Support for generating the XML Tool which links to Access databases and generates XML files for the appropriate schemas Download and install RBD level Important not to change database structure Independent of database Validation carried out in desktop tool

56. Conversion tool

57. Article 8 schema conversion To allow for resubmission of previous Article 8 reporting added functionality to the XML converter Select one of the three Article 8 schemas and the tool will convert it

58. QA/QC

59. Entry point for those producing their own XML

60. Validation rules Technical level validation ensures that numbers are entered as numbers, no characters; that the XML file is well-formed and so on. Business rule validation handles the more complex relations in the report, e.g. where data is mandatory if and only if other fields have a certain value. The validation rules are meant to ensure data meet the requirements of the reporting sheets. The rules also check that the reported data have the correct format to be stored in the WFD database model.

61. Element types and limits Submitted data needs to conform to the data types that have been used for each element in the schema: String: all characters allowed. Integer: only integers are allowed. Decimal: any number is allowed. Percentage: must be between 0 and 100. Date: must be a valid date in the format yyyy-mm-dd. URL: must be a valid URL format.

62. Required / Conditional / Optional Required: minimum occurrence is set to > 0. Conditional: minimum occurrence is set to 0 (conditional check) Optional: minimum occurrence is set to 0 (and no conditional check)

63. Multiple occurrences Minimum occurrence = 1, maximum occurrence = infinity Minimum occurrence = 0, maximum occurrence = infinity Minimum occurrence = 1, maximum occurrence = n Minimum occurrence = 0, maximum occurrence = n Minimum occurrence = n, maximum occurrences = n

64. Code checks valid codes are selected from the attached codelist defined in the WFD Common schema, or are selected from the enumeration list defined within the element itself e.g. YesNoCode / CountryCodeType / etc.

65. Complex validation checks Conditional Choice check Data structure check Cross-schema check All listed in the RBMP submission user guidance

66. Quality Logical consistency ID management

67. Within schema checks

68. Cross schema checks (I)

69. Cross/Within Schema checks (II)

70. XML validation tools

71. Two options for validation Desktop tool ReportNet

72. Desktop validation tool Installation downloaded Validates the XML files Retrieves schema from ReportNet Accesses QA/QC validation on ReportNet Same checks and output as ReportNet

73. Desktop validation tool

74. Click on the links for details

75. First check format

76. Second check – QA/QC rules

77. ReportNet Workflow

78. ReportNet validation – first check

79. ReportNet validation – second check

80. Cross/within schema checking Initiated from separate button in CDR Checks all submitted schemas

81. ReportNet

82. CDR: Central Data Repository Submission at country level for a specific obligation One obligation for WFD RBMP reporting Password protected – upload by designated MS focal point only

83. CDR Workflow Upload Validation performed (dependent schemas) Overwrite to correct errors Close envelope on completion Manual check by EEA/Commission Resubmission to correct (full submission only)

84. CDR Workflow

95. CDR Workflow resubmissions If envelope not released, overwrite previous submission. If envelope closed, create new envelope [RBD]_resubmission Use same file name as file replacing [country code]_[RBD]_[schema]_[date].xml Remember: full submission only Release envelope on completion

96. Envelope management RBD level reporting Envelopes will be pre-created One envelope for national level schema

97. Workflow testing CDR test area ReportNet envelope management Guidance document ReportNet QA/QC validation (cross schema checking) Closing of envelopes Letter generation

98. Reporting GeoData

99. Spatial information reporting (I) Features NOT points River Basin Districts (RBDSUCA.xsd) Sub-units (RBDSUCA.xsd) Surface Water bodies (SWB.xsd) Ground Water bodies (GWB.xsd) Protected areas (ProtArea.xsd)

100. Spatial information reporting (II) All objects defined in the schema will be present in the spatial dataset Attribute information for these spatial objects are defined in the associated schemas and attribute information should only be reported against the schemas

101. Spatial information reporting (III) Shapefile format (mandatory fields) Upload to same ReportNet folder Follow the naming convention [Country ID]_[River Basin District ID]_[Feature set name]_[Date] Positional accuracy for reported data should be better than 125 metres (1:250 000) and a maximum of 500 meters (corresponding to a scale of 1:1.000.000) ETRS-89.

102. Protected areas The WFD includes the following types of protected areas: Areas designated for water abstraction Areas designated for protection of economically significant aquatic species Recreational waters Nitrate Vulnerable Zones Special Protected Areas For the purposes of submission a separate layer (shapefile) should be provided

103. Quality checking Completeness Logical consistency (in schema QA/QC) Topological consistency specific to WFD General topological consistency

104. Logical consistency A water body can only be assigned to one RBD A monitoring station must be assigned to a least one water body A RBD must have at least one subunit (if MS doesn’t report subunits) can RBD be used as subunit Groundwater bodies must be assigned to only one RBD (even if they have parts outside of the respective RBD); Associated monitoring stations must be located within the boundaries of the respective groundwater body.

105. Topological consistency The objects of one type should be positionally consistent with spatial objects of related types. Reported elements should be considered as reference data and geometric consistency with other themes may be achieved if these other themes use the reported data as background data during the production or the validation of their own data, e.g. River Basin Districts. Groundwater bodies Groundwater bodies need not cover the entire territory of a country; Groundwater bodies CAN overlap; Overlapping groundwater bodies must not intersect if groundwater bodies lying upon each other are reported within one file

106. Topological consistency (II) Surfacewater bodies Rivers, lakes, transitional and coastal areas CANNOT overlap Rivers must not intersect (nodes at intersections) Rivers, lakes and transitional and coastal areas must be covered by subunits Rivers and lakes CANNOT overlap with coastal waters or transitional waters Outlet of each river must touch coastline A coastal area must not have gaps Coastal area must touch transitional waters, national boundaries or subunits RBD and subunits CANNOT overlap and have no gaps RBD and subunits must cover the extent of the MS RBD must contain at least one river The coastal areas must not be larger than one nautical mile from the coastline

107. General topological consistency Overlaps, overshoots, undershoots, slivers to be avoided. GIS software topology validation checks should be performed for connectivity issues before uploading the geometry files.

108. Data harmonisation Across data themes Across national borders WISE follows Inspire Hydrography data specification guidance

109. Centroids Data files in the reported xml schemas are related to the centroids for the associated spatial object types: Surfacewater bodies Groundwater bodies Protected areas Reported centroids are to be consistent with the reported spatial data set Quality check – reportnet tools

110. ID management and life cycle The location of a point features changes (e.g. if a monitoring station is moved upstream or downstream); threshold 125 m in accordance to the positional accuracy recommended for GIS datasets (according to the scale 1:250,000); The location or length of a line feature changes (e.g. if a river water body is divided or merged with another); The location or size of a polygon changes (e.g. if a River basin District is divided or merged with another).

111. Life cycle schema

113. Metadata Complete metadata information for each shapefile is needed in order to adequately describe the file, its contents and its origin.

114. Resources WISE GIS guidance on circa Shorter GIS reporting guidance

115. Documentation

116. Support documentation Schema user guidance Reporting user guidance: Access tool help XML Conversion tool Desktop Validation tool QA/QC validation tool help ReportNet workflow GIS reporting guidance

117. Online resources

118. Obligation and information http://rod.eionet.europa.eu/obligations/521

119. Support files online

120. Testing summer 2009

121. Phase two testing objectives Schemas Submission workflow Database to XML conversion tool XML validation tool Documentation Suggestions!

122. Phase 2 testing Scheduled to start in beginning of June Schemas available for download Help desk contact Supporting documentation and tools online Register so can be set up on ReportNet

123. Testing support Help desk (helpdeskWFD@atkinsglobal.com) Specific dialogue where appropriate

124. Capturing any issues Log What was tested and by whom What the problems were Actions required: i) schema change ii) documentation change iii) other action Reviewing the schema test data

125. Finally Just try the tools with a test database

126. Notification Email helpdeskWFD@atkinsglobal.com if wish to participate in 2. testing phase and receive notifications when tools and documents are ready Questions?