|
|
| Line 28: |
Line 28: |
| | *Ability to track changes on a power plant site? A wind farm may be built in stages, generators may be decommissed, upgraded, etc. Primary fuel used may change as well. | | *Ability to track changes on a power plant site? A wind farm may be built in stages, generators may be decommissed, upgraded, etc. Primary fuel used may change as well. |
| | *What format will the data be published in? Will it be machine-readable? The [http://www.bundesnetzagentur.de/cln_1932/DE/Sachgebiete/ElektrizitaetundGas/Unternehmen_Institutionen/Versorgungssicherheit/Erzeugungskapazitaeten/Kraftwerksliste/kraftwerksliste-node.html BNetzA xls database] is mostly ok in this regard, but columns like ''Spezifizierung "Mehrere Energieträger" und "Sonstige Energieträger" - Hauptbrennstoff'' are difficult to parse consistently. | | *What format will the data be published in? Will it be machine-readable? The [http://www.bundesnetzagentur.de/cln_1932/DE/Sachgebiete/ElektrizitaetundGas/Unternehmen_Institutionen/Versorgungssicherheit/Erzeugungskapazitaeten/Kraftwerksliste/kraftwerksliste-node.html BNetzA xls database] is mostly ok in this regard, but columns like ''Spezifizierung "Mehrere Energieträger" und "Sonstige Energieträger" - Hauptbrennstoff'' are difficult to parse consistently. |
| | + | **Best would be to provide data in different formats: Georeferenced database table (online accessible and downloadable dump) and Spreadsheet. To keep costs low, spreadsheet should be derived from database table. |
| | + | |
| | *It might be useful to suggest collecting use cases for the data to help ensure that what is being gathered can help to answer real research problems. | | *It might be useful to suggest collecting use cases for the data to help ensure that what is being gathered can help to answer real research problems. |
| | **e.g. "be able to sum up all CO2 emissions for all facilities owned by company X and all its subsidiaries" - for this to be answered, the data structures need to provide links both between organizations and from organizations to their facilities. In other words, through this exercise we're mapping out what types of data should ideally be linked to what other types of data. This isn't just about putting data in tables, it's about if we can link data spread across multiple tables. | | **e.g. "be able to sum up all CO2 emissions for all facilities owned by company X and all its subsidiaries" - for this to be answered, the data structures need to provide links both between organizations and from organizations to their facilities. In other words, through this exercise we're mapping out what types of data should ideally be linked to what other types of data. This isn't just about putting data in tables, it's about if we can link data spread across multiple tables. |
| Line 34: |
Line 36: |
| | **Best longitude and latitude, Ok adress data | | **Best longitude and latitude, Ok adress data |
| | | | |
| − | *... | + | *...<br/> |
| | | | |
| | <br/>[1] [http://opendatacommons.org/licenses/odbl/ http://opendatacommons.org/licenses/odbl/] (also used by OpenStreetMap)<br/><br/><br/> | | <br/>[1] [http://opendatacommons.org/licenses/odbl/ http://opendatacommons.org/licenses/odbl/] (also used by OpenStreetMap)<br/><br/><br/> |
Revision as of 09:55, 13 August 2015
Germany (BMWi, BNetzA) plans to to develop a register of power plant data that covers all plants (“starting from 0 kW”) that supersedes the current “EEG Stammdatenbank” and the “BNetzA Kraftwerksliste”.
- geographic scope: Germany
- content: capacity, technical characteristics, detailed information such as hub height of wind turbines (“master data”)
- detail: individual blocks
- go-live: early 2017
- not included: time series of any sort; yearly generation data
- license: BMWi and BNetzA has not thought about a license yet
http://www.bundesnetzagentur.de/DE/Sachgebiete/ElektrizitaetundGas/Unternehmen_Institutionen/DatenaustauschundMonitoring/MaStR/Datendefinitionen/mastr_datendefinitionen-node.html
The consultation process is open now until end of August 2015. This page collects issue we would like to raise in the consultation.
- we support such a register
- the register should “think” European, be compatible with existing registers elsewhere.'Do we have specific examples? (ORISPL - Office of Regulatory Information System Plant Location (US)')
- should be published under an open license. (suggesting ODbL? [1])
- the coverage of the data should become clear (e.g., "X% of all capacity is included; most missing capacity is small-scale gas-fired plants")
- There are > 800k PV installations - will these be included?
- Does Stromerzeugungsanlagen (EAS) distinguish between generators and boilers?
- Form EIA-923 & Form EIA-860 are excellent examples of how to manage data on the power sector
- Are market roles and functions linked? Or would we have to deduplicate things by hand? Also, what about companies that may have a joint partnership in a power plant? Or subsidiaries? Relations that change over time? Mergers & splits?
- Ability to track changes on a power plant site? A wind farm may be built in stages, generators may be decommissed, upgraded, etc. Primary fuel used may change as well.
- What format will the data be published in? Will it be machine-readable? The BNetzA xls database is mostly ok in this regard, but columns like Spezifizierung "Mehrere Energieträger" und "Sonstige Energieträger" - Hauptbrennstoff are difficult to parse consistently.
- Best would be to provide data in different formats: Georeferenced database table (online accessible and downloadable dump) and Spreadsheet. To keep costs low, spreadsheet should be derived from database table.
- It might be useful to suggest collecting use cases for the data to help ensure that what is being gathered can help to answer real research problems.
- e.g. "be able to sum up all CO2 emissions for all facilities owned by company X and all its subsidiaries" - for this to be answered, the data structures need to provide links both between organizations and from organizations to their facilities. In other words, through this exercise we're mapping out what types of data should ideally be linked to what other types of data. This isn't just about putting data in tables, it's about if we can link data spread across multiple tables.
- Include spatial data
- Best longitude and latitude, Ok adress data
[1] http://opendatacommons.org/licenses/odbl/ (also used by OpenStreetMap)
