Electronic Noise Data Reporting MechanismA handbook for delivery
Contents
1. CDR Central Data Repository dB Decibel dbf Shapefile attribute format DF Data Flow DG Env Directorate General Environment EC European Commission EEA European Environment Agency Eionet Environment Information and Observation Network END Environmental Noise Directive ENDRM Environmental Noise Data Reporting Mechanism ESRI Environmental Systems Research Institute ETC SIA European Topic Centre on Spatial Information and Analysis EU European Union GIS Geographic Information System HTML Hypertext Transfer Mark up Language ICAO International Civil Aviation Organisation INSPIRE Infrastructure for Spatial Information in the European Community LAU Local Authority Unit Lis Noise indicator for day evening and night as defined by END Laight Noise indicator for night time as defined by END MS Member State prj Shapefile projection format QA Quality Assessment ROD Reporting Obligations Database SEIS Shared Environmental Information System shp Shapefile shape format shx Shapefile index format xml Extensible Mark up Language Electronic Noise Data Reporting Mechanism 33 European Environment Agency Electronic Noise Data Reporting Mechanism A handbook for delivery of data in accordance with Directive 2002 49 EC 2012 33 pp 21 x 29 7 cm ISBN 978 92 9213 324 5 doi 10 2800 55226 Version 2 December 2012 97ZSS 008Z 0T Op N NI 600 ZT NV HL ISBN 978 92 9213 324 5 917892922. Feedback posted for this file Ce 09 foe ty Electronic Noise Data Reporting Mechanism Lids Posted automaticaly on 08 Jun 2012 Visualisation Figure 8 1b Visualisation of the automatically converted xml file name of the file should be considered solely as an example OLLA ErtoWin owe Piogoutterete A a EIONET CDR Testing e nara Einnet CONTEST Spain European Union EU Morse directive DFS ES gt DFES del201se Services File ES z DF1 5 2015 del DF1 5 Agg xml Bach to envelope Search View fie as Notifications Ogre Heip SQL for MySQL CR eee Subscribe to receive HOUR Alos A you want to SQL for MS Access stay Updated about s Simple HTML table L events in this site H Excel ARIS VB ior MS A Change tie Local upload Exammar Upload Edit fe properties Title Converted ttom ES_z DF1 5 2015_dotads Schema tocation http dd eonet europa ew GetSchema ide TBL7 246 File size 7 26 KB 7429 Bytes Last uploaded 08 Jun 2012 09 36 Restricted trom public view _ Change Quality assessment Run validation on Noise DF 1_5 Agglomeraticas 2012 fun OA 1 Feedback posted tor this fe No feedback avaiable for this Me When you wish to visualise GIS data the menu choices are different such as show shapefile as an image which is illustrated in the following example Then the image is revealed as illustrated overleaf Electro
3. Electronic Noise Data Reporting Mechanism Data model Figure 4 8 Agglomerations industry 20 Electronic Noise Data Reporting Mechanism Data model Figure 4 9 Agglomerations all sources Electronic Noise Data Reporting Mechanism 21 22 Reporting platform Reportnet 5 Reporting platform Reportnet The information submitted by Member States is to be collated and managed by the EEA on behalf of the EC using the Reportnet system Reportnet is a system of integrated IT tools and business processes creating a shared information infrastructure optimised to support European environmental reporting It provides an existing framework for the reporting of environmental data flows including those reguired by relevant air guality and water framework directives Where appropriate data formats and specifications for the END reporting mechanism templates have been harmonised with those of existing environmental reporting obligations reported through Reportnet This includes tabular data in xml spreadsheets Microsoft Excel and or databases e geographic information webforms and written reports e metadata Data providers will access the Central Data Repository CDR http cdr eionet europa eu and upload the delivery The system will then validate it automatically and the data requesters clients will manually inspect it More details about Reportnet and the Central Data Reposit
4. HU_DF1_5_2015_del If HU delivery is not correct the folder will be sent back to draft and will not be accepted until the information could be considered correct In this case the information should be stored in the same folder until the data is considered correct and the delivery is accepted If HU delivery is correct but not complete it is still missing some information and they report all the information 2 months after the deadline a new folder should be created and ALL the information should be stored there again and the new folder will be named as follows HU_DF1_5_2015_upd150226 If subsequent updates of the information should be done the names of the subsequent folders will follow the naming convention specified before Then click on Add You now have an envelope that you must activate Electronic Noise Data Reporting Mechanism 5 3 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 During the time someone works on a task his her colleagues are able to see this by consulting the status of the envelope For further information on the work
5. See dataflows specific annexes for direct URLs to CDR reporting 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 deactivate the envelope 5 1 1 Getting help If you need to request an Eionet username or require any other assistance during your Environmental Noise Directive reporting please contact the Eionet helpdesk helpdesk eionet europa eu The helpdesk will assist you directly with most problems relating to the use of the Central Data Repository CDR They will pass questions on issues relating to the content of reporting to EEA and the European Topic Centre on Spatial Information and Analysis ETCSIA If you find that parts of this user manual could be improved please send your suggestion to EEA via the helpdesk 5 1 2 For the impatient CDR Data delivery procedure in quick steps for the impatient 1 Enter the
6. inz de la Maza The concept of the Electronic Noise Data Reporting Mechanism is based upon the original version produced on behalf of the EEA by Bureau Veritas in 2007 The key contributors to this revised handbook are members of the ENDRM review team Colin Nugent N ria Blanes Jaume Fons Roman Ortner Anna B ckman and Nigel Jones the CNOSSOS EU Working Group 9 Guillaume Dutilleux Radoslaw Kucharski Hilary Notley including Extrium and DG ENV Balazs Gergely as well as the Joint Research Centre of the European Commission Stylianos Kephalopoulos Marco Paviotti Fabienne Anfosso L d e Additional advice and input was received by Sheila Cryan Soren Roug and Hermann Pfeiffer from EEA Additionally it was reviewed by the Eionet National Reference Centres on Noise and by Aphrodite Mourelatou from the EEA Electronic Noise Data Reporting Mechanism 5 6 Introduction 1 Introduction This handbook has been developed to facilitate Member State reporting in a common format while ensuring that the reporting requirements of the END are met among other voluntary information that could be facilitated It addresses the reporting obligations set out in the END and provides reporting templates for MS to utilise directly downloadable from Reportnet This handbook has been prepared by the European Environment Agency on the basis of the original handbook prepared by Bureau Veritas and Extrium behalf of both the
7. this is not a user friendly way to show it There are other ways One of them is the HTML view that shows the data reported as a webpage including associated GIS information This view also provides a more print friendly layout In most cases a quality assessment can be triggered on demand by the reporter To do this click on the run QA links next to the filename created from the files you uploaded with the data This will run a collection of quality assessment scripts and produce a report describing the tests and the results of them It can typically detect syntax issues and incomplete entries but cannot determine the accuracy of the original data More information on the quality assessment functions is provided in Chapter 9 5 7 Completing the envelope When you click on Complete task you submit your report to EEA You will not be able to modify any files in the envelope after you decide to complete the task The fully automated QA process will run on your delivery and a feedback 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 Reportnet approach is that completed deliveries to reporting obligations are 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 e
8. Central Data Repository CDR http cdr eionet europa eu 2 Click on the country for which you want to make the delivery 3 Open the data collection European Union EU obligations 4 Enter to the corresponding sub collection e g Noise Directive DF1_DE5 Report on all major roads railways airports and agglomerations or Noise Directive DF7_DF10 Action Plan Summaries etc These are listed under Environmental Noise Directive folder 5 Add a new envelope for the delivery 6 Open the new envelope 7 Activate the task 8 Add the data into the envelope download first the templates that are provided to fulfil the requirements of each DF in the case of tabular data 9 Inspect that everything is correct and meets your national quality requirement Run QA if applicable Complete the task when all data has been uploaded 12 See Section 5 8 for subsequent processing oa Ro 5 2 Creating the envelope First you should login Navigate to the DF that you wish to report e g Noise Directive DF1_DF5 Report on all major roads railways airports and agglomerations under European Union EU obligations Environmental Noise Directive folder For direct URLs see dataflow specific annexes You will see a grey button on the right side saying new envelope Click on it to create a delivery envelope Provided the updates of the information that should be provided every five years several subfolde
9. EEA and DG ENV in 2007 It has been updated to take account of the experience gained in the use of the Mechanism during the delivery of first round noise mapping data pertaining to the END It contains 11 sections e Section 1 provides an introduction to the handbook e Section 2 introduces the reporting requirements of Directive 2002 49 EC This includes the reporting obligations set out in the Directive and also covers an introduction to the formatting requirements of the Reporting Mechanism and the associated data flows e Section 3 provides an overview of the Reporting Mechanism including an introduction to the different types of information to be reported and how the Mechanism is structured Section 4 is a more technical section which sets out the Reporting Mechanism data model It notes how the END data requirements have been translated into a coherent data structure Specific details for any kind of information can be found in the corresponding annexes Section 5 contains the description of how to deliver the requested information through Reportnet and how to proceed in case of updates or corrections in existing sources of information Sections 6 and 7 provide general information concerning tabular and spatial information to be reported concerning all reporting obligations Section 8 shows how the reports provided can be visualised by different means in Reportnet Section 9 contains the general description of the quality ass
10. europa eu Enquiries eea europa eu enquiries Contents Contents ForewoOrd ane nnnenn en nnnenn eme n eme nan anna nana ana ana nana ana an anna nana 4 Acknowledgements uuzananunnunnanunnanunnanunnanunnnnnannnnannnnannnn an aaa a Ea iaa nana nana ananasas 5 1 Introduction ommcconcnconnncancncnncnnnncnnnn cnn nana cnn rca narran cnn nr anna aaa an aaa an aaa an ananasas 6 2 Aim of Reporting Mechanism ocococnorocononorannncnnnnrannnrnnnnnnnrnnnnrnnnnrananrnnnnranrananennanennane 7 2 1 Reporting obligations and data flOWS zuresssrsnnennannennenan nun enn nn nenne nennen nennen nenn 7 2 2 Reporting Mechanism approach kaka kaka kaka n nen ann nen narrar nun aaa 7 3 Overview of the ENDRAM uuuunuanunnanannannanunnanunnanunnanann ann ana nana ananasai an ana an an nana ananasas 10 341 Member State reporting viscosa siusis an rei 10 3 2 Reporting entities xico A a i a a a k i AN d io 10 A Data model TO 12 5 Reporting platform Reportnet uuruunanunnanannnnunnanunnnnnnnunnanannanunnanannannannnnanunnannnn 22 5 1 Using the Central Data Repository for reporting zzeessnensennnennnonnennnnnnnn nun nan nennen nennen 22 5 2 Creating the envelope 2 0 cece eee ee nennen nenne nn kaka nun een ennnn nun nen nennen nenn nennen nennen 23 5 3 Managing the envelope use ea EEE bei i 24 5 4 Uploading data nidos kai ae anna na Us a FR 24 5 5 Use of EU languages urinaria es Ri ias i a a a a a o p 24 5 6 Checking data
11. of the hierarchy of reporting by the Member State defining the various organisations who would be reporting within the Member State DFO would set out responsibilities coverage and contact information for all referenced organisations DFO thus defines the reporting structure in which the Member State proposes to submit all subsequent reports The presence of dataflow zero in the reporting mechanism performs a number of functions By receiving documentation of the reporting structure in each Member State the EC will have knowledge of which organisations they can expect to receive any given piece of information This will result in an efficient system for submission of reports and communication exchange Due to the fact that DFO defines the structure of reporting at the highest level of the hierarchy within a Member State its existence is crucial to the manner in which all subsequently received reports and data sets are collated and compiled Dataflow zero therefore facilitates the integration of submitted data into a coherent system that will enable the EC to create summary reports and analyses 3 2 Reporting entities The information required by the END has a temporal component The dataflows identified by the EEA DG ENV shown in Table 2 1 detail a Electronic Noise Data Reporting Mechanism method for identifying the deadlines inherent in the directive It is also apparent from these dataflows and from the statements in the Directi
12. 1133245 NL European Environment Agency 2 J
13. EEA Technical report No 9 2012 Electronic Noise Data Reporting Mechanism A handbook for delivery of data in accordance with Directive 2002 49 EC AAA ISSN 1725 2237 M European Environment Agency J 2 EEA Technical report No 9 2012 Electronic Noise Data Reporting Mechanism A handbook for delivery of data in accordance with Directive 2002 49 EC M European Environment Agency 2 Design EEA Layout Rosendahl Schultz Grafisk EEA Cover photo EEA Legal notice The contents of this publication do not necessarily reflect the official opinions of the European Commission or other institutions of the European Union Neither the European Environment Agency nor any person or company acting on behalf of the Agency is responsible for the use that may be made of the information contained in this report Copyright notice EEA Copenhagen 2012 Reproduction is authorised provided the source is acknowledged save where otherwise stated Information about the European Union is available on the Internet It can be accessed through the Europa server Www europa eu Luxembourg Publications Office of the European Union 2012 ISBN 978 92 9213 324 5 ISSN 1725 2237 doi 10 2800 55226 Version 3 November 2013 21 i a EMAS Verified environmental management REG NO DK 000244 European Environment Agency Kongens Nytorv 6 1050 Copenhagen K Denmark Tel 45 33 36 71 00 Fax 45 33 36 71 99 Web eea
14. S is a collaborative initiative of the European Commission and the EEA to establish together with the Member States an integrated and shared EU wide environmental information system This system would tie in better all existing data gathering and information flows related to EU environmental policies and legislation It is based on technologies such as the internet and satellite systems and thus make environmental information more readily available and easier to understand to policy makers and the public The underlying aim of SEIS is also to move away from paper based reporting to a system where information is managed as close as possible to its source and made available to users in an open and transparent way According to the SEIS concept environmentally related data and information will be stored in electronic databases throughout the European Union These databases would be interconnected virtually and be compatible with each other The proposed SEIS is a decentralised but integrated web enabled information system based on a network of public information providers sharing environmental data and information It will be built upon existing e infrastructure systems and services in Member States and EU institutions Electronic Noise Data Reporting Mechanism 7 8 Aim of Reporting Mechanism Table 2 1 Data reporting obligations Data Flows in END Data flow Summary description of Legally bind
15. ata as listed in First legally binding deadline Mandatory Art 8 1 Annex VI for major roads railways 18 January 2009 every five Art 8 2 airports and agglomerations and fo tati t years ia any criteria used in drawing up 1st implementation step Art 8 5 action plans Second legally binding deadline 18 January 2014 Art 10 2 2nd implementation step Art 10 5 Annex VI Art 8 3 Note 1st implementation step concerns the following reporting entities e Agglomerations gt 250 000 inhabitants Per major civil airport gt 50 000 movts year For overall major roads gt 6 million veh year For overall major railways gt 60 000 trains year Electronic Noise Data Reporting Mechanism 2nd implementation step concerns the following reporting entities note that they include the reporting entities of the ist implementation step Agglomerations gt 100 000 inhabitants Per major civil airport gt 50 000 movts year For overall major roads gt 3 million veh year For overall major railways gt 30 000 trains year Aim of Reporting Mechanism The SEIS Communication was launched by the Commission in January 2008 and more information about this initiative may be obtained at http ec europa eu environment seis index htm 2 2 4 Metadata The Reporting Mechanism is based upon electronic files Therefore in order to manage these files effective metadata needs to be provided with each data flow report The sp
16. ata that are reported Overview of the ENDRM Figure 3 1 High level overview of data model wee ee Sel Se MS S Source ETC SIA and Extrium 2012 Electronic Noise Data Reporting Mechanism 11 12 Data model 4 Data model To maximise inter comparability and harmonization between Member States a fixed common format for reporting is necessary The data structures presented in this section together with the annexes containing the data specifications provide a basis for common delivery of reporting obligations required by the END Furthermore this approach should support the development of the strategic noise map database required by the END Article 10 3 The following figures present the proposed conceptual data models for each entity The intended use of the data models is to help the users lt CountryCode gt lt Reporting Entity Short Name gt DF1 Agg PK Unigue Agglomeration ID Reporting Entity Unigue Code Agglomeration Name Number of Inhabitants Size A x 2 Vv 1 DF 1 5 Major road network fa DF_1_5 Major rail network DF_1_5 Aggloms Polygons DFO Reporting Regions Polygons a a DF 15 Major Airports DF 4 8 Noise contour maps understand the content and relationships between the dataflows for any one entity In conjunction with these data models users should refer to the high level data model presented in Figure 3 1 to view the co
17. ecified metadata standards for spatial data are those currently adopted by the EEA and proposed for future use within INSPIRE They are based around a profile of 15019115 The EEA standards will be regularly updated and the standards set by the INSPIRE directive will be followed Further details are set out in the relevant data specifications in Section 5 of this handbook The standard for non spatial data has been harmonised with the standard already used by Reportnet This is based upon the widely used Dublin Core metadata standard 2 2 5 Software standards MS Excel and MS Word and GIS files The content of the Reporting Mechanism templates has been structured for compatibility with the commonly used Microsoft Excel and Word software applications the last one to provide supplementary information These software tools are used by the EEA and are understood to be in common use throughout Member States The structuring of reported information into worksheets and written text reports also allows Member States flexibility For example member States can implement the basic MS Excel templates in a more advanced relational database management system if so desired Finally shapefiles for vector data or ASCII files for raster data have been used as GIS standard to provide spatial information being the most disseminated GIS exchange files formats 2 2 6 Reporting Mechanism design principles The range of requirements associated w
18. ed locally e fillin the file with the corresponding information requested in each data flow e upload the file following the naming conventions suggested in each dataflow specific annex Each time you would like to make an update of the data consider that the whole package of information should be provided again and upload all the intended data including the specific changes Electronic Noise Data Reporting Mechanism If you upload data in a zip file the Microsoft Excel content will not be converted and quality assessed Please do not use the option of Add Zip file to upload the filled in worksheets templates If you have any queries regarding the generation of the XML file or any problems with the upload of the data please contact the Eionet helpdesk 7 GIS reporting GIS reporting In order to avoid data format problems for the development of one common reference layer for environmental noise data it is recommended to provide the mandatory information on the areas affected by the Directive and the corresponding noise contour maps in spatial format To facilitate the process countries are invited to choose shapefile format or ARC INFO ASCII GRID for the following reasons e Shapefile is an open format and a de facto standard e Major GIS software packages and all the open source desktop GIS support it What is referred to as a shapefile is actually a set of several files Four individual files are mandatory to s
19. essment rules being performed against each individual report being delivered under END requirements Finally sections 10 and 11 contain the options each Member State has to deliver the information from national databases as well as a glossary of terms The annexes provide detailed data specifications which define the structure and formatting of the various data flows contained within the Reporting Mechanism The European Commission has formally stated a preference for the use of Reportnet in the delivery of data relating to Directive 2002 49 EC In order to satisfy the reporting obligations a letter of confirmation should be sent by the country s Permanent Representation to the Sectretariat General of the Commission stating that the upload to Reportnet has taken place Electronic Noise Data Reporting Mechanism Aim of Reporting Mechanism 2 Aim of Reporting Mechanism 2 1 Reporting obligations and data flows Directive 2002 49 EC requires Member States to report a variety of information to the EC at different stages of implementation from 2005 onwards Details of the information to be reported or data flows are set out below in Table 2 1 2 2 Reporting Mechanism approach 2 2 1 Simple reporting A number of factors have been considered during the development of the Reporting Mechanism The main aim has been to simplify the reporting for Member States This has been achieved by e reducing repetition through the use
20. formats which are not easy for all users to read over the Web e g XML or in case this information needs to be later integrated and aggregated in other systems databases reports etc This section refers to the conversion of XML files for reports major sources agglomerations or noise maps into printable formats and also the visualisation of map data To use conversion just click on the name of the file in the envelope You will get a menu which shows the original i e no conversion and the list of available conversions Choose Quickview in HTML as illustrated in the following examples Figure 8 1a Visualisation of the original Worksheet uploaded by the Member State name of the file should be considered solely as an example Q6aA immewiad mm EIONET COR Testing e Cionat CORTEST Spain European Union EU Services File ES 2 DF1 5 2015 del xis View fil as Notifications Original e 5 i Le j MTL Change fie te Local upload i Subscribe Lo MEL i L not it you want to Eot Me properties stay updated about i Title events in the sde i File site 28 5 KB 29184 Bytes Last uploaded 06 Jun 2012 09 36 Restricted from public view Quality assessment No quailty assessment scripts avakabis for mis document horse directive OFS Loge ireponen A E 15 delab15 Back to envelope Upload Excel le converted mio an XML delivery
21. in progress and previously done 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 guidance necessary for you to carry out your task 5 4 Uploading data There are various ways of uploading or entering data for reporting in accordance with the Environmental Noise Directive You can e upload a file e add a zip file especially for delivery of spatial information where the file size may be very large e add the data directly if it is a web form These procedures are described in Chapters 6 and 7 5 5 Use of EU languages It is possible to use any of the official EU languages in the free text fields agreed for Environmental Noise Directive reporting You are however requested to use only one language for the information in a single file It is not necessary to use the same language for all your files Reporting platform Reportnet 5 6 Checking data quality yourself Two ways have been provided to help you verify that your data meets your national quality requirements visual inspection and quality assessments To visually inspect your data click on the filename in the envelope This will lead you to a page showing you the metadata of the file and a menu of different ways to view the data For verbatim presentation use original however
22. ing deadline Updates by END information to be reported MS provision DFO Definition of reporting structure DF1 5 Major roads major railways First legally binding deadline Mandatory Art 7 1 major airports and agglomerations 30 June 2005 every five years Art 7 2 designated by the Member State ist imbl tati t i for DF1 ist ER 1st implementation step implementation Art 7 5 Second legally binding step suggested deadline 31 December 2008 for DF5 2nd 2nd implementation step implementation step DF2 Competent bodies for strategic 18 July 2005 Possible at any Art 4 2 noise maps action plans and data time collection DF3 Noise limit values in force or 18 July 2005 Possible at any Art 5 4 planned and associated information time DF4 8 Strategic noise maps related data First legally binding deadline Mandatory Art 7 1 as listed in annex VI for major 30 December 2007 every five Art 7 2 roads railways airports and ii tati t years iz agglomerations 1st implementation step Art 7 5 Second legally binding deadline 30 December 2012 Art 10 2 2nd implementation step Annex VI DF6_9 Noise control programmes that have First legally binding deadline No updates Art 10 2 been carried out in the past and 18 January 2009 A VI noise measures in place 1st implementation st p LL 4 Ed 1 3 amp 2 3 Second legally binding deadline 18 January 2014 2nd implementation step DF7_10 Action plans related d
23. ith the reporting obligations of Directive 2002 49 EC and the need to minimise the reporting burden to Member States has led to a particular design of the Reporting Mechanism The design principles of relational databases allows for information of different formats to be linked together and therefore reducing the need for repetition a single item of information can be reported once and used multiple times This process is known as normalisation The data model for the Reporting Mechanism has therefore been developed along the lines of a relational database design This design concept is a standard approach adopted within the information technology industry to optimise efficiency and facilitate a common implementation Further details on the END Reporting Mechanism data model and data specifications can be found in section four and in the corresponding annexes of this handbook Electronic Noise Data Reporting Mechanism 9 10 Overview of the ENDRM 3 Overview of the ENDRM 3 1 Member State reporting In addition to the dataflows required by the END it is also necessary to permit flexible reporting by Member States The structure of the ENDRM should allow Member States to submit data to the EC at sub Member State regional levels In order to facilitate sub Member State reporting in a traceable manner dataflow zero has been included in the structure Dataflow zero DFO is a report to be submitted at the top level
24. mplete conceptual model Users should also refer to the Data specifications detailed in the corresponding annex which present the precise definition and content for each field specified in the data model A brief description of the symbols used in the diagrams is presented below This symbol illustrates where submission of tabular data is required and presents the file naming convention together with the columns in the table see details concerning file naming conventions in the corresponding annexes The relationships associated with the table will also be shown This symbol indicates that xml metadata is required for each table to be reported This symbol indicates where written reports are to be supplied These symbols indicate where geodata objects are required In the data model diagram PK represents Primary Key and is the unique identifier for the row record FK represents Foreign Key and is the reference link between two tables Electronic Noise Data Reporting Mechanism Data model Data model Figure 4 5 Agglomerations roads Electronic Noise Data Reporting Mechanism 17 Data model Figure 4 6 Agglomerations railways 18 Electronic Noise Data Reporting Mechanism Data model ons air Figure 4 7 Agglomerat il li 2 h ila LA mu ni E 19
25. nic Noise Data Reporting Mechanism 30 Visualisation Figure 8 2a Visualisation of the original shapefile uploaded by the Member State name of the file should be considered solely as an example Ora Crvitu Vardews PLogoutiieserter A a EIONET COR Testing Fimnete CONTEST gt Spain Eurnpenn Union EU tnise directive DES ES DF1 5 del2015 E 401 Services File IE a Agg Areas shp ALL Search View Mie as Notifications Original Help Stow shapefiie metadata Based on ogrinto from gdat 1 0 6 gt Note Couvert stapefile to vald OGG KML 2 2 Based on ogr2ogr from geal t 0 6 Only shapefiles lt 10M will be converted Show 2hapetis as image Based on shp2ing trom FWTools 2 0 5 Subscribe to receive 3 posicao Ml you want to Change Me stay updated about i s Local upload Examinar Upload events in this site i L de Edit Nie properties Tie IE Aga Arsasshp File site 407 KB 4172 Bytes Last uploaded 08 Jun 2012 00 45 Restricted from public view Quality assessment No quality assessment scripts avatabie tor this document Feedback posted for this Me No feedback ava abie for this the Figure 8 2b Visualisation of the shapefile using the option Show shapefile as image rin N CA Vid wt tk j y j 4 A F N j Nasi k f fy U gt f 1 j EJ 4 PY Shapet ile bounding bex A Sharat ile feature t soluen N
26. nvelope 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 5 8 Correcting the envelope Once the envelope has been completed the manual review of the data and exploitation for reporting purposes start by the EEA and ETCSIA side If some of the provided data is incorrect then ETCSIA will provide feedback to the envelope asking for the correction of the data reported This action implies that the envelope is returned to draft and the country is allowed to correct the files and complete the envelope again If the country identifies an error on the data provided then the responsible person should contact Eionet helpdesk to activate the envelope again The country can then correct the identified error and complete the envelope again Therefore if the action is for correcting data already provided identified by ETCSIA in the manual QA or identified by the same country the envelope will be returned to draft status and the error can be corrected The result will be one envelope for the dataflow at a given date Please contact the Eionet helpdesk if you require assistance Electronic Noise Data Reporting Mechanism 25 26 Reporting of tabular information 6 Reporting of tabular information The Repo
27. of relational database principles e adopting formats which best suit the type of information to be reported e keeping consistency of reporting formats between successive reporting rounds e adopting formats which are in line with existing EEA EC reporting approaches 2 2 2 INSPIRE The Directive for the establishment of an infrastructure for spatial information in the European Community is otherwise known as the INSPIRE Directive A key objective of INSPIRE is to make more and better spatial data available for Community policy making and the implementation of Community policies initially environmental policy in the Member States at all levels Since its adoption in 2007 the INSPIRE Directive has defined the most appropriate format for data in relation to many other directives and data streams Relevant elements of the ENDRM have been formatted in a way that meets the reguirements of INSPIRE This includes the use of the ETRS89 geographical referencing system and the use of spatial metadata standards to accommodate delivery of noise maps source locations agglomeration boundaries and action planning areas including zones delimited as guiet areas Importantly the reporting formats are designed to meet a minimum achievable standard which takes into account the diversity of approaches to managing spatial data which currently exists across Member States 2 2 3 SEIS The Shared Environmental Information System SEI
28. ory can be found at http www eionet europa eu reportnet html Reporting of environmental noise data has a few particularities such as a large number of files may be delivered in an envelope and therefore the display query and quality assessment of those needs to be handled in a easy to use manner besides the text based delivery geographical data is desirable maps and eventually it will need to be processed queried and aggregated 5 1 Using the Central Data Repository for reporting To participate in the delivery process you should first log in to CDR http cdr eionet europa eu with your Eionet username by clicking on the top right login button see Section 5 1 1 on how to request a login There are two level of folders predefined in order to facilitate uploading your data The first level is entitled Environmental Noise Directive under the EU obligations In the second level you will find a folder for each data flow Noise Directive DFO Definition of reporting structure Noise Directive DF1 DF5 Report on all major roads railways airports and agglomerations Noise Directive DF2 Competent bodies Noise Directive DF3 Limit values in force report Noise Directive DF4_DF8 Strategic noise maps report Noise Directive DF6 DF9 Noise control programmes Noise Directive DF7_DF10 Action plan summaries Electronic Noise Data Reporting Mechanism Reporting platform Reportnet
29. otbyroww nap dela by Gpentireetnap and Conte laitiers CCE ban oc bn Electronic Noise Data Reporting Mechanism Quality assessment 9 Quality assessment The quality assessment QA consists in a set of rules checked against each individual report This happens in the following way During the drafting of the report the user can trigger on demand a QA in order to fix possible errors at that stage it is done by clicking the corresponding QA button next to each fact sheet During drafting the QA result is not stored in the envelope just displayed to the user on a web page You can save it on your own PC if you wish 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 The rules checked are the same as in the case of the on demand QA Hint for the QA rules are available at http converters eionet europa eu do gaScripts The lists of ICAO codes airports used by the system for control are available at http converters eionet europa eu xmlfile Eurocontrol airports xml The lists of Unigue AgglomerationsID used by the system for control are available at http cr eionet europa eu sparql fillfrom http 3A 2F 2Fcreionet europa eu 2Fsparqlbookmarks 2F3742593108919731431 and you must click on the Execute button The results of the on demand QA may be viewed in CDR by checking the Feedback fo
30. quality yourself Sie 25 5 7 Completing the envelope Kit kane anse an an i nn 25 5 8 Correcting the envelope miii li a a etaient 25 6 Reporting of tabular information oomoocononnnronnnrannnranancancananrananrananrananrnncnnanennanennane 26 7 GIS reporting nuunsananuanannannnnunnanunnanannanunnanan nana anna aaa aaa an anna nana ann ana nana ana ana nana ananasas 27 7 1 Spatial reference ren Hure nen 27 7 2 Metadata a ias 27 8 Visualisation RE Da a a anna a ana aaa 28 8 1 Visualisation of the reports nenn nennen nun nun nun aaa nun rr rr rr nr rra 28 9 Quality assessment unnunnnennnnnnnnnnnnunnunnunnnunnunnunnunnnnnnnnnnnnnnnnnnnnnnunnnnnunnun nun nun nun nenn 31 10 Delivering from National database omocoonoconnononnnrannnnnncanancnnnncanancnnnncrncanancnnancananes 32 11 Glossary S 33 The annexes are available at http www eea europa eu publications noise handbook Electronic Noise Data Reporting Mechanism 3 Foreword Foreword The Directive 2002 49 EC relating to the assessment and management of environmental noise otherwise known as the Environmental Noise Directive END contains several provisions which require Member States MS to communicate information to the European Commission EC These reporting obligations are summarised in a document drafted by the European Commission s Directorate General for the Environment DG ENV which is made available on the web and is also reproduced f
31. r the envelope as highlighted in red in Figure 9 1 Figure 9 1 Visualisation of the Automatic QA report of the files uploaded in Reportnet Nordebein Westfales updated verson Microweft Internat Explorer provided En BEA 101x S TT 1 2151 x E Po Ele Et Lem Faotes lock teb 1 QNorhananetain Lo ES corkrel prograrrees 1 ki a Search freetext Nordrhein Westfalen updated version gt Search by obligation Deseription Search XML files Obligations Report on all major roads always sirports and agglomerations OFS Global worklist Period 2009 Whole Year Coverage Germany DEA Hay Reportes 20 110 Manage Status o the manual Q ned Activate task Manual GA TI st NOW do tr f JA j envelope E Electronic Noise Data Reporting Mechanism 31 32 Delivering from National database 10 Delivering from National database You may also chose to upload data directly from an automatic QA will not be conducted on your a relevant national database in order to fulfil deliverable your Environmental Noise Directive reporting requirements The format of the data will of course If you require further advice or assistance with a need to be compatible with Reportnet otherwise delivery from a national database please contact the Eionet helpdesk Electronic Noise Data Reporting Mechanism 11 Glossary Glossary
32. rs indicating the delivery year corresponding to a specific reporting period would be created under the general envelope structure as follows del CountryCode _DF number _ RefYear _ upd date Electronic Noise Data Reporting Mechanism 23 24 Reporting platform Reportnet Where number is the DF number DFO DF1_5 DF2 DF3 DM 8 DF6 9 or DF7 10 RefYear corresponds to the year when the deliverable should be done four digits e del corresponds to the first time that a country provide information for this reporting obligation in a specific reference year e upd corresponds to the updates of the information corresponding to the reporting obligation for a specific reference year of the END i e when the information reported under del is not complete or does not contain the complete expected coverage e and date is the date when the update of information to the same reporting obligation is done Date format is year two digits month two digits and day two digits yymmdd Example HU wants to report data for the first time on DF1 and DF5 on 2015 delivery date specified in the END the folder where to put the information would be the general one Noise Directive DF1_DF5 Report on all major roads railways airports and agglomerations e inside that folder HU will create its own subfolder subenvelope corresponding to the delivery HU wants to do and it will be named as
33. rtnet Data Dictionary provides the detailed specifications for the data to be provided in connection with each data flow This may be accessed at http dd eionet europa eu datasets In order to avoid misunderstanding during the quality check one of the following values should be provided for an empty field Field Value Meaning Description 1 Data not Even if the field is not applicable it should not be left empty This may apply to applicable the following cases Table field not to be reported because no agglomeration or no major roads or no major railways or no major airports fall in the scope of the Directive meeting the minimum threshold specified by END In this case the 1 value only needs to be inserted into the upper left cell For the agglomerations case if a specific noise source is not present In this case the 1 value should be used as field values A field value does not exist e g EURoadID 2 Data not Data not mandatory for reporting not yet available or not available available Users can make the data delivery by one of the following methods e Uploading a file using the templates Microsoft Excel worksheets that can be downloaded by clicking to Data Dictionary at the corresponding line Completing the web form e Generation of the XML from local system e g database and upload it into the envelope In the case of reporting a Microsoft Excel template save the template provid
34. tem 1989 but it can also be provided using a specific national reference system though the coordinate system used should be specified in any case Coordinate system and projection ETRS89 LAEA52 if another coordinate system is used it should be specified in the metadata file in order to process the data provided Most maps in EEA reports are presented in the Coordinate Reference System CRS as in the table below For the purpose of streamline the information of the used Coordinate Reference System CRS the EEA OC team recommends to state the EPSG code instead of writing the full name and definition of the used CRS where it is possible Look up EPSG codes here http Avww epsg registry org Background information on GIS related issues is available at http www eionet europa eu gis 7 2 Metadata Further details are set out in the corresponding data flows annexes of this handbook Coordinate EPSG code Name and definition Types of Datum reference system coordinates ETRS LAEA 3035 Lambert Azimuthal Equal Area 5210 Map projection in ETRS89 Latitude of origin 52 N meters Longitude of origin central meridian 10 E Electronic Noise Data Reporting Mechanism 27 28 Visualisation 8 Visualisation 8 1 Visualisation of the reports Files added in a delivery envelope can be converted into different formats according to their type The data conversion is particularly relevant in case of original
35. tore the core data that comprises a shapefile lt a gt shp lt a gt prj lt a gt dbf and lt a gt shx being lt a gt the file name which should be the same for all the files If a country only provides a single file with the shp extension this file cannot be used for any purpose as it is incomplete for distribution The other three supporting files are required e ARC INFO ASCII GRID is a non proprietary format and is used as an exchange or export format due to the simple and portable ASCII file structure Most of noise modelling programs can export the results of the analysis in this format Although noise contour maps can be delivered in any suitable format to display a map the preferred ones are shapefiles or Arc Info Ascii grid This information can be uploaded using Add file or Add zip file button following the naming conventions suggested in the corresponding data flow annexes of this Handbook 7 1 Spatial reference Information on the spatial reference used when preparing GIS data is vital when the data has to be compared or combined with GIS data coming from other sources The GIS information provided by countries will be combined with that from their neighbours to provide a full European picture of the areas affected by the application of the Directive and also of the population exposed to environmental noise It is highly recommended to provide the data using the European Terrestrial Reference Sys
36. urther in this document This handbook depicts the design details of the Reporting Mechanism ENDRM proposed by DG ENV It is supplemented with an overview document where the main design characteristics of the proposed Reporting Mechanism are presented accompanied by a series of electronic templates These templates can be used by the reporting authorities to fulfil their obligations t http ec europa eu environment noise directive htm http ec europa eu environment noise data htm These files can be found on the web They were finalized in October 2007 by DG ENV on the basis of the outcomes of a project carried out by Bureau Veritas on the behalf of the European Environment Agency EEA in 2006 and updated in 2011 This handbook aims to support MS authorities in understanding and using the proposed electronic templates It presents the technical approach taken and the proposed data model to fulfil the proposed templates for reporting to the EC The proposed and updated data specifications which can be followed by Member State reporting authorities can be found in the corresponding annexes G http forum eionet europa eu nrc noise libarary endrm guidelines 2012 Electronic Noise Data Reporting Mechanism Acknowledgements Acknowledgements This handbook was written by staff from the EEA Colin Nugent and the European Topic Centre for Spatial Information and Analysis N ria Blanes Jaume Fons Miguel S
37. ve that the reporting obligations can be further sub divided into information required by entity as follows major Roads major Railways major Airports agglomerations The reporting structure implemented in a Member State may be different for each of these entities Therefore there is a requirement for a DFO to define the reporting structure for each of the four entities separately giving a total of four DF 0 tables Furthermore the END also indicates that there is a requirement for certain dataflows within agglomerations to be sub divided between the four sources roads inside agglomerations railways inside agglomerations airports inside agglomerations industry inside agglomerations Moreover the ENDRM also permits the submission of strategic noise maps relating to overall predictions of exposure to multiple sources in agglomerations Figure 3 1 presents the high level design implemented for the Reporting Mechanism reflecting both the temporal aspects of the reporting obligations represented by the individual dataflow elements and the structure of the model by entity The relationships between all the different pieces of information required are also displayed to provide a complete overview of the structure of the reporting mechanism The information to be supplied for dataflow zero has also been incorporated in this model showing how this information is critical to the structure and understanding of the subsequent d
Download Pdf Manuals
Related Search