1 / 21

WFD 2015 Schemas

WFD 2015 Schemas. Andres Stæhr Bastholm. WFD 2015 Schemas. Agenda Status of the WFD schema development What are the main changes? Simplification of schemas Re- deliniation of Water Bodies Challenges: direct links between main elements

egil
Download Presentation

WFD 2015 Schemas

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WFD 2015 Schemas Andres Stæhr Bastholm

  2. WFD 2015 Schemas • Agenda • Status of the WFD schema development • What are the main changes? • Simplification of schemas • Re-deliniation of Water Bodies • Challenges: direct links between main elements • Pre-requisites for a smooth 2015 electronic reporting (including QA procedures)

  3. 1. Status of the WFD schema development

  4. Status of the WFD schemadevelopment

  5. What is next step? • Schemasare the backbone of the electronicalreporting WFD2 Master DB Technicalguidance doc(s) Schemas INSPIRE Desktop ValidationTools Reportingtool XML ConversionTools

  6. 2. What are the main changes in the 2015 schemas?

  7. Whatare the mainchanges? • General trend of 2015 reporting: • More data – less text • GIS data for all water bodies • Implications for schemas: • Simplification of the schemas • Option for re-deliniation of Water Bodies with link to previous WB • Enable many-to-many relations between Impacts and Pressures

  8. 2.1 Simplification of Schemas

  9. Simplification of 2015 schemas • Schema elements deleted • No summary texts • Use of references to background documents • Use of closed lists and targeted questions • Harmonization of lists across DPSIR chain (Drivers, Pressures, Status, Impacts, Response) • Schemas will have a simpler structure

  10. Example of a schema sketch

  11. 2.2 Re-delineation of Water Bodies

  12. Re-delineation of Water Bodies Links to previsousWB's to mapchanges

  13. Re-delineation of Water Bodies Example of dis-aggregatedWB's (DrentseAa) EUSurfaceWaterBodyCode: NL33DA NL33DA1 NL33DA2 NL33DA3 Introduction of 3 new WB codes in database

  14. Re-delineation of Water Bodies Example of aggregated WB EUSurfaceWaterBodyCode: NL33DA NL33DA1 NL33DA2 NL33DA3 1 new WB codewith links to 3

  15. Re-delineation of Water Bodies Re-redelineation of WB's in Schemas

  16. 2.3 Links between the main elements

  17. Links between the main elements RBD WB WB

  18. Enablemany-to-many relations betweenPressures and Impacts Many-to-manyrelationship

  19. 3. Pre-requisites for a smooth electronical 2015 reporting

  20. Pre-requisites for a smoothelectronicalreporting 2015 • Feed back from MS: • Electronical reporting is cumbersome • Many tools, guidance documents and reporting steps • Complicated validation process • Web page: • Resource page should be directed towards the 2015 reporting • Optimally 1 guidance document, 1 tool, 1 validation step • How to improve QA process: • Validation tool should stop the data • Content and technical person should sit together

  21. Thank you very muchandres.staehr.bastholm@atkinsglobal.com

More Related