1 / 14

New Delhi COP8, October 2002 Katarina Mareckova SHMU, Tinus Pulles TNO

IPCC project on Establishment of a Database on GHG Emission Factors. New Delhi COP8, October 2002 Katarina Mareckova SHMU, Tinus Pulles TNO. UNFCCC, Kyoto protocol.

gillock
Download Presentation

New Delhi COP8, October 2002 Katarina Mareckova SHMU, Tinus Pulles TNO

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

E N D

Presentation Transcript

  1. IPCC project onEstablishment of a Database on GHG Emission Factors New Delhi COP8, October 2002 Katarina Mareckova SHMU, Tinus Pulles TNO

  2. UNFCCC, Kyoto protocol • Countries have to submit inventories on regular bases, which are consistent, complete, comparable, transparent, and accurate • Quality of GHG inventories depends on reliable emission factors and activity data

  3. Emission Factors • Emission factors should reflect national/regional circumstances. • Emission Factors have to be accompanied with appropriate scientific background information • Emission factors should be documented: “easy” to find and “easy” to check / compare

  4. Comparisons of the underlying information will facilitate the selection of the most appropriate parameters. Objective of the EFDB Project • To develop a database of emission factors and underlying information for the purposes of securing and disseminating the most current scientific information on emission factors and assisting in increasing transparency and reliability of national inventories. • Sharing data/information will avoid duplication of research efforts

  5. Why IPCC EFDB • Regional inventory workshops(IPCC,UNDP,UNFCCC,….) • Cuba (IPCC/UNFCCC joint expert meeting, Havana, September 1998) • Ghana (UNFCCC expert meeting, Accra, July, 1999) • UNDP – (Capacity building to Improve National GHG Inventories 2000-2002 ) • Development of revised IPCC 1996 Guidelines • Development of Good Practice Guidance 2000 • An easily accessible public EFDB with supporting scientific information would help improve the quality of GHG inventories in a cost-effective way.

  6. Schedule • Phase I : July 2000 - October 2002Planning, Design, Construction, Pilot Testing, Population • Scoping meeting (New Delhi, July 2000) • 1st expert meeting for determining functional design, etc. (Paris, July 2001) • Development of Prototype Database(October 2001 - January 2002) • Pilot testing (February - April 2002) • 2nd expertmeeting revision of DB prototype (Bratislava, April 2002) • Finalisation of the EFDB construction, population with default EF (May - October 2002) • Presentation of EFDB at COP8 (New Delhi, October 2002) • Phase II : November 2002 -Dissemination and On-going maintenance, Further Population Dissemination through the internet, CD ROMs ( SBSTA 18)

  7. Users of the EFDB • Inventory compilers (Inventory agencies) in every Party to the UNFCCC • IPCC (for future update of the IPCC Guidelines) Other groups: • Inventory expert review teams (ERT) • Project developers, involved in e.g. CDM & JI • Scientist, Consultants involved in GHG inventories work • General public and NGOs

  8. Nature of the EFDB - more of a “Library” than an “Authority” • Users of the EFDB must be able to trust the background information provided with the quantitative value they find. This means that the inclusion/exclusion of new data in/from the database must be controlled. • However, usage of the EFDB information for compiling GHG inventories will always be the full responsibility of the user.

  9. Contents of the EFDB • Gases to be included • CO2, CH4, N2O, HFCs, PFCs, SF6 + Some other gases (Indirect GHGs …) • Structure (categorisation) to be followed • IPCC Source/Sink Categories • IPCC Fuel Categories • Information to be presented (Data fields) • Administrative information • data provider, date of receipt of the data, etc. • Technical information • descriptive name, value, unit, confidence limit, technical reference, properties, etc. • Usage/Review information • type of EF (Measured/Modelled/…), external QC, etc.

  10. Find EF (Search and get data) • 3 options: • Search step by step by specifying the IPCC source category and Gas(es) • FULLTEXT search using keywords • Find EF using unique EF-ID

  11. Find EF • Categorization stage User defines the relevant • Sector • Fuel (only in case of Energy Sector) • Gas (Plural gases can be chosen at a time) • Search stage Output table will appear on the webpage. User screens them out for the optimal choices by - filtering on the webpage, or - exporting to MS-Excel and using its functions. • Acquisition stage User gets detailed information on the selected data. (Export to MS-Excel)

  12. Some standing QC procedures will be applied. Single, Bulk, Minibatch Input (Population of the database) • Categorization stage User defines the relevant • Sector • Fuel (only in case of Energy Sector) • Gas (Plural gases can be chosen at a time) • Input stage User specifies: - Administrative information - Technical information - Usage/Review information

  13. Publishing and distribution • Editorial board (review of the EFs) • Publication on the Internet at COP8 • Updates of the database at fixed intervals (2 to 4 times per year) • Distribute copy on CD ROM • For experts with limited access to the Internet • Updates once or twice a year

  14. And further … • EFDB is meant as an interactive platform for exchange of knowledge on emission factors • EFDB will only be successful if experts not only browse the database but also propose new emission factors

More Related