Review of the Electronic Noise Data Reporting Mechanism (ENDRM) Meeting of the EIONET National Reference Centres for Noise 7-8 October 2010 Copenhagen.

Review of the Electronic Noise Data Reporting Mechanism (ENDRM)

Meeting of the EIONET National

Reference Centres for Noise

7-8 October 2010

Copenhagen

Nigel Jones, Director

Overview

Presentation Overview

•CNOSSOS-EU and Task 9 “Updating of the ENDRM”- CNOSSOS-EU- Requirement for Task 9- Expert Group

•Lessons Learnt- Using ENDRM in Round 1- Using Reportnet- Challenges of using MS Returns

•Future Considerations- Further developing ENDRM and Reportnet- Improving relevance of data- Aligning with CNOSSOS-EU

CNOSSOS Task 9:

Updating the ENDRM

Common NOise aSSessment methOdS in EU(CNOSSOS-EU)

•EC require a common understanding of noise climate across European Member States

•This requires a common assessment method•Expert meeting in march 2009 identified wide range of

methods used in END R1•Method - not just ‘acoustic calculation’ method•CNOSSOS-EU established at end of 2009•National experts involved in 9 Tasks•CNOSSOS-EU designed to compliment the END Review

work


1. Co-ordination Group

2. Road Noise Source

3. Railway Noise Source

4. Industrial Noise Source

5. Noise Propagation

6. Aircraft Noise Source

7. Guidelines for use of CNOSSOS-EU

8. Population Exposure

9. END Reporting Mechanism Update





















Requirement for Task 9 – Update of ENDRM

•Review

•Experiences of reporting on END Round 1- From MS perspective, and- From an EEA/EC perspective

•Feedback received from NRCs - How effective were the ENDRM Handbook and Templates?- What would they change?

•Reportnet now officially available for 4 Dataflows (DF1, DF5, DF6 and DF7)

- How have MSs fared when using Reportnet?

Requirement for Task 9 – Update of ENDRM

•Also and opportunity to look forwards…..

•NOISE viewer launched- How could this be further developed to inform the

citizen•Provision of information to support EC policy requirements

- Does the current ENDRM content support this?• Impending update of DF1 (30 June 2010)

- Inclusion in Reportnet- opportunity for MSs to fill in any gaps

•Ensuring ENDRM integrates with Common Methods- To provide a better understanding of results

Task 9 - Expert Group

• Colin Nugent (EEA)

- Task Leader and chair of EPON• Anna Backman (EPoN)

- Commissioned original 2007 ENDRM• Juame Fons and Nuria Blanes Guardia (EEA ETC-LUSI)

- QA and analysis of MS reports

- Design and development of NOISE viewer• Roman Ortner (UWB)

- ‘User’ of ENDRM as NRC for Austria • Nigel Jones (Extrium)

- Architect of 2007 ENDRM

- ‘User’ supporting UK and Irish Governments

- Drafting CNOSSOS-EU Guidelines

Lessons Learnt

Lessons learnt - END Round 1

•The introduction of the ENDRM in 2007 helped in the reporting of information (especially from DF4 onwards).

•Around 80% of Member States have followed the ENDRM approach by using templates.

•But feedback has highlighted that…- ENDRM Guidelines document was complex to use- The need to follow the ID and referencing system was

perhaps not fully appreciated by NRCs- The entity relationships have not always been followed- Guidelines on how to use within Reportnet were not

included in 2007 version.•Weaknesses in some technical aspects of END identified.

Importance of Entities, IDs and their Relationships

<CountryCode>_DF0_MRoad

PK Reporting Entity Unique Code

FK1 Country Code Full Name of Reporting Entity Contact Name Address Telephone Fax E-mail

<CountryCode>_<Reporting Entity Unique Code>_DF1_MRoad

PK Unique Road ID

FK1 Reporting Entity Unique Code EU Road ID National Road ID National Road Name Annual Traffic Flow Road Start Node (x1) Road Start Node (y1) Road End Node (x2) Road End Node (y2) Length

<CountryCode>_<Reporting Entity Unique Code>_DF2_Map_Code_MRoad

PK CA Entity Code (Mapping)

Name of Competent Authority Contact Name Address Telephone Fax E-mail


PK Noise limit value report details

FK1 Reporting Entity Unique Code


PK,FK1 Reporting Entity Unique Code

Numbers Exposed to Lden 55-59 Numbers Exposed to Lden 60-64 Numbers Exposed to Lden 65-69 Numbers Exposed to Lden 70-74 Numbers Exposed to Lden > 75 Numbers Exposed to Lden 55-59 with Special Insulation Numbers Exposed to Lden 60-64 with Special Insulation Numbers Exposed to Lden 65-69 with Special Insulation Numbers Exposed to Lden 70-74 with Special Insulation Numbers Exposed to Lden >75 with Special Insulation Numbers Exposed to Lden 55-59 with a Quiet Facade Numbers Exposed to Lden 60-64 with a Quiet Facade Numbers Exposed to Lden 65-69 with a Quiet Facade Numbers Exposed to Lden 70-74 with a Quiet Facade Numbers Exposed to Lden >75 with a Quiet Facade Numbers Exposed to Lnight 50-54 Numbers Exposed to Lnight 55-59 Numbers Exposed to Lnight 60-64 Numbers Exposed to Lnight 65-69 Numbers Exposed to Lnight > 70 Numbers Exposed to Lnight 50-54 with Special Insulation Numbers Exposed to Lnight 55-59 with Special Insulation Numbers Exposed to Lnight 60-64 with Special Insulation Numbers Exposed to Lnight 64-69 with Special Insulation Numbers Exposed to Lnight >70 with Special Insulation Numbers Exposed to Lnight 50-54 with a Quiet Facade Numbers Exposed to Lnight 55-59 with a Quiet Facade Numbers Exposed to Lnight 60-64 with a Quiet Facade Numbers Exposed to Lnight 65-69 with a Quiet Facade Numbers Exposed to Lnight >70 with a Quiet Facade Area exposed to Lden > 55 (including agglomerations) Area exposed to Lden > 65 (including agglomerations) Area exposed to Lden > 75 (including agglomerations) Numbers exposed to Lden > 55 (including agglomerations) Numbers exposed to Lden > 65 (including agglomerations) Numbers exposed to Lden > 75 (including agglomerations) Dwellings exposed to Lden > 55 (including agglomerations) Dwellings exposed to Lden > 65 (including agglomerations) Dwellings exposed to Lden > 75 (including agglomerations) Reference to Maps Computation and measurement methods report details


PK Name of Noise Control Programme

FK1 Reporting Entity Unique Code Cost of Programme Date of Implementation Date of Completion Number experiencing an improvement in environmental noise Noise Control Programme report details

<CountryCode>_<Reporting Entity Unique Code>_DF7_Summary_MRoad

PK,FK1 Reporting Entity Unique Code

Action Plan summary report details

Detailed Data FlowsMajor Roads

Version 1.6 – 05/01/07

Finalising the END Reporting Mechanism – Contract EEA/BSS/06/006

DF0 Reporting RegionsPolygons

Member States

PK Country Code

Country Name

<CountryCode>_<Reporting Entity Unique Code>_DF2_AP_Code_MRoad

PK CA Entity Code (Action Planning)

Name of Competent Authority Contact Name Address Telephone Fax E-mail

<CountryCode>_<Reporting Entity Unique Code>_DF7_NCP_MRoad

PK Name of Noise Control Programme

FK1 Reporting Entity Unique Code Cost of Programme Date of Implementation Date of Completion Number experiencing an improvement in environmental noise Noise Control Programme report details

Restricted Draft

<CountryCode>_<Reporting Entity Unique Code>_DF2_Map_MRoad

FK1 Unique Road ID CA Entity Code (Mapping)

<CountryCode>_<Reporting Entity Unique Code>_DF2_AP_MRoad

CA Entity Code (Action Planning)FK1 Unique Road ID

*

1

1

1

*

*

*

*

*

*

<xml>

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

<xml>

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

<xml>

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

<xml>

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

<xml>

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

<xml>

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

<xml>

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

<xml>

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

<xml>

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

<xml>

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

*

<CountryCode>_<Reporting Entity Unique Code>_DF2_Collect_Map_MRoad

FK1 Reporting Entity Unique Code Name of Competent Authority Contact Name Address Telephone Fax E-mail

<CountryCode>_<Reporting Entity Unique Code>_DF2_Collect_AP_MRoad

FK1 Reporting Entity Unique Code Name of Competent Authority Contact Name Address Telephone Fax E-mail

*

<xml>

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

<xml>

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

*

Reportnet

•Guidelines on the use of Reportnet were made available for DF5 onwards

•Use of Reportnet by Member States has increased significantly from DF5 onwards

- >80% use Reportnet•Reports now in a centralised location•Reportnet is a properly managed data repository•Templates now have a QA function built into them•A few Member States not using Reportnet•Some users not making use of all functions, e.g. QA•Not yet available for all Dataflows

Challenges using MS Returns (1)

•The use of data reported under the ENDRM does not stop once data is reported…

• It is integrated into a European noise database• It is used to support development of European noise policy

- Feeds into TERM, Urban themes, SOER, etc..- Health impacts e.g. Night Noise Guidelines- Testing ‘what if’ policy scenarios

• It is used to support public information portals (NOISE viewer)- So GIS format information is of value- Important to EEA/EC as it enables cross-policy analysis

•Following the ENDRM Guidelines are beneficial….

Challenges using MS Returns (2)

•European noise database- Data needs to be standardised

• It is used to support development of European noise policy- Provision of information on probity of data- Reporting on time- Definitive data (sometimes updated information is supplied)

•Public information/online mapping- Requires spatial data rather than tables or images - Many different spatial referencing systems

• It is helpful to use the entity model in the ENDRM- around 50% of MSs have reported Noise Action Plans

under DF7, but already around 800 electronic files.

Potential ENDRM Improvements

Further developing ENDRM and Reportnet

•Development of further Guidelines on use of Reportnet- DF8

•Further development of web forms for data entry•Enhancing the data dictionary• Improvement of the ENDRM handbook

- Provision of non-technical explanations- Grouping of reporting requirements by source (entity) to

help NRCs coordinate internally with competent authorities

•Reportnet system test (pilot with Austria and Wales)•Review of ENDRM ID codes (with Deutsche Bahn)

Reviewing relevance of ENDRM content

•Reviewing content of ENDRM in response to new and developing policy requirements

- Emerging health impact knowledge (WHO NNG)- Global assessment - how to consider the combined

impacts from multiple noise sources at a single location (Quiet Area policy)

- Use of spatial data•Technical requirements of cross-cutting policies

- Shared Environmental Information System (SEIS)- Inspire

•Has an implication on how data is defined, how mapping is undertaken and on the format in which it is reported

Proposed ENDRM Changes

•The ability for MSs to report exposure statistics down to:- 40dB Lnight- 50db Lden

•Ability to report global exposure statistics in agglomerations•Ability to report noise map data (spatially referenced noise

levels)

•Reporting of Quiet Areas?

Aligning with CNOSSOS-EU

•How methods can affect data reported- How noise sources are defined (DF5)- Quality and quantity of data inputs (DF5 and DF8)- Calculation methods (DF8)- Population exposure methods (DF8)

• It is important for the ENDRM to influence the approach to any Common Method, so that results are relevant and support policy requirements. Implications for MSs:

- Role of monitoring- Scope and design of mapping projects- Coordinating results for exposure assessment

Summary

Presentation Summary

•CNOSSOS-EU and Task 9 “Updating of the ENDRM”- CNOSSOS-EU- Requirement for Task 9- Expert Group

•Lessons Learnt- Using ENDRM in Round 1- Using Reportnet- Challenges of using MS Returns

•Future Considerations- Further developing ENDRM and Reportnet- Improving relevance of data- Aligning with CNOSSOS-EU

Acknowledgements

• Colin Nugent•Anna Backman•Juame Fons•Nuria Blanes Guardia •Roman Ortner

Thank you

[email protected]

+44 (0) 1892 704040

Review of the Electronic Noise Data Reporting Mechanism (ENDRM) Meeting of the EIONET National Reference Centres for Noise 7-8 October 2010 Copenhagen.

Documents

endrm slide

noise propagation

endrm cnossos

cnossoseu slide

railway noise source

industrial noise source

road noise source

aircraft noise source