NOTE: This Power Watch database of power plants is currently in draft status and not yet published. Please do not reference or cite the data as basis for research or publications until the data is officially published.
This project aims to build an open database of all the power plants in the world. It is the result of a large collaboration involving many partners, coordinated by the World Resources Institute and Google Earth Outreach. If you would like to get involved, please email Johannes Friedrich (jfriedrich@wri.org), or fork the repo and code!
If you're just looking for the data, the latest database is available in CSV format here. Please note this is a BETA version, and is not an official WRI publication.
This work is made possible and supported by Google.
All code and data for this project are published under a Creative Commons-Attribution 3.0 United States (CC BY 3.0 US) license.
The PowerWatch database is built in several steps.
- The first step involves gathering and processing country-level data. In some cases, these data are read automatically from offical government websites; the code to implement this is in the build_databases directory.
- In other cases we gather country-level data manually. These data are saved as public Google Fusion Tables, and are read into the processing chain using the build_database_WRI.py script in the build_database directory.
- The second step is to integrate data from different sources, particularly for geolocation of power plants and annual total electricity generation. Some of these different sources are multi-national databases. For this step, we rely on offline work to match records; the concordance table mapping record IDs across databases is saved in resources/master_plant_concordance.csv.
Throughout the processing, we represent power plants as instances of the PowerPlant class, defined in powerwatch.py. The final database is in a flat-file CSV format.
The database includes the following indicators:
- Plant name
- Fuel type(s)
- Generation capacity
- Country
- Ownership
- Latitude/longitude of plant
- Data source
- Data source year
- Annual generation
- Annual generation year
We will expand this list in the future as we extend the database.
We define the "Fuel Type" attribute of our database based on common fuel categories. In order to parse the different fuel types used in our various data sources, we map fuel name synonyms to our fuel categories here. We plan to expand the database in the future to report more disaggregated fuel types.
A major challenge for this project is that data come from a variety of sources, including government ministries, utility companies, equipment manufacturers, crowd-sourced databases, financial reports, and more. The reliability of the data varies, and in many cases there are conflicting values for the same attribute of the same power plant from different data sources. To handle this, we match and de-duplicate records and then develop rules for which data sources to report for each indicator. We provide a clear data lineage for each datum in the database. We plan to ultimately allow users to choose alternative rules for which data sources to draw on.
To the maximum extent possible, we read data automatically from trusted sources, and integrate it into the database. Our current strategy involves these steps:
- Automate data collection from machine-readable national data sources where possible.
- For countries where machine-readable data are not available, gather and curate power plant data by hand, and then match these power plants to plants in other databases, including GEO and CARMA (see below) to determine their geolocation.
- For a limited number of countries with small total power-generation capacity, use data directly from Global Energy Observatory (GEO).
A table describing the data source(s) for each country is listed below.
Finally, we are examining ways to automatically incorporate data from the following supra-national data sources:
- Clean Development Mechanism
- ENTSO-E
- E-PRTR
- CARMA
- Arab Union of Electricity
- IAEA PRIS
- Industry About
- Think Geo Energy
- WEC Global Hydropower Database
We assign a unique ID to each line of data that we read from each source. In some cases, these represent plant-level data, while in other cases they represent unit-level data. In the case of unit-level data, we perform an aggregation step and assign a new, unique plant-level ID to the result. For plants drawn from national data sources, the reference ID is formed by a three-letter country code ISO 3166-1 alpha-3 and a six-digit number. For plants drawn from other database, the reference ID is formed by a five-letter prefix code and a six-digit number.
In many cases our data sources do not include power plant geolocation information. To address this, we attempt to match these plants with the GEO and CARMA databases, in order to use that geolocation data. We use an elastic search matching technique developed by Enipedia to perform the matching based on plant name, country, capacity, location, with confirmed matches stored in a concordance file. This matching procedure is complex and the algorithm we employ can sometimes wrongly match two power plants or fail to match two entries for the same power plant. We are investigating using the Duke framework for matching, which allows us to do the matching offline.
Methods:
- "A" = automated with a dedicated build_database script
- "M/A" = currently manual, working to automate
In all other cases, we use manual data or GEO data. In a few cases, multiple methods are used for a single country. Further details are available in the country information file.
| Country | Method | Source(s) |
|---|---|---|
| Argentina | A | MINEM |
| Australia | A | AREMI |
| Belgium | M/A | ELIA |
| Brazil | A | ANEEL |
| Canada | M/A | PFF |
| Chile | A | CNE |
| China | A,M | Sourcewatch (coal) |
| Finland | M/A | EA |
| India | M/A | CEA, RRI |
| Mexico | M/A | SENER |
| Portugal | M/A | INEGI |
| Switzerland | M/A | BFE |
| Turkey | M/A | MENR |
| United Kingdom | A | DUKES, REPD |
| United States | A | EIA |
| Uruguay | M/A | MIEM |