The move from the PLEXOS-World dataset to the GEM datasets to determine existing powerplant capacities should be done given the below constraints;
As of now GEM datasets only exist for Coal, Gas, Solar (no distinction between CSP and PV) and Wind plants all in separate, slightly different formats (all long format with different column headers). Hydro, Geothermal, Nuclear and Biomass will follow late 2022 and/or 2023.
Total reported capacities from the datasets for Coal and Gas are in line with values as reported by other datasets (benchmarked with Ember/BP) and do not require additional 'Capacity Scalers' as applied in the PLEXOS-World model. Solar and Wind plants in the GEM dataset only cover >10 MW projects hence require Capacity Scalers.
Is your feature related to a bug?
No response
Suggested Soltuion
As a temporary solution, until all GEM datasets are available incl. for Hydro, Geothermal, Nuclear and Biomass, the OPG_powerplant_data script should make use of both datasets. GEM for Coal, Gas, Solar and Wind and PLEXOS-World for the others. This means that capacities for these other technologies will not be up to-date for the time being.
For countries with sub-country nodes, the allocation of individual powerplants from the GEM datasets (reported by country) to nodes can occur by matching the coordinates of said plant with coordinates of the nearest plant from the PLEXOS-World datasets. A more accurate method for future use would be to create shapefiles of all nodes and group plants that fall within the area of a certain shape/node.
For Solar and Wind 'Capacity Scalers' are required to scale total capacity values as reported by the GEM datasets (>10 MW plants) to total Solar and Wind capacities following benchmark datasets (e.g. IRENA) that include smaller projects/rooftop solar.
For countries with sub-country nodes, the allocation of these missing capacities (IRENA capacity - GEM capacity = missing capacity) should occur by means of a function (or separate script such as the mentioned OPG_powerplant_data_split_by_node script). The inputs for such a function/script would be I) a list of sub-country level proxy values that can be be used for the downscaling and II) the missing capacities by country. Default proxy values could be the relative share of capacities per node & technology following the GEM dataset, but the function/script should be setup in such a way that other proxy values could be read as well by means of the config file to allow for user flexibility.
A solution needs to be sought for other less common technologies (e.g. Oil, Ocean/Tidal) for which no current GEM datasets are in the pipeline.
Idea
The move from the PLEXOS-World dataset to the GEM datasets to determine existing powerplant capacities should be done given the below constraints;
Is your feature related to a bug?
No response
Suggested Soltuion
As a temporary solution, until all GEM datasets are available incl. for Hydro, Geothermal, Nuclear and Biomass, the OPG_powerplant_data script should make use of both datasets. GEM for Coal, Gas, Solar and Wind and PLEXOS-World for the others. This means that capacities for these other technologies will not be up to-date for the time being.
For countries with sub-country nodes, the allocation of individual powerplants from the GEM datasets (reported by country) to nodes can occur by matching the coordinates of said plant with coordinates of the nearest plant from the PLEXOS-World datasets. A more accurate method for future use would be to create shapefiles of all nodes and group plants that fall within the area of a certain shape/node.
For Solar and Wind 'Capacity Scalers' are required to scale total capacity values as reported by the GEM datasets (>10 MW plants) to total Solar and Wind capacities following benchmark datasets (e.g. IRENA) that include smaller projects/rooftop solar.
For countries with sub-country nodes, the allocation of these missing capacities (IRENA capacity - GEM capacity = missing capacity) should occur by means of a function (or separate script such as the mentioned OPG_powerplant_data_split_by_node script). The inputs for such a function/script would be I) a list of sub-country level proxy values that can be be used for the downscaling and II) the missing capacities by country. Default proxy values could be the relative share of capacities per node & technology following the GEM dataset, but the function/script should be setup in such a way that other proxy values could be read as well by means of the config file to allow for user flexibility.
A solution needs to be sought for other less common technologies (e.g. Oil, Ocean/Tidal) for which no current GEM datasets are in the pipeline.
Additional Info
No response