sphericalpm / ghgdata

Greenhouse gas emissions data packaged for easy exploration and charting

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

GHG Data

What is this?

GHG Data is a dataset compiled out of national greenhouse gas (GHG) inventory submissions by Annex I Parties to UNFCCC. The primary purpose of this dataset is to simplify comparison and charting of GHG data on a single-variable level.

How do I access GHG Data?

Data is available on Amazon S3, in JSON format, one file per inventory variable. The URL format is

http://ghg-data.s3-website.eu-central-1.amazonaws.com/VARIABLE-UID.json

The uid should be CAPITALIZED.

The response is JSON in the following format:

{"years":["list","of","years"],
 "series":{
  "<party-code>":["list","of","values"]}
}

Where:

  • "list","of","years" is a list of strings with year names (brows back down and see below in gotchas) sorted alphabetically
  • party-code is a three-letter code of the Party. In most cases, but not always, this is an ISO ALPHA-3 code.
  • "list","of","values" is a list of record values sorted according to the years in "list","of","years"

Where do I get the variable uid?

This is outside of the scope of this README. The short answer is that all variables are defined in UNFCCC metadata available here. If you are a user of UNFCCC CRF Reporter, you may see variable UIDs when you export reporting tables with uids. If you are a user of Spherical's National Inventory System, you will find uids of variables on cell info boxes on all data entry and reporting views. If you are neither, making sense of variable uids is not easy. Ask Spherical, we will help.

Gotchas

"Life is really simple, but we insist on making it complicated" - Confucius

Non-numeric year names

Years are not numbered but rather named. This is because Parties are free to name their reporting years the way they like, and Hungary used this freedom to name one of their years "1985-1987". In addition to that, there is a year that is used as baseline for calculating the Party's performance in GHG reduction. This year is named "Base Year". Most of the time, you will not be needing these years but you'll need to filter them out on your side.

Non-ISO country codes

Most country codes are ISO country codes. A UNFCCC-invented three-letter codes are used where an ISO country code is not available for a reporting entity. In particular:

  • Sub-countries reporting separately:
    • Belgium: BRU is Brussels, WAL is Wallonia, FLA is Flanders
    • UK: GBE is UK excluding overseas territories that are not part of EU
  • Countries reporting under the Convention and under the Kyoto Protocol separately:
    • Denmark: DKE is for the 1st commitment period of the Kyoto Protocol, DNM is for the 2nd
    • France: FRK is France's report under the Kyoto Protocol
    • UK: GBK is UK's report under the Kyoto Protocol
  • Non-countries considered Parties to UNFCCC
    • EU: EUA is European Union, EUC is European Union's report under the Kyoto Protocol

Funny numbers

All numbers in the inventory are floating point numbers, with all floating number fun to be expected. In addition to that, some data may be a result of complex calculations in national or UN software that are not rounded properly to make sense. Do not be surprised to see a country reporting a quarter of a cow and handle it appropriately in your solutions.

Nulls

According to the rules, complete GHG inventories shall not have empty records or zeroes. At the same time, there is a number of situations when a record does not contain a valid numeric value:

  • The variable is non-numeric
  • The Party could not report a number for some reason (the data point is zero, confidential, included in another variable or unavailable)
  • The year is not applicable for the Party

In these cases the dataset will include null for the record. GHG management software usually treats most of such records as zeroes.

How fresh is the dataset?

The dataset is based on the latest 2017 GHG inventory submissions.

Come on, give me some uids to test my charts!

Sure!

A simple matplotlib-based demo in chart.py shows the great progress of EU countries in reducing Methane emissions:

Methane Down

Legal status of this data

All data is produced by national governments and officially reported to the UN. Data is further dedicated to public domain by UNFCCC. This work, presented by Spherical, is a repackaging of public domain data which Spherical further dedicates to public domain. Important notes:

  • Although data has not been modified, no warranty of any kind is provided as to its accuracy, authenticity or integrity. This is not an official source. If you require officially sourced data, you will need to source it from the respective national government or from UNFCCC directly.
  • Continuous availability of data is not pledged. The service may be interrupted or discontinued without notice.
  • Programming errors and irregularities in the original dataset may have led to errors in this data. No responsibility is assumed for such errors. If you believe that you have found an error, please let us know.
  • We also reserve the right to change the API at any moment and without notice. Such changes will be made primarily to enrich data offered and therefore have backward compatibility. If you are using the dataset, you are advised to program your solutions in a way that they are tolerant to the expansion of the schema and changes to data volume.

About

Greenhouse gas emissions data packaged for easy exploration and charting


Languages

Language:Python 100.0%