Home

Floods reporting workflow user manual v5.0

1. FloodLocationCode EUSurfaceWaterBodyCode PFRA_TypeofConsequence b U1 UNIQUECODE Consequence gt O H FK1 11 FloodEventCode TypeofConsequence OtherConsequenceDescription Degree TotalbDamage Degree TotalbamageGDP Degree TotalDamageClass OtherDamageDescription Summary UNIQUECODE Consequence Fatalities FatalitiesDescription Link to CAUOM table can only be established if the EJUOMCode has been reported in the CAUOM schema Floods reporting workflow user manual v5 0 PFRA tables linkages PFRA_ArticleApplied EUUOMCode ArticleApplied OverallApproach PastAdverseConsequences SignificantAdverseConsequences PotentialAdverseConsequences LongTermDevelopments IssuesArticle4_2 d NotConsideringlssuesArticle4_2 d OtherRelevantinformation InternationallnformationExchange ArticleApplied FloodEventCode TypeofFlood PFRA_FloodEvent FloodLocationCode FloodEventCode NameofFloodEvent CategoryofFlood DateofCommencement DurationofFlood Area Length Recurrence Frequency OtherRelevantinformation SsummaryFloodEvent PFRA AssociatedFloodLocations FK1 11 FloodEventCode FloodLocationCode schemaName METADATA URL UNIQUECODE FloodTypes PFRA_SpecificArea ArticleApplied opecificAreaCode NameofSpecificArea UNIQUECODE_FloodTypes OtherDescription Attributes shall be filled with the required informati
2. asc He 1 pire Use the H button to create a new record If you do not select this then the current record will be overwritten Floods reporting workflow user manual v5 0 21 ATKINS 4 Creation of xml files The DB to xml conversion tool 4 1 Concept The purpose of the DB to xml conversion tool is to allow Member States to generate the required xml files from their own data without any prior Knowledge of xml formats and standards However database knowledge including MS Access and advanced data transformation skills are still needed to use the conversion tool The tool extracts the data from the tables in the Access database back end described in Section 2 and generates the schema This tool does not carry out any validation of the data that is used to create the xml files nor does it validate the xml file produced Validation is performed with the desktop validation tool and or in ReportNet as described later in this document Please note that the xml conversion tool will only function with the database structure which has been built specifically in the FD Access reporting database as supplied 4 2 Computer Requirements The DB to XML conversion tool requires the following e Windows XP or newer 30 MB of free hard disk space and an 800x600 monitor minimum e Microsoft NET Framework 3 5 SP1 or higher If NET 3 5 SP1 is not already present it will automatically be installed dur
3. Floods reporting workflow user manual v5 0 40 ATKINS 7 1 QA QC Common validation checks The following checks are carried out for all elements within the schema Element types and maximum and minimum limits Submitted data needs to conform to the data types that have been used for each element in the schema The data types are as follows e String all characters allowed The maximum and minimum settings define the maximum number and minimum number of characters that are allowed e Integer only integers are allowed The maximum and minimum values define the maximum and minimum values that are allowed e Decimal any number is allowed The maximum and minimum values define the maximum and minimum values that are allowed e URL must be a valid URL format Required Conditional Optional elements The data within the schemas may be Required Conditional or Optional for the purposes of automatic validation The logic for determining whether an element is considered to be Required Conditional or Optional is based on the minimum number of occurrences defined for that element and whether the element has been designated as Conditional All elements that are Conditional are identified in the table in Appendix B and also in the annotation of the schemas themselves The logic used is as follows e Required minimum occurrence is set to gt 0 e Conditional minimum occurrence is set to 0 and there is a conditional ch
4. PFRA PFRAInformation Article4Applied FloodEvents FloodData TypeofFloods Description Error message EUCACode must be unique within the MS Must be populated if WFDCompetentAuthorities are set to N EUUOMCode must be unique within the MS Must be populated if OtherCompetentAuthorities is populated Must be populated if International Y Must be populated if International Y Must be a valid EUCACode in CA_UoM CompetentAuthority Must be a valid EUCACode in CA_UoM CompetentAuthority Must be a valid EUUOMCode in CA_UOM UnitsOfManagement or valid sub unit code EUSubUnitCode ind the WFD RBDSUCA Schema At least one of the elements FloodIinformationArt4 TransitionalMeasuresArt13 1 a or TransitionalMeasuresArt13 1 6 must be populated Must be populated if article 4 and or article 13 1 a has been applied and in the case that A13 1 b is applied for a part of the UoM RBD or for a specific flood type Must be populated if CategoryofFlood past flood Must be populated if CategoryofFlood past flood Must be populated if SourceofFlooding A16 other NS Element name Element root eee Description Error message FloodData TypeofFloods other FloodData TypeofFloods other HumanHealth FloodData TypeofConsequence HumanHealth Other OtherConsequenceDescription PFRA PFRAInformation Article4Applied FloodEvents i eau CulturalHeritage FloodData TypeofConsequence Cult
5. e Access database back end This complements the schemas and organises the information into database tables The database allows for manual entry but also bulk data import can be used depending upon the skill and the needs of the user e Access database front end The front end of the Access database is a user interface that also complements the schemas and organises the information into the back end database tables The front end user interface only allows for manual entry and is only developed for the reporting of the CA and UoM e XML Conversion tool which generates the schemas from the Access database e QA QC rules help ensure the information is filled out correctly The QA QC is run from the following ReportNet Desktop validation tool Schemas The reporting schemas are not dealt with in detail in this document The schemas are available from this web page hittp icm eionet europa eu schemas dir200 760ec resources along with supporting documentation Related documents This is Document 1 providing support for the workflow There are three other documents which provide additional support to the reporting process e Document 2 Schema user guidance http icm eionet europa eu schemas dir200760ec resources e Document 3 Guidance on the reporting of GIS information http icm eionet europa eu schemas dir200 760ec resources e Document 4 Guidance on reporting for FHRM of spatial information http icm e
6. Notific Help The login has been e moved to the upper right corner SEERE Description Activate task Obligations WFD River Basin Management Pian including programme of measures o o OA XM lly on 12 Mar 2009 9 9 allv on 12 Mar 2009 Floods reporting workflow user manual v5 0 Release data xml schema generated from Access DB CA_UoM xml Validate data input and generate error report Error report When errors corrected upload xml file on EIONET and run QA QC and correct errors CA_UoM xml ATKINS 2 2 1 2 2 Access Database back end Back end quick guide A quick step by step guide for the advanced user who has experience in using previous similar reporting databases e Download the Access DB from http icm eionet europa eu schemas dir200760ec resources e Fill in the required information into the relevant tables using the guidance provided in Appendix A e When all the data has been entered into the back end of the database use the xml conversion tool to generate the xml files Download of back end Access database The Access DB will be available for download at http icm eionet europa eu schemas dir200760ec resources and is available in 2000 version All the schemas are designed to contain information at UoM level except for the CAUOM schema which will contain information about all the UoMs within the MS The DB reflects this de
7. XML Floods reporting workflow user manual v5 0 Meaning Definition Area of Potential Significant Flood Risk schema Competent Authorities Competent Authorities and Unit Of Management schema Central Data Repository Database Floods Directive Flood Hazard and Risk Map schema Ground Water Body schema Ground Water Methodologies schema Ground Water Monitoring Stations schema Monitoring schema Member State Protected Areas schema Programme Of Measures Preliminary Flood Risk Assessment schema River Basin District River Basin District Sub Unit Competent Authorities schema River Basin Management Plan schema Surface Water Body schema Surface Water Methodologies schema Surface Water Monitoring Stations schema Unit of Management in most cases the UoM will be the same as the RBD reported in the WFD Water Body Water Framework Directive Water Information System for Europe Extensible Markup Language ATKINS 1 1 1 1 2 1 3 Floods reporting workflow user manual v5 0 Introduction The purpose of this guidance is to provide support to the workflow for the Floods Directive reporting Article 3 4 5 6 and 13 Fundamental to the reporting process are the schemas which have been developed from the reporting sheets All the schemas are available online from EEA s ReportNet To facilitate the submission of information according to the schemas the following tools have been developed
8. e Windows XP or newer e 30 MB of free hard disk space e an 800x600 monitor minimum e Microsoft NET Framework 3 5 SP1 or higher If NET 3 5 SP1 is not already present it will automatically be installed during the installation process However the installation program itself requires at least Microsoft NET Framework 2 0 see section 5 3 Important Running the ReportNet desktop validation tool requires access to the internet Installation uninstallation Installation The ReportNet desktop validation tool can be installed via the internet from the URL below http icm eionet europa eu schemas dir200 760ec resources validationtool Please note that the installation will only run from Internet Explorer not from other browsers e g FireFox googleChrome As described in section 5 2 the installation will automatically include the Microsoft NET Framework 3 5 SP1 if this is not already present However it should be noted that installation of NET requires local administrator access and you may therefore need to contact your system administrator In order to run the installation program itself Microsoft NET Framework 2 0 or later must be installed To determine what versions of the Microsoft NET Framework is installed have a look in the folder C Windows Microsoft NET Framework and if present the versions of the NET framework will be in numbered folders If you do not already have NET 2 0 or higher you are recommended to i
9. eionet europa eu schemas dir200060ec LAT element is invalid The value 15N is invalid according to its datatype http water eionet europa eu schemas dir200060ec wfdcommon CoordinateType The Pattern constraint failed The http water eionet europa eu schemas dir200060ec LON element is invalid The value 43562656 is invalid according to its datatype http water eionet europa eu schemas dir200060ec wfdcommon CoordinateType The Pattern constraint failed The http water eionet europa eu schemas dir200060ec Natural element is invalid The value ArtificialArtificialArtificialArtificialA is invalid according to its datatype String The Enumeration constraint failed The http water eionet europa eu schemas dir200060ec YesNo element is invalid The value B is invalid according to its datatype http water eionet europa eu schemas dir200060ec wfdcommon YesNoCode The Enumeration constraint failed Figure 5 5 example of validation error message You will typically find the first list of errors is not the full list but as you fix things fresh errors are thrown This is because as you fix things more content is added which hasn t been checked previously Floods reporting workflow user manual v5 0 30 ATKINS 5 6 1 Fixing errors requires a lot of detective work but with experience recognition of the cause of errors becomes easier A good practice is not to approach the error list sequential
10. if TypeCulturalHeritage B33 Other Must be populated if TypeEconomicActivity B45 OtherConsequenceDescription Other MediumScenario FloodRiskMap ExposedElement Environment EnvironmentalConsequences FHRM FloodHazardMaps HazardArea OtherConsequenceDescription QuantitativeLikelinood MediumProbability MediumScenario FloodRiskMap ExposedElement FHRM FloodHazardMaps HazardArea QuantitativeLikelinood HighProbability HighScenario FloodRiskMap ExposedElement EconomicActivity EconomicActivityConsequence FHRM FloodHazardMaps HazardArea QuantitativeLikelinood HighProbability HighScenario FloodRiskMap ExposedElement Environment EnvironmentalConsequences FHRM FloodHazardMaps HazardArea OtherConsequenceDescription QuantitativeLikelinood HighProbability HighScenario FloodRiskMap ExposedElement Must be populated if TypeCulturalHeritage B33 Other Must be populated if TypeEconomicActivity B45 OtherConsequenceDescription Other OtherConsequenceDescription Must be populated if TypeEnvironment B24 Other Must be populated if TypeCulturalHeritage B33 Other Floods reporting workflow user manual v5 0 53
11. reported in the CAUOM schema Floods reporting workflow user manual v5 0 46 ATKINS A 4 FHRM tables linkages Medium Probability used as example Attributes Schema name EUUOMCode CreationDate Summary1 Creator Summary2_CoastalAreas FHRM_Summary Summary3_1 Summary3_2 Summary3_3 Summary3_4 Summary3_5 Summary4 Summary5 Summary6 Description GeneratedBy ClassificationCode FHRM_Otherinformation EUUOMCode Hyperlink DescriptionLink Email Summary2_GroundWaterSources FK1 11 Language Summary2_Article6_6AndOrArticle6_7 FHM_UniqueCode EUUOMCode APSFRCode SourceofFlooding OtherSource FHM_UniqueCode Article6_6AndOr6_7Applied DescriptionofProbability Frequency Recurrence ProbabilityofOccurence FHRM_MedProbinhabitantsAffected d Bee a I 1 I 1 I 1 I 1 I 1 I 1 I FHM UniqueCode i OverAll_InhabitantsAffected 1 I 1 1 1 I 1 I 1 I i I 1 I 1 I 1 Day Night TransitoryPopulation OtherPeople FHRM_MedProbEnvironmentTypelED FK1 11 FHM_UniqueCode TypelEDInstallation NaceCode FHRM_MedProbOtherConsequences FHM_UniqueCode TypeofPotentialConsequence ExplanationPotentialConsequence FHM_UniqueCode TypeCulturalHeritage OtherCulturalHeritageConsequenceDescription Floods reporting workflow user manual v5 0 FHRM_MedProbldentifier_HMP FHM_UniqueCode EU_CD_HMP Attributes shall be filled with the requ
12. specific element please look in either the User Guide to the reporting schema v4 0 or the Access database Back end database design Mandatory data A large number of fields are required in order to ensure that the submission can be processed Note that the term mandatory is no longer used in the context of schemas because of possible confusion with mandatory in the sense of legal compliance i e failure to supply mandatory information is legally not in compliance with the directive For all elements in the database it is indicated in the description field whether the element is required optional or a choice NOTE Refer also to the schema to understand which information is required optional or conditional choice The validation tool will indicate any required fields which have not been completed Field descriptions Every table within the database contains detail on what each field means Description and what format of data is required in the field To view these click once on the table and go to Design view This description has been taken directly from the schema annotations but in some cases where the description was too long for the field length the description has been truncated and you should refer back to the schemas themselves Text fields Most of the fields within the DB are defined as text fields and an indication of number of characters allowed can be found in either the description field
13. table design view in the general field settings or in the schema xml file as illustrated below Floods reporting workflow user manual v5 0 11 ATKINS Ne Data Type Description CCR Text Link to table COUNTRY see CountryCode us EUCACode Text Unique EU code for the Competent Authority CompetentAuthorityName Text Official name of the Competent Authority in E CompetentAuthorityNameNL Text Official name of the Competent Authority in N Acronym Text Acronym for the Competent Authority if it ex Auth_CD Text pigere Natiorrareede for the Competent Aut LegalStatus Memo Sum text lt 5000 char offthe legal status of e Street qe Text City Text Official name of city in English CityNL Text Official name of city in National Language Country Te N Postcode Text URL Text asite address of the Competent Authority T General Lookup ne Sag Soe SS lt xs element name Postcode type fd StringS0Type minOccurs 0 gt lt xs element name Roles gt ormat lt xs annotation gt lt xs documentation gt Core Roles undertaken by the Competent Authority A vith the responsibility for either the implementation of the different stages of the Flog Default Value lt xs element gt _ lt xs elem nt name Street type fd String100Type gt lt xs element name Gya mid TTE lt xs element name CityNL type fd String100Type gt lt xs element name Country type fd String100Type gt ycumenta
14. the element CategoryofFlood in the PFRA schema is populated with past flood then element DateofCommencement is then required and must also be populated Conditional fields are clearly marked within the schemas themselves with the word CONDITIONAL at the start of the description It is important to understand which fields are conditional and therefore what other fields become required once a conditional field is populated This will help you avoid validation errors Choice checks In some cases there is a choice of what to report For instance it is mandatory to provide either length of length of inundated river stretch OR inundated area This is marked in the schemas by the symbol in In Figure 2 4 The Choice check is required in order to ensure that an element has been populated where a choice of attached elements is provided In all cases where an element requires a subsequent choice to be made from a series of attached elements the choice options are set to minimum 1 and maximum 1 i e the validation routine should check that only one of the attached elements has been chosen and populated For example in the PFRA schema one of element Area or Length must be populated but not both Floods reporting workflow user manual v5 0 14 ATKINS FloodData i a type z vr Extent of land inundated Indicate the total area in kroz l type fd NumberDecimalType Inundated length of river stret
15. tool bar in the upper right corner 5 5 2 Viewing an XML file To view an xml file click the View XML file button see Figure 5 1 and browse to the relevant xml file you wish to view When OK is clicked the tool will use the valid schema definition to retrieve the possible conversions which have been set up for this schema in ReportNet The conversions listed see figure 16 with hyperlinks to View the files if the size of the XML is less then 250kb or to Save the files from where they can be opened using the appropriate application by the user Floods reporting workflow user manual v5 0 29 ATKINS 5 6 _ view file result Ioj x AML file D V rticle 13Mestdata vconversion tool test 4 deploy pa xml Original View Orginal Save xml file HTML Factsheet View HTML Factsheet Save html file Show stations in Google Earth Save kml file Figure 16 Example of desktop translation output Understanding desktop validation output lf errors are reported under the first schema check xml schema validation the line number in the schema where the error was found and a description of the error itself are provided The checks are typically those described in section 5 You should use a text editor or similar viewer which gives line numbers e g Notepad to display the xml schema and systematically work through the error list correcting as you go Some examples of errors are Line Error The http water
16. 000 Yet to be measured 9999 Unknown 5 7 Complex validation checks by element Schema incorrect e g mandatory where conditional Use 7777 for numbers and NA available for text for text If in doubt contact the x schema limitations e g greater than 100 Agree with COM ignore error Incorrect type e g comment in number field FIX comments in number fields will get value 0 The table in Appendix H contains full details of the complex checks that are carried out on elements within the schemas in addition to the technical first validation checks described in the Floods reporting workflow user manual v5 0 34 ATKINS previous section Note Cross schema checks are run as part of a manual process after MS has completed submission The cross schema check will check if eg the MarineUnitID s used in all the schemas are defined in the MSFD4Geo schema 5 7 1 Validation check output The example below shows the validation error output and the information that is given to help determine where the error is Floods Directive FHRM validation Complex validation checks 1 Conditional checks Element name Element root oo Error Description RecordID LowProbability must be populated if Y has been reported in the element Article6 6_6 7 under the APSFR4 MediumProbability Not LowProbability FHRM FloodHazardMaps HazardArea TypeofFloods reported e Element name The name of the element
17. BackEnd mdb are in the same folder and have not been renamed the front end will automatically link with the back end If the back end cannot be located either because it has been moved or renamed since last used an error message similar to the following will be displayed Databases are not linked The required Article 5 back end WFD Reporting 2005 _be mdb could not be found You can use the next dialog box to locate the File on your system IF you cannot find this File or are unsure what to do choose CANCEL at the next screen and call the database administrator When clicking OK the Locate backend file browser window will open which can be used to locate the back end file Locate backend A dbi5 mdb EF db16 mdb E db241 mdb db mdb A db341 mdb El db rmdb N Il db5 mdb Mu Documents M i dbg mdb E db7 mdb db13 lE db mdb HPD3 anil Dene 1 e li a n s LILI My Network P MER Files of type Access mdb File name Floods reporting workflow user manual v5 0 16 ATKINS When the back end file has been located clicking the Open button will restart the automatic linking process lf Cancel is chosen the following error message will be displayed Article 5 back end links not established 7 i xj 3 You can t run Article 5 Functionality of this tool until you can locate WFD Reporting 2005 be mdb 3 3 Reporting data in the User interface front en
18. Floods Directive reporting user guide for electronic reporting Floods Directive reporting A user guide for electronic reporting Version 5 0 June 2013 Notice This report was produced by Atkins Danmark a s for The European Commission for the specific purpose of support for FD reporting This report may not be used by any person other than The European Commission without The Commission s express permission In any event Atkins accepts no liability for any costs liabilities or losses arising as a result of the use of or reliance upon the contents of this report by any person other than the European Commission Atkins Limited Document History JOB NUMBER DOCUMENT REF 4 Draft to be reviewed during Wolstrup test phase May 2013 4 Final version adjusted after test Wolstrup phase Purpose Description Originated Checked Authorised Date Floods reporting workflow user manual v5 0 Plan Design Enable ATKINS Contents Section Glossary of Terms 1 1 1 1 2 1 3 1 4 2 2 1 2 2 2 3 2 4 2 9 2 6 2 7 3 3 1 3 2 3 3 3 4 4 4 1 4 2 4 3 4 4 5 5 1 5 2 5 3 5 4 5 9 5 6 5 7 6 6 1 6 2 6 3 6 4 6 5 6 6 6 7 6 8 6 9 Introduction Schemas Related documents Getting help Overview of reporting steps Access Database back end Back end quick guide Download of back end Access database Database design Back end database design Order of populating the table
19. KINS 5 5 1 Validating an xml file To validate an xml file click the Check XML file button see Figure 5 1 browse to the relevant xml file you wish to validate and the validation is run as soon as OK is clicked ReportNet Validation tool ver 2 0 0 x File Help ReportNet Validation tool Check XML file View AML file Figure 5 1 The desktop validation tool The main output from the validation tool is presented as shown in Figure 5 2 Validation result XML file C Documents and Settings J MA Desktop RBDSUCAtest xml L Schema validation a v ir J pe l File Checks the schema dennition ant The validation passed succesfully i show details REDSUCA The validation tailed B show details Figure 5 2 Result of validations For each of the validations run the result is shown The detailed reports are marked with the symbols below Floods reporting workflow user manual v5 0 27 The validation was not passed The detailed report contains information about the validation including the errors found A The validation was passed with warnings The detailed report contains information about the validation including the warnings not shown li The validation was passed successfully The detailed report contains additional information about the validation The detailed reports can be seen by clicking the Show details link This will open the report as shown below Detail
20. a value from the enumeration cvc type 3 1 3 The value B of element YesNo is not valid Although QA1 performs the same checks as the desktop validation tool the error messages generated in Reportnet validation are not written the same as those in the desktop validation tool This is because they use a different engine Schema validation follows the W3C XML specification http www w3 org TR xmlischema 1 concepts schemaConstraints These error messages are XML specified validation rules or constraints Constraints have unique names and numbered parts At the following link http www w3 org TR xmlschema 1 concepts schemaConstraints there is a reference in which any error messages can be looked up As all errors relate to one of the following general rules https svn eionet europa eu projects Reportnet wiki SchemaValTec it is easier to examine the element and if it is throwing an error go through each criteria to see if that would throw a specific error Reference to the original schema can also help pinpoint where the error is coming from Complex validation checks QA2 The second validation that is carried is the business rules as described in section 7 2 6 9 Completing the envelope Release envel When you click on Se you submit your report to EEA You will not be able to modify any files in the envelope after you click this button The full automated QA process will run on your delivery and a feedb
21. a into Unit of Management as the Competent Authority code also must be entered in Unit of Management Competent Authorities WFD Competent Authorities u at EUCACode Give details of the Competent Authority IF the same Competent Authority is used for the Floods Directive as for the WFD Buk the relevant information in relation to the responsibilities For the Floods Directive was not yet notified to the Commission the information should be given here iS Competent Authority Name Acronym Competent Authority Mame NL LegalStatus Auth Coy Street ity City WL Postcode Country Roles Role code Comment References Retetetice SS Record TT TO Pei Record 4 1 Lo J P of 3 Drop down lists Code Lists All code lists defined in the schemas have been incorporated into the front end of the database and are used to create drop down lists where appropriate e g country code list This ensures that only valid codes are entered into the back end database International Internationa Mame Floods reporting workflow user manual v5 0 19 ATKINS 3 4 2 3 4 3 3 4 4 Field description All annotations from the schema design have been incorporated into the front end design By clicking on a field a description if this is available in the schema design will appear in the bottom of screen as illustrated below In some cases where the description w
22. ack report will be posted to the envelope EEA and the team responsible for the expert manual review will receive an automatic email that you have completed the envelope The completion process also automatically generates a cover letter acknowledging receipt of the data uploaded to CDR including a list of all files uploaded and their precise location within the CDR 6 9 1 Restricted or confidential data The ReportNet approach means that submitted data is made available for the public to see However you can specifically restrict individual files from public view if this is your national policy To restrict viewing of a file click on the filename in the envelope This will lead you to a page showing you the metadata of the file There you will see a check box which allows you to restrict public access to the file after the envelope has been completed EEA and the team responsible for the expert manual review can still access all files Floods reporting workflow user manual v5 0 39 ATKINS 6 10 Resubmissions If you wish to make an amendment to any data already submitted i e envelope released you must resubmit the whole schema again This means that if a MS corrects information for e g some Unit of Management the MS has to re submit the full CAUOM file again including all the information in the schema not just those corrected This file will replace the previous version Within the envelope create a new envelope for the re submission
23. activate the envelope Creating the envelope First you should login There is grey button on the right side of the page saying New envelope Click on it to create a delivery envelope Most of the necessary metadata is already filled out You need to enter a title for the envelope E g name May 26 2010 and the date which is the reference date of the data you are reporting Floods reporting workflow user manual v5 0 36 ATKINS 6 4 6 5 6 6 Then click on Add You now have an envelope that you must activate by pressing the Activate task button and uploading files Managing the envelope After activation you have reserved the envelope for yourself to work on Other users will not be able to intervene until you e complete the task in which case the system will move forward to the next step in the reporting process or e deactivate the task from the corresponding right side blue button which keeps the work already done and makes it possible for someone else to take over the task It is possible to see if anyone else is working on a particular task by consulting the Status of the envelope Status Task s in progress Draft user bulanmir To track progress of the upload task take a look at the History tab of that envelope When you have activated a task you will notice a new tab in the envelope The system will automatically place you there This is the activity tab It contains the information and
24. as too long for the field length the description has been truncated and you should refer back to the schemas themselves abak of the Competent Jeuthoriy I the same Compebent Authority is used for the Floods arnt as for the WC but the relearn formation n in naliti bo they reporter For the Heed Dti ve FE ret moths to hy Cierra then iate chak be geeni Pan Text fields Text fields hold alphanumeric data The maximum length of the string is determined by the schema This has been included in the table definition so you cannot physically enter more than the defined number of characters For example the EUCACode can have a maximum of 42 characters NOTE A space counts as a character Numeric fields It will be possible to enter numeric data with decimals using both comma 2 75 and a period 2 75 separator The XML conversion tool will translate all the comma separated data into period separated data When actual values cannot be provided the user should or must if entry is mandatory enter one of the negative integer codes listed to indicate the status of the requested data 9999 for Unknown 8888 for Yet to be measured 7777 for Not Applicable Floods reporting workflow user manual v5 0 20 ATKINS 3 4 5 Multiple data entry In embedded datasheets see illustration below it is possible to have multiple data entries
25. asn t there and it also says which elements it was expecting to find So in this case the tool says that Summary1 is expected but only Summary2 was found Part of the detective work Is finding in which section of the schema the error has been raised because this tells us which table in the database to look at Above we work up the schema from the error and we can see we are in the Summary part We can look at the schema to see what structure is expected there The schema diagrams are available as clickable HTML from the resources page From this diagram we can see the expected structure Floods reporting workflow user manual v5 0 31 ATKINS 5 6 2 Floods reporting workflow user manual v5 0 EUUOMCode type fd FeatureUniqueEUCodeType i Summary1 type fd String1 0000Type type g Summary3_1 type fd String5000Type i Summary3_2 type fd String5000Type Summary3_3 CoS type fd String5000Type N g Summary3_4 type fd String5000Type i Summary3_5 type fd String5000Type x Summary5 type fd String10000Type So this agrees with the error message that there should be a Summary1 node here in this hypothetical case So we now know we need to look in the database under the FHRM_Summary table Add the required information and then regenerate the XML file for validation again Address each error until the validation tool reports no errors Or reports errors for which you know the reason a
26. b missed XML file in that envelope and the output is saved XML Schema validation checks QA1 The first schema check QA1 is the xml schema validation which carries out checks that the XML file is well formed and simple validation checks as described in section 7 1 Errors detected in this validation will be returned as a table within a texteditor file The errors within the table will be labelled with the corresponding line and column numbers from the schema SO you Can easily find and correct the error within your schemas example below Floods reporting workflow user manual v5 0 38 ATKINS Type Position Error message ERROR ree cvc datatype valid 1 2 1 this is not a url is not a valid value for any URI ERROR e cvc type 3 1 3 The value this is not a url of element URL is not valid ERROR Line 13 cvc pattern valid Value 15N is not facet valid with respect to pattern 0 1 0 9 1 2 0 9 1 5 Col 17 for type CoordinateT ype ERROR may cvc type 3 1 3 The value 15N of element LAT is not valid ERROR Line 14 cvc pattern valid Value 43562656 is not facet valid with respect to pattern 0 1 0 9 1 2 0 9 Col 22 1 5 for type CoordinateType RROR ey eve type 3 1 3 The value 43562656 of element LON is not valid Line 27 RROR 21 Line 27 ERROR une 21 cvc enumeration valid Value B is not facet valid with respect to enumeration Y N It must be
27. be automatically generated verifying the date of the reporting along with a list of reported documents files User interface front end Back end data storage Fionde Acirsa Tool i Floods Dir Reporting Database v1 Database Access ena iz BK data link Goon aftes cone X Au 5S tl To enter view and edit data for 7 Competent authorkies ha j To enter view and edit date for ret of Mangement Abbibutes CALR _Conpetentoutihor ties CALOM Conpeteniduthorty References CALIOM_CompetertAuthority Roles To aot from Fede Anes Toot CALEA LOM Other C oopeten Ahotie CALR UOM WFD RS WF DLink Name J a ul i a m J is Corin B Favortes FOalemmon Floods reporting workflow user manual v5 0 8 Data to Access DB Rotionshiya Database BackEnd To enter view and edit data for Competent Authorities To enter view and edit data for Unit of Management To enter view and edit date Set Up and General information To exit from Floods Access Tool Database FrontEnd XML conversion tool WFD Conversion Tool ver 1 0 s iol x Fie Help Select database p Atticle 13 tools Test dbout mdb Sa Select schema i fine method repot x Build XML file Desktop validation tool Revortnet Validation tool ver 10 aT File Help ReportNet Validation tool Check XML file EIONET CDR Testing
28. ches or coasts Indicate the total lenght in km Figure 2 4 How to identify a choice field in the schemas 2 Import previously reported CAUOM PFRA APSFR data to newer database version Included in the latest version of the database is functionality to import all the table data for CAUOM tables from previous versions of the database Open the back end database Navigate to Access Objects gt Forms Open the Form Import Press the button import CAUOM PFRA APSFR data Select the database to import from oe ae Se eS Once the database is selected the script will import all the row data from the CAUOM PFRA APSFR tables in the selected database Import CAUOM PFRA APSFR data Press the button and select the database from which CAUOM PFRA and APSFR table data should be imported from Floods reporting workflow user manual v5 0 15 ATKINS 3 3 1 3 2 Access Database user interface only for the GAUOM schema Download of front end Access database In order to set up the front end of the Access database it is necessary to download both the back end and front end of the Access database Both are available for download at htto icm eionet europa eu schemas dir200 760ec resources and are available in 2000 version Linkage of front end with back end Access database To open the front end open Floods Directive Reporting Database mdb If the back end database Floods Directive Reporting Database
29. cription Error message Must be populated if either FloodinformationArt4 and or sae TransitionalMeasuresArt13 1 a in PFRA SHS BOKS OS eN AHOn ik dd 7 PFRAInformation are populated and if International Y in CA _UOM UnitsOfManagement is populated APSFRCode APSFR AreasofFloodRisk APSFRCode must be unique within the MS APSFR AreasofFloodRisk TypeofFloods Must be populated if SourceofFlooding A16 other OtherMechanism APSFR AreasofFloodRisk TypeofFloods aa POPAS O ME ARS mose Gene SAS OtherCharacteristics APSFR AreasofFloodRisk TypeofFloods 1 MES DE PO PU IE HG Natec ENS SSO e noe other FE APSFR AreasofFloodRisk Must be populated if TypeHumanHealth B13 ED a TypeofPotentialConsequences Other a APSFR AreasofFloodRisk ROA OtherConsequenceDescription TypeofPotentialGonsequences Must be populated if TypeEnvironment B24 Other APSFR AreasofFloodRisk Must be populated if TypeCulturalHeritage B33 TypeofPotentialGonsequences Other APSFR AreasofFloodRisk aa Must be populated if TypeEconomicActivity B45 OtherConsequenceDescription OtherConsequenceDescription TypeofPotentialConsequences Other Must be populated if International Y in CA_UOM InternationallnformationExchange UnitsOfManagement PFRA PFRAInformation PFRASummarylnformation OtherSource FHRM FloodHazardMaps HazardArea T ypeofFloods Must be populated if SourceofFlooding A16 other Must be populated if MechanismofFloo
30. d On successfully starting the tool the start up form enables the user to enter data for Competent Authorities Unit of Management and Set up and General information Floods Access Tool To enter view and edit data for Competent Authorities To enter view and edit data for Unit of Management To enter view and edit data Set Up and General information To exit From Floods Access Tool Exit Tool When clicking Competent Authorities CA on the start up form the below Select Competent Authority form opens Select Competent Authority Existing Competent Authorities EUCACode Name No data Competent Authories are reported under WFD Directive O Open existing Competent Authority O Delete Existing Competent Authority Floods reporting workflow user manual v5 0 17 ATKINS This is the main control form for reporting the Competent Authorities and gives four options e Enter new Competent Authority e No data Competent Authorities are reported under WFD Directive e Open existing Competent Authority e Delete existing Competent Authority Same four options will be available for Unit of Management UoM Select Unit of Management Existing Unit of Management EUUOM Code Name No data Unit of Management are reported under the WFD Directive Open existing Unit of Management Delete Existing Unit of Management Select the Set Up option to set attribute
31. ding A25 other FHRM FloodHazardMaps HazardArea TypeofFloods vera a populated if CharacteristicsofFlooding A39 ERE OO ASSENS AES ALE Must be populated if Y has been reported in the OtherMechanism FHRM FloodHazardMaps HazardArea T ypeofFloods OtherCharacteristics LowProbability ADANE CKE SST element Article6 6_6 7 under the MediumProbability FHRM FloodHazardMaps HazardArea QuantitativeLikelihood LowProbability FloodRiskMap J j J j J j J j J ee Must be populated if TypeEconomicActivity B45 OtherGonsequenceDeseription ExposedElement EconomicActivity EconomicActivityConsequence Other O1 Floods reporting workflow user manual v5 0 2 V a Element root eee Description Error message a FHRM FloodHazardMaps HazardArea QuantitativeLikelihood LowProbability FloodRiskMap ExposedElement Environment EnvironmentalConsequences FHRM FloodHazardMaps HazardArea OtherConsequenceDescription QuantitativeLikelinood LowProbability FloodRiskMap ExposedElement FHRM FloodHazardMaps HazardArea QuantitativeLikelinood MediumProbability MediumScenario FloodRiskMap ExposedElement EconomicActivity EconomicActivityConsequence Check FHRM FloodHazardMaps HazardArea OtherConsequenceDescription Nee BOSS Me au Ske BA A Must be populated if TypeEnvironment B24 Other OtherConsequenceDescription Must be populated if TypeEnvironment B24 Other Must be populated
32. eck as described in the table in Appendix B e Optional minimum occurrence is set to 0 and there is no conditional check described in the table in Appendix B Choice check The Choice check is required in order to ensure that an element has been populated where a choice of attached elements is expected in the schema In all cases where an element requires a subsequent choice to be made from a series of attached elements the choice options are set to minimum 1 and maximum 1 i e the validation routine should check that only one of the attached elements has been chosen and populated For example either FloodData or the elements under FloodNoData must be populated but not both Multiple occurrences There are instances when multiple occurrences of elements are required These are required when the maximum occurrence set for an element Is gt 1 The following options exist in the schemas Floods reporting workflow user manual v5 0 41 ATKINS e Minimum occurrence 1 maximum occurrence infinity there must be at least 1 occurrence of the element or sequence of elements and there is no limit to the number of times that element or sequence of elements can be repeated e Minimum occurrence 0 maximum occurrence infinity there may be no occurrences of the element and there is no limit to the number of times that element or sequence of elements can be repeated e Minimum occurrence 1 maximum occurrence n
33. ed report XML Schema validation The following 2 validations of the XML schema were made 1 XML Schema definition Examines f SML file contams a schema definition that is correct and accessible The test was passed successfully The schema definition to be used in validation is http water eionet europa eu schemas dirl00060ec RBDSUCA 1p xsd 2 XML Schema format This validation checks that SML file is wellformed and consistent with schema http water_eionet europa euw schemas dr 200060ec RBDSUCA 190 xsd The test was passed succesfully Figure 5 3 Example of desktop validation output high level Floods reporting workflow user manual v5 0 28 ATKINS Detailed report RBDSUCA WISE RBDSUCA validation Common validation checks Common validation checks Complex validation checks 1 Conditional checks All validation checks were passed successfully 2 Choice checks No Choice Checks has been carried out in this schema 3 Data structure checks No Data Structure Checks has been carried out in this schema 4 Cross schema checks Element ezaz Element name Element root RE Error Description RecordID ER AE AP aes rs Must be a valid EUCACode in PrimeCompetentAuthority RBDSUCA RiverBasinDistrict CAbbbc RBDSUCA CompetentAuthority DKRBD111 5 Code checks Figure 5 4 Example of desktop validation output detailed The results of the validation can be saved and printed from the
34. en the database and the XML file Floods reporting workflow user manual v5 0 23 ATKINS s previously mentioned the conversion tool does not include any validation of the data Therefore the generated xml file must be validated using the desktop validation tool see section 5 If the validation results in errors it is important to verify whether the error exists in the database or in the nationally reported data It is very important that the corrections are made in the national dataset not just in the conversion tool database Floods reporting workflow user manual v5 0 24 ATKINS D 9 1 Desktop validation tool Concept The purpose of the desktop validation tool is to allow the Member States to validate their data prior to upload to ReportNet CDR where another similar level of validation is performed based on the same rules By undertaking this task prior to uploading your xml files onto ReportNet you can correct any validation errors earlier on in the process and therefore repeating the task later on it will save you time The validation tool implies that an xml file has already been generated Thus it is not possible to generate the xml file through the validation tool If the xml file cannot be generated directly from the MS national database the MS Access Reporting DB tool should be used followed by the DB to xml conversion tool 5 2 Computer Requirements 3 3 The desktop validation tool requires
35. erenced against the relevant data in other corresponding tables For example e PFRA_FloodTypesOther and PFRA_ConsequenceFatalities table both have a column named starting with UNIQUECODE_xx The code is AUTO generated within the tables PFRA_FloodTypes and PFRA_TypeofConsequence The unique Code is used to establish a link between the tables A drop down list is available for the tables PFRA_FloodTypesOther and PFRA_ConsequenceFatalities which have been generated on the basis of the information in table PFRA_FloodTypes and PFRA_TypeofConsequence see Figure 2 3 Floods reporting workflow user manual v5 0 13 ATKINS 2 6 2 6 1 2 6 2 Figure 2 3 PFRA_FloodTypesOther table NOTE The table PFRA_FloodTypesOther link to both floodtypes applied for a specific article Column ArticleApplied and the type of flood to identify a flood event Column TypeofFlood Both columns can not be used at the same time see below example TypeofFlood A32 A12 A21 arn Complex structure It is not enough just to use the database to fill in the information It should be used in conjunction with the schemas This is because there are some complex structures which need to be followed else a validation error will occur The following are important to note Conditional checks The Conditional check is required in order to ensure that an element is populated where a previous element is set to a defined value For example if
36. guidance necessary for you to carry out your task Uploading data onto ReportNet To fulfil the reporting obligations you are required to upload the xml file The upload facility enables you to upload the xml file and also add the required shapefiles or where necessary a zip file containing the shapefiles Please remember to use the unzip function in Reportnet if a zip file is uploaded Naming convention for the xml to be uploaded The files should be named according to the following format EVUOMCode Schema name _ dateYYYYMMDD xml e g DK1234_ PFRA_ 20111222 Use of EU Languages You may use any of the official EU languages to report in the free text fields You are however requested to use only one language for the information within any single schema It is not necessary to use the same language for all the schemas No data to be reported If no data are available for a UOM then leave the envelope for the specific UOM empty It is recommended to upload a short note though explaining the no data availability for the specific UOM Floods reporting workflow user manual v5 0 37 ATKINS 6 7 6 8 Checking data quality Once you have uploaded your xml file you need to check the quality of your data within Reportnet EIONET The quality assessment QA consists of a set of rules checked against each individual report It happens in two ways e During the drafting of the report into the envelope QA is manually
37. he functionality forms and system tables which are integral with the functionality No data are stored in this file Only the CAUoM is supported by the front end It is possible to enter both data into the user friendly interface of the Access database or to enter data directly into the database tables 2 XML conversion tool This tool converts the data entered into the MS Access tool into the xml format required for reporting 3 Desktop validation tool This tool checks the quality of the data within the xml files generated It uses the same rules as the validation tool within ReportNet and will detect and report any errors in the xml files at an early stage rather than waiting until you have generated and uploaded onto ReportNet only to have to go back to the start to correct errors This tool can therefore save you a lot of time This tool could be the starting point for those MS generating the XML files directly from their systems 4 ReportNet upload Once the xml files have been generated checked through the desktop validation tool and no errors returned or errors corrected the files are ready to be uploaded onto ReportNet 5 ReportNet QA QC Once the xml have been uploaded into ReportNet it is recommended to also finally run the QA QC facility on ReportNet to ensure that there are no errors remaining in the XML files Once you are satisfied that no such errors occur the files are ready to be released and a cover letter will
38. ime of writing is 3 5 SP1 This is available from the URL below htto www microsoft com downloads details asox familyid ab99342f 5d1a 413d 8319 81da479ab0d7 Each time the Database to xml conversion tool is started an automatic check for new versions will be performed If an update is found but installation is skipped it can be installed manually later on Running the installation as well as the DB to xml conversion tool through a proxy server might cause problems In this case your administrator must change the network configuration in order to remove the proxy for the following websites http icm eionet europa eu schemas dir200760ec resources conversiontool http eionet europa eu 4 3 2 Un installation The DB to xml conversion tool has to be un installed from the Control Panel 4 4 Using the conversion tool The DB to xml conversion tool is started from the start menu Programs gt The European Commission gt Database to XML conversion tool To generate an XML file first select the relevant database for which you want to generate the xml When the Build XML file button is pressed the application builds the file and then prompts the user to save the file as follows Floods Conversion Tool ver 1 0 O x File Help Convert database Select database PA Select schema Build AML file Note The generation of XML files can take a long time if there is a lot of information to map betwe
39. information the Member State country code metadata and url The information entered on this form is used to generate the metadata for the XML files for example the creator email and description Set Up and General Information Attribute Information Creation Date Creator Email Description Generated By General Information Country Code METADATA URL Please notice that some of the fields are red coloured This means that this information is mandatory and must be filled out The three fields in the Set_up and General Information form are the only mandatory fields in this reporting Floods reporting workflow user manual v5 0 18 ATKINS 3 4 3 4 1 NOTE Optional fields can be mandatory fields these fields have not been marked In some cases an element may be optional but if provided then some data becomes mandatory For example this is the case if the unit is part of an international unit then both International name and international relationship most be entered The validation tool will indicate any mandatory fields which have not been completed Data entry All data entered or edited via the front end are saved automatically to the back end database on closing the forms A change that has not yet been saved can be undone by pressing the Esc keyboard key It is recommended to enter data into the Competent Authority form before entering dat
40. ing the installation process However the installation program itself requires at least Microsoft NET Framework 2 0 see section 5 3 Important Running the Database to XML conversion tool requires a connection to the internet 4 3 Installation un installation 4 3 1 Installation The Database to XML conversion tool is installed through the internet from the URL below http icm eionet europa eu schemas dir200 760ec resources conversiontool It should be noted that the installation will only run from Internet Explorer not from other browsers e g FireFox googleCrome Please note that if a previous version of the conversion tool is installed on the PC this will have to be uninstalled as the URL has changed As described in section 4 2 the installation will automatically include the Microsoft NET Framework 3 5 SP1 if this is not already present However it should also be noted that installation of NET requires local administrator access In order to run the installation program itself you must have Microsoft NET Framework 2 0 at least already installed To determine what versions of the Microsoft NET Framework is installed have a look in the folder C Windows Microsoft NET Framework Versions of the NET framework will be in numbered folders Floods reporting workflow user manual v5 0 22 ATKINS lf you do not already have NET 2 0 or higher it is recommended that you install the latest version of NET which at the t
41. ionet europa eu schemas dir200760ec resources Getting help All schemas tools and supporting documents are available from this web page http icm eionet europa eu schemas dir200760ec resources lf you need assistance on issues not addressed in this User Guidance please contact helodeskWISEreporting atkinsglobal com ATKINS ATKINS 1 4 Overview of reporting steps The main reporting steps are shown in the diagram below The approach taken depending on the tools and databases already available within the MS can take different forms Some MS are able to generate the XML files directly from their own systems and would therefore only be interested in the validation and upload steps The reporting steps shown here are for MS where no local tools exist to easily build the xml files required for upload onto ReportNet 1 Access DB Structured around the agreed schemas described in Document No 2 Floods Directive reporting User Guide to the reporting schema v4 0 this MS Access database can be used to import and structure MS data into the required format for the generation of the XML files The database comprises front end interface linked to back end databases The tool is split into two files e Floods Directive Reporting Database mdb This is the back end of the database It contains only tables All data are stored in this file e Floods Directive Reporting Database FrontEnd mdb This is the front end of the database It contains all t
42. ired information in order to create the xml schema from the conversion tool FHM_UniqueCode TypeofFlooding OtherTypeofFlooding FHM_UniqueCode TypeEconomicActivity OtherConsequenceDescription FHM_UniqueCode NACECodes FHM_UniqueCode TypeEnvironment OtherConsequenceDescription O O lt One to many relation Order to fill data into table FHM_UniqueCode Level 0 ProtectedAreas ProtectedArealD Leavers Level 2 Level 3 Not linked FHM_UniqueCode AffectedlEDInstallations Otherlnformation ATKINS Appendix B B 1 Complex validation checks Floods reporting workflow user manual v5 0 ATKINS Floods reporting workflow user manual v5 0 ATKINS Key to Type of Check 1 Conditional check 2 Cross schema check Element name ATKINS Schema CA UOM EUCACode CompetentAuthority EUUOMCode NationalRelationships InternationalName InternationalRelationships PrimeCompetentAuthority OtherCompetentAuthorities Schema PFRA EUUOMCode PFRAInformation PFRASummarylInformation DateofCommencement DurationofFlood lande ranarting workflow user manual v5 OtherSource Type of UnitsOFManagement UnitsOFManagement UnitsOFManagement UnitsOFManagement UnitsOFManagement UnitsOFManagement PFRA PFRA PFRAInformation PFRA Article4Applied PFRA PFRAInformation Article4Applied FloodEvents i FloodData PFRA PFRAInformation Article4Applied FloodEvents FloodData
43. is not part of the defined enumeration list which apply to the element SourceofFlooding By searching for the SourceofFlooding in the HTML it will be clear that S14 is not part of the defined list Floods reporting workflow user manual v5 0 33 ATKINS element FHRM FloodHazardMaps HazardArea TypeofFloods Sourceof Floodin diagram s 5 SourceofFlooding type fd SourceofFlooding Value annotation enumeration A11 enumeration A12 enumeration A13 enumeration A14 enumeration A15 enumeration A16 enumeration A17 facets Kind annotation documentation Indicate source of floods from enumeration list 5 6 3 Correction of validation errors If the validation results in errors these must be corrected before uploading the XML file to Reportnet It is very important that the data are corrected in the database or original source date not just in the XML file See Appendix D 6 for an explanation on interpreting the error reports 5 6 4 Exceptions to error rules In some cases an error generated is legitimate and can be ignored helpdesk Some general guidelines Number larger than field restriction Exceeding text field lenath Values outside of enumeration list Agree with COM as cose lqnore error Ignore error Information not avallable for number fields Information not available for mandatory fields Ise 9999 for numbers and Not Use exception types 7777 Not applicable 6
44. ive reporting User manual v3 0 Document No 2 Floods Directive reporting User Guide to the reporting schema v3 0 Spatial guidance Document No 3 Floods Directive reporting User Guide to reporting spatial data v3 0 Circabc https circabc europa eu faces jsp extension wai navigation container jsp Floods reporting workflow user manual v5 0 43 ATKINS Appendix A A 1 CAUOM tables linkages METADATA FK1 11 URL U1 EUUOMCode UOMName UOMNameNL UOM_MS_CD Area NationalRelationships International InternationalName IntemationalRelationships PrimeCompetentAuthority OtherRelevantRoles Floods reporting workflow user manual v5 0 WFDCompetentAuthorities EUCACode CompetentAuthorityName CompetentAuthorityNameNL Acronym Auth CD LegalStatus Summary Street City CityNL Country Postcode URL EUUOMCode EUCACode RoleCode Comment Attributes CreationDate Creator Email Description GeneratedBy OtherCompetentAuthorities EURBDCode TypeOfAssociation 02 lt lt One to many relation Order to fill data into table Level 0 Level 1 Level 2 Not linked 44 ATKINS 2 CAUOM UnitsofManagement C CD EUUOMCode UOMName UOMNameNL UOM MS CD Area NationalRelationships International InternationalName InternationalRelationships OtherRelevantRoles ArticleApplied FloodLocationCode FloodLocationName CrossBorderRelationship CrossBorderFloodLocationCode
45. ly but to address simple errors causing multiple messages in order to reduce the size of the list Being the detective The validation tool gives the following error message The element Summary in namespace http water eionet europa eu schemas dir200760ec has invalid child element Summary2 in namespace http water eionet europa eu schemas dir200760ec List of possible elements expected Summary1 in namespace http water eionet europa eu schemas dir200760ec Open the generated schema in your test editor and go to line 6 1 lt xml version 1 0 encoding utf 8 7 gt 2 lt FHRM xmins fd http water eionet europa eu schemas dir200760ec fdcommon x xsiischemaLocation http water eionet europa eu schemas dir200760ec http water eionet europa eu schemas dir200760ec FHRM_2p1 xsd CreationDate d Description das GeneratedBy ad ClassificationCode 003 xmins http water ei 3 lt C_CD gt AT lt C_CD gt 4 lt EUUOMCode gt UoM1 lt EUUOMCode gt 5 lt Summary gt 6 i lt Summary2 gt 7 i lt CoastalAreas gt Y lt CoastalAreas gt 8 i lt GroundWaterSources gt Y lt GroundWaterSources gt 9 lt Article6 6AndOrArticle6 7Applied gt aone lt Article6 6AndOrArticle6 7Applied gt 10 r lt Summary2 gt 11 lt Summary3_1 gt t1 lt Summary3_1 gt 12 lt Summary3_2 gt t2 lt Summary3_2 gt 13 lt Summary3_3 gt t3 lt Summary3_3 gt The error message says it was expecting content at line 6 which w
46. nd intend to report in this way Typical validation errors Invalid child element can apply to a whole node missing which could be either a row missing as the above example in a table or a whole table has not been filled in Invalid child element on just one field means typically a field has not been filled in for a row ina table So you need to find which table and which row and check which filed is missing some information If you have an item then you can also do a search on the schema HTML page 32 ATKINS type f String 10000 Type 1 summary6 type fd String5000Type type String10000Type by AL ms pre T ee mn ate Lire R E Summary less than 10 000 characters on methods used to identify assess or calculate flooding extent including res have been selected or return periods depths or water levels velocities or flows where appropriate models used d 5 6 Searching for elements in the HTML page The enumeration constraint failed Other typical errors include invalid element types for example where a value has been reported which is not part of an enumeration list Line Error 23 The http water e1onet europa eu schemas dir200760ec SourceofFlooding element is invalid The value S14 is invalid according to its datatype http water eionet europa eu schemas dir200760ec fdcommon SourceofFlooding The Enumeration constraint failed Here the value S14
47. nstall the latest version of NET which at the time of writing is 3 5 SP1 This is available from the URL below htto www microsoft com downloads details asox familyid ab99342f 5d1a 413d 8319 81da479ab0d7 Floods reporting workflow user manual v5 0 25 ATKINS So Each time the desktop validation tool is started an automatic check for new versions will be performed If an update is found but installation is skipped it can be installed manually later on Running the installation of the desktop validation tool as well as running the tool itself through a proxy server might cause problems In this case your administrator must change the network configuration in order to remove the proxy for the following websites e http icm eionet europa eu schemas dir200760ec resources validationtool http eionet europa eu Uninstallation The ReportNet desktop validation tool has to be uninstalled from the Control Panel 5 4 Principles of validation 5 4 1 5 4 2 The purpose of the validation of an xml file is to check that it is complying with required xml schema form It checks that the xml is well formed and the technical validation is met The first validation carried out checks that the xml is well formed and adheres to the common structure rules outlined in section 7 1 The second validation carried out checks that xml adheres to the complex structure as outlined in section 7 2 The desktop validation tool only wo
48. ollection gt e g Floods Directive Unit of Management and Competent Authorities al Add a new envelope called the todays date e g May 26 2010 8 Activate the task upper right corner 9 Upload xml file into the envelope and name it CountryCode CAUoM _ YYYYMMDD please use PFRA APSFR FHRM for the other relevant xml files 10 Check that everything is correct and meets your national quality requirements 11 Release envelope and QA and cover letter will automatically be generated Overview To participate in the upload process you need to first log in with your Eionet username and password by going to hitp cdrtest eionet europa eu and clicking on the top right Login button If you do not have an Eionet username and password then please contact helpdesk eionet europa eu If you already started this work and you want to be reminded of the URL of the envelope you are working on or if you want to see what you can do next consult the Global Worklist linked from the left side grey button available from every page Whether your job implies drafting the delivery inspecting the result or finalising the work the way to start it and also inform other users that you are executing that action is to activate a task e g Draft for creating updating the delivery Activation reserves the envelope for you and prevents your colleagues from inadvertently corrupting the data If you want to transfer the task to someone else you can de
49. on in order to create the xml schema from the conversion tool U Attributes Schema name CreationDate Creator Email Language Description GeneratedBy ClassificationCode 4 O lt One to many relation Order to fill data into table Level 0 Level 1 Level 2 Level 3 Level 4 Not linked 45 ATKINS A 3 APSFR tables linkages CAUOM_UnitsofManagement APSFR_Summary Cc CD EUUOMCode 1 UOMName EUUOMCode UOMNameNL SummaryofMethodology JOM MS CD SummaryofCoordination rea NationalRelationships International InternationalName InternationalRelationships OtherRelevantRoles EUUOMCode APSFRCode NameofAPSFR CrossBorderRelationship 7 CrossBorderAPSFRCode FK1 APSFRCode LAT TypeofConsequence LON OtherConsequenceDescription GeneralAdditionalComments APSFR_TypeofConsequence ASPFR_FloodTypesOther See UL UNIQUECODE_FloodTypes FK1 APSFRCode 1 TypeofFlood UNIQUECODE FloodTypes OtherDescription O 0 lt One to many relation Order to fill data into table Level 0 Schema name CreationDate Creator Email Language Description GeneratedBy ClassificationCode ii Attributes shall be filled Level 1 Level 2 schemaName Level 3 METADATA URL Not linked with the required information in order to x s create the xml schema Link to CAUOM table can only be established TOMA CONVERSION too if the EUUOMCode has been
50. rks if you have a connection to the internet because the tool pulls down the latest version of the relevant schema directly from ReportNet This ensures that any validation is always consistent with the latest version of the schema Schema definition schemaLocation The XML file should contain a reference to the schema definition file so that the validation can be undertaken The reference is an attribute to the root element and consists of two parts namespace and location e g xsi schemaLocation http water eionet europa eu schemas dir200760ec http icm eionet europa eu schemas dir200760ec CA_UoM_Ops3 xsad For the validation tool to successfully retrieve the other validation rules from ReportNet then the schema definition needs to point at the schema held on ReportNet The urls to the latest schema versions can be found at this location Description FD Reporting http converters eionet europa eu do upl Schemas The first validation described below checks this definition Cross schema and within schema validation checks The desktop validation tool checks the integrity of the xml files generated in terms of data structure format and duplicates 5 5 Using the validation tool The desktop validation tool can be accessed through the Start menu on your desktop simply go to Start gt Programs gt The European Commission gt ReportNet desktop validation tool Floods reporting workflow user manual v5 0 26 ATKINS AT
51. s Complex structure Import previously reported CAUOM PFRA APSFR data to newer database version Access Database user interface only for the CAUOM schema Download of front end Access database Linkage of front end with back end Access database Reporting data in the User interface front end Data entry Creation of xml files The DB to xml conversion tool Concept Computer Requirements Installation un installation Using the conversion tool Desktop validation tool Concept Computer Requirements Installation uninstallation Principles of validation Using the validation tool Understanding desktop validation output Complex validation checks by element Uploading xml files onto ReportNet A Quick guide Overview Creating the envelope Managing the envelope Uploading data onto ReportNet No data to be reported Checking data quality Understanding validation output in ReportNet Completing the envelope Floods reporting workflow user manual v5 0 ATKINS 6 10 Resubmissions 7 QA QC 7 1 Common validation checks 8 Documents and links Appendices Appendix A Database diagrams Appendix B QA QC validation rules Appendix C Database to schema linkages Floods reporting workflow user manual v5 0 40 41 41 43 ATKINS Glossary of Terms Term APSFR CA CAUOM CDR DB FD FHRM GWB GWMET GWST MON MS PA POM PFRA RBD RBDSUCA RBMP SWB SWMET SWST UoM WB WFD WISE
52. se the specific source of flooding should be reported in the tables FHRM_FloodHazardMaps and if additional flood type needs to be reported in a group then this should be done in the table FHRM_FloodHazardMapsAdditionalFloodT ypes Order of populating the tables The fields that form the link between tables will also be in most cases drop down lists and it is therefore a good idea to fill information into the tables in a certain order since these drop down lists will be created as the data is filled in At a schema level it is recommended to fill information into the tables in the following order 1 Attributes 2 Country 3 schema tables CAUOM PFRA APSFR and FHRM This suggested order is also contained within Appendix A using colour coding of the tables Linkage of low level tables within the database Most tables will be linked through unique identifiers given by the MS e g EUUOMCode APSFRCode but some tables require the use of an auto generated unique ID from the parent table Where this is the case it is clearly stated in the description field within the tables and will also be marked in the table linkage diagrams in Appendix A Drop down lists make the information easier to fill in as long as the parent tables are filled in first In order for the tables within the DB to link to each other in the same way that the schemas themselves link to each other unique ID s are required in different tables to be ref
53. sign and hence each reporting DB should contain data from only one UoM along with the CAUOM schema which needs to be common to all reporting DBs A separate DB should therefore be created for every UOM in the MS and the CAUOM tables should be copied into every one of these DB as illustrated in Figure 2 1 The CAUOM tables can easily be identified within the database because the table names have the prefix CAUOM Access DB Access DB Access DB UOM X UOM Y UOM Z Figure 2 1 CAUOM tables need to be copied into each reporting DB for the MS Floods reporting workflow user manual v5 0 10 ATKINS 2 3 2 3 1 2 4 Database design Naming of the Tables within the Reporting Database The Access database contains many tables These tables have been structured to reflect the schema designs Appendix A The tables within the database are therefore related to one of the 4 individual schemas and it is possible to see which schema each table relates to with the prefix schema name to the table name For example schemas linked to PFRA have a PFRA prefix to the table name In the same way that the schemas link to each other so do the various tables within the reporting database The linkages between the tables relating to any given schema can be seen in Appendix A The required elements in the Access database tables are bold in Appendix A however please note that several elements are conditional To see the specific rules laid down for a
54. tag within the schema which has caused the error e Element root Where this element is found within the schema e Element value The value which has caused the error if there is one e Error description Why the error occurred e RecordiD An ID of the record within which the error was thrown To find the error requires some detective work because this type of validation does not provide line numbers If the element value is provided then searching for that value in the XML would be the quickest approach 5 7 2 Correction of validation errors If the validation results in errors these must be corrected It is very important that the data are corrected in the source data not just in the XML file Floods reporting workflow user manual v5 0 35 ATKINS 6 6 1 6 2 6 3 Uploading xml files onto ReportNet A Quick guide This quick guide outlines the Central Data Repository CDR delivery procedure in quick steps for the experienced ReportNet User 1 Download the xml schemas and use your chosen method of generating the information to report against them i e the Access reporting tool supplied or another Use the desktop validation tool to check your data and correct any errors found Enter the Central Data Repository CDR by going to hitp cdr eionet europa eu Click on the country for which you want to make the delivery Go to data collection European Union EU gt obligations we S N Click on the relevant subc
55. there must be at least 1 occurrence of the element or sequence of elements and that element or sequence of elements can be repeated up to a maximum of n times e Minimum occurrence n maximum occurrences n there must be n occurrences of the element or sequence of elements and that element or sequence of elements can be repeated up to a maximum of n times Yes No elements There are elements that require a Yes No answer These must be checked to ensure that the correct codes have been used The FD Common schema stores codelists that may be referred to by more than one element within the schema There are two Yes No types that have been defined in the FD Common schema e YesCode Y e YesNoCode Y N Where Y Yes N No Code check The Code check is the most common validation check and is required to ensure that where relevant valid codes are selected from the attached codelist defined in the FD Common schema and that in almost all cases only one occurrence of the selected code exists in the data submission avoiding the creation of duplicates For example element C_CD must be populated with a valid country code defined in the codelist CountryCodeType within the FD Common schema Floods reporting workflow user manual v5 0 42 ATKINS 8 Documents and links Floods Directive hitp eur lex europa eu LexUriServ LexUriServ do uriz CELEX 32007L0060 EN NOT Schema guide Document No 1 Floods Direct
56. tion gt lt xs annotation gt lt xs complexType gt Figure 2 2 Field design illustrated in both Access DB table and in schema file 2 4 4 2 4 5 2 4 6 If text fields in the DB are defined as Memo the information on how many characters allowed will be available in both the xml file and in the text description Enumeration Drop Down Lists All code lists defined in the schemas have already been incorporated into the DB and are used to create drop down lists where appropriate e g country code C_CD list This ensures that only valid codes are entered into the DB Code lists are defined in the system schema FDCommon Numeric fields In some of the numeric fields it is possible to insert an exception These will be available from a drop down list in the DB 9999 Unknown 8888 Yet to be measured 7777 Not Applicable lt will be possible to enter numeric data with decimals using both comma 2 75 and a period 2 75 separator The XML conversion tool will translate all the comma separated data into period separated data Date and URL Date format must be in the format yyyy mm dd if nothing else is specified and links URL to relevant documentation must be a valid URL format Floods reporting workflow user manual v5 0 12 ATKINS 2 9 How to use access database table FHRM_FloodHazardMapsAdditionalFloodTypes Probabilities can be reported on the basis of different flood types If this is the ca
57. triggered by the user in order to fix possible errors at that stage it is done by clicking the corresponding QA button next to each factsheet During drafting the QA result is not stored in the envelope but is just displayed to the user on a web page You can save it on your own PC if you wish for your records e After the data reporter completes the envelope QA is automatically triggered by the system on all reports in this case the result is stored in the envelope as Feedback object the rules checked are the same as in the case of manual QA Hint the QA rules are available at http converters eionet europa eu queriesindex jsp To start the QA click on the Run QA links next to your uploaded files This will run a collection of quality assessment scripts and produce a report describing the specific tests carried out and the results It can typically detect syntax issues but won t know if your information makes sense in terms of the other schemas uploaded or not More detail on the specific QA functions is provided in chapter 7 of this document Understanding validation output in ReportNet Validation in ReportNet can be run at two points Manually after an XML file has been uploaded Buttons will appear next to the filename in the envelope QA1 and QA2 Output from a manual validation is not saved anywhere just displayed on screen Secondly when an envelope is released all the validations are run on the su
58. uralHeritage Other EconomicActivity FloodData T ypeofConsequence EconomicActivity Other TransitionalMeasuresArt13 1 a T ypeofFloods T ypeofFlood TransitionalMeasuresArt13 1 a T ypeofFloods T ypeofFlood other TransitionalMeasuresArt13 1 a T ypeofFloods T ypeofFlood other PFRA PFRAInformation i Adan PFRA PFRAInformation Must be populated if MechanismofFlooding A25 TransitionalMeasuresArt13 1 6 TypeofFloods T ypeofFlood other PFRA PFRAInformation Must be populated if CharacteristicsofFlooding A39 OtherMechanism OtherCharacteristics TransitionalMeasuresArt13 1 b TypeofFloods TypeofFlood other Must be populated if International Y in CA UOM InternationallnformationExchange UnitsOfManagement PFRA PFRAInformation PFRASummarylnformation Schema APSFR Must be a valid EUUOMCode in CA UOM UnitsOfManagement or valid sub unit code EUSubUnitCode ind the WFD RBDSUCA Schema Must be populated if either FloodinformationArt4 and or APSFR 2 TransitionalMeasuresArt13 1 a in PFRA PFRAInformation are populated 51 EUUOMCode APSFR AreasofFloodRisk APSFR Must be populated if TransitionalMeasuresArt13 1 b in PFRA PFRAInformation is populated Must be populated if either FloodinformationArt4 and or TransitionalMeasuresArt13 1 a in PFRA PFRAInformation are populated Art13 1 bSpatiallnformation SummaryofMethodology APSFR Floods reporting workflow user manual v5 0 NS Element root eee Des

Floods reporting workflow user manual v5.0

Contents

Download Pdf Manuals

Related Search

Related Contents