Water Framework Directive WISE

Items on which to report progress oFinalising schemas for 2005 reporting oDevelop WISE Web site for 2005 oDevelop a tool to assist in 2005 reporting oVisualisation oGenerating a map for 2004 reporting oIncorporate inter-calibration into WISE oReview of ReportNet

Web site 2005

Only Minor changes oWeb site oChanged to enable upload of 2005 data oSlight changes but basically the same oJust enables different data to be loaded

Logon screen

RBD submissions

Supporting documents

Schema download

Access based tool to support 2005 submissions

2005 Reporting Tool Access 2000 –Discussed with GIS Activity 1 Group –Confirmed with DG ENV at reporting steering group Table definitions to match schema requirements Data may be uploaded directly to tables –SWB, GWB and Protected Areas from GIS or similar –Forms interface for RBD summary data

2005 Reporting Tool Forms –Enables data for the RBD to be entered –One form per Reporting sheet –No field validation Run as batch on each form –All edits automatically saved –Can create XML files for upload RBD, SWB, GWB and Protected Areas

RBD Form

River Basin District Form

SWB1 - Typology of Surface Water Bodies

SWPI1- Summary of Significant Pressures on Surface Water Bodies

Generate XML files

Schema development

Schema work carried out Schema issues discussed with GIS Activity 1 Group 10 th March st draft issued to member states for comment 22 nd March 2005 Some comments received –From GIS Activity 1 Group members –Compiled into schemas issue log Reviewed 13 th April 2005 –Close for comments 26 th April 2005

2005 Reporting Requirements Schemas 4 reporting schemas defined –RBD.xsd RBD summary information Split by reporting sheets –SWB1, SWB2, SWB3, SWPI1 – SWPI9 –GWB1, GWPI1-GWPI11 (GWPI9 not included as at water body level) –ECO1, RPA1

2005 Reporting Requirements Schemas –SWB.xsd Data for each Surface Water Body lake, river, coastal and transitional water bodies –GWB.xsd Data for each groundwater body –ProtArea.xsd Data for each Protected Area

2005 Reporting Requirements Schemas WFDCommon.xsd Reference schema only - not used for data. All common type definitions, enumerated lists etc Extended to include new definitions, lists etc –E.g. Risk Status Code –1 =Not at Risk; –2 =Possibly at Risk; –3 =At Risk

Metadata and URLs Metadata –a reference to any metadata statements may be provided at the schema level, or at the individual waterbody/protected area level. These metadata statements should be uploaded to the WISE server or made available on the internet. URL, reference to uploaded document, text URLs –A URL may also be provided if wished Requires a valid hyperlink/URL format to be provided. Web-mapping system or further information

Key Comments / Issues ISSUERESOLUTION/OUTCOME Data duplication, e.g RBD.xsd requires number of SWBs. Can be determined from SWB.xsd Facilitates cross-checking Useful for stylesheet conversion for reports as cannot retrieve data from separate files Move all optional elements to bottom of group to support automatic generation. Will restructure so that all mandatory simple elements to top, with optional elements to bottom Issues with following GIS guidance, e.g water body cannot be AWB and HMWB Initially maintain separate elements, now single element with choice Agree codelists, structures etcRisk Status, Importance code, Water Body Type code, pollutant substance structure etc Consider merging all schemas so that all RBD, SWB, GWB and ProtArea data within same file Has advantages but will make submitted files very large so keep separate

Inter-calibration metadatabase

Intercalibration Metadata Integrate inter-calibration site data witinh WISE –Will continue to input/update site data using existing interface Upload XML files to WISE –Processes to validate and convert on GIG and/or MS level Enable site data to be accessed graphically –Selected data –Pre-generated reports and graphs –Data download as.csv or site XML file

Timetable

Next Planned Steps Update WISE site now available for testing –Compile and assess all comments –Implement agreed changes and re-issue schemas by ?? May 2005 –Amend WISE to validate revised schemas –Amend data input and XML generation tool to match revised schemas Make site and tools available for use ?? June 2005 Develop extra requirements –Inter-calibration, –Map of Article 3 reporting