1 / 21

PFRA Reporting Drafting Group Meeting Output Summary

Summary of the key outcomes from the PFRA Reporting Drafting Group meeting including database structure, test phase details, tools to be tested, user guides, clarification questions, and next steps.

mrosie
Download Presentation

PFRA Reporting Drafting Group Meeting Output Summary

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. PFRA reporting – Output from 2. test phase FD Drafting Group, Meeting 15-16 June 2011 Mette Wolstrup

  2. Revisedstructure - a quick go through

  3. Database structure

  4. Test phase – kick off • Email sent to MS 12.05.2011 - 4 weeks testing • Volunteer MS: AT, CZ, ES, FI, IE, PL, SE, UK

  5. Tools and documents to be tested • Database/schemas • Database to xml conversion tool • Desktop validation tool • User Manual, v3.0 • User Guide to the reporting schema v3.0 • User Guide to reporting spatial data v3.0 • Stylesheets • Upload in cdrtest and QA's • Ressource page: http://icm.eionet.europa.eu/schemas/dir200760ec/resources/

  6. Outcome

  7. Clarification questions • Variousclarificationquestionsonhow to interpretdifferent elements in the schema • FI: How to reportifno events in UOM?

  8. Database • UK: Re-introduction of the asterix (*) • AT: Incorrect annotation text • IE, ES: Redundant data in database

  9. PFRA Schema • UK: Should have a default value under each type of potential consequences. • UK/PL: How to use the two elements 'CrossBorderRelationship' and 'CrossBorderFloodLocationCode' • ES: EUSurfaceWaterBodyCode? • FI: Name of flood location shouldbeadded

  10. PFRA Schema (2) • UK: Type of floodsontwolevels? • AT/PL: How to useflood location? • PL: Currency of damageestimates? • FI: Degree to beremoved from - Degree_TotalDamage • - Degree_TotalDamageGDP • - Degree_TotalDamageClass

  11. APSFR • UK: Change annotation text in element 'SummaryofCoordination'? CONDITIONAL. To be provided if article 4 and/or 13.1.a have been applied and if APSFR is part of a international APSFR. Optional for article 13.1.b. Description (less than 5,000 characters) of international coordination that has taken place between relevant MSs within international RBDs or international units of management

  12. Database to xml conversion tool AT/UK/PL: All experienced problems with the DB to xml conversion – ghost tags and mapping levels – Atkins to correct the conversion tool.

  13. Upload files in test environment,QA's, factsheets FI: No errors in the upload work flow FI/UK: Some incorrect complex validations – will be corrected by Atkins UK: Factsheet - Suggestion to have flood type/consequence names instead of codes

  14. Ressource page http://icm.eionet.europa.eu/schemas/dir200760ec/resources/ SE: Missing links (corrected) UK: Various comments on all 3 guidance documents – will be incorporated.

  15. Next step

  16. Timetable 1. and 2. test phase closed Release of final schemas and tools – 1 July 2011(tentative) 22.12.2011: Deadline for finalising PFRA 22.3.2012: Deadline for reporting PFRA

  17. Thank you Mette Wolstrup GIS & ITATKINSArne Jacobsens Allé 17, 2300 Copenhagen S, Denmark | Tel: +45 5251 9000 | Fax: +45 5251 9001 | Direct line: +45 5251 9110 | Mobile: +45 2711 1295Email: Henrik.Kaltoft@atkinsglobal.com | Web: www.atkins.dk

More Related