Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improvement of integration GEM with powerplantmatching #1080

Open
ekatef opened this issue Aug 11, 2024 · 2 comments
Open

Improvement of integration GEM with powerplantmatching #1080

ekatef opened this issue Aug 11, 2024 · 2 comments

Comments

@ekatef
Copy link
Member

ekatef commented Aug 11, 2024

Have tested the idea to exclude non-Global Energy Monitor (GEM) data from the sources used by powerplantmatching. To do so, GEO and GPD have been commented out in configs/powerplantmatching.config.yaml.

Testing has been done for Uruguay as an example, and here are the outputs:

  1. Having the default set of sources gives in a more complete picture -- GEM-only powerplantmatching (ppm) search returns only less than 1/3 of the power plants found by the default ppm configuration.

  2. Interactions between GEM sources and others can have some side effects -- in case of Uruguay the default configuration lead to some mess for Punta Del Tigre power plant. In reality, there are two plants, the first consisting of 6 gas turbine blocks (300 MW in total), the second one being CCGT of 540 MW. If GEM only is used, it results in merging two blocks to a single CCGT of 840 MW, while the default configuration leads to double-counting of GTs as an additional fuelled block of 300MW.

  3. Installed wind generation capacity is completely lost from our data workflow for some reason, while in fact wind generates ~1/3 of the electricity. Interestingly, wind installed capacity presents in the online version of GEM.

Basically, it confirms what has been noticed before: adding GEM leads to a considerable decrease of the capacities which are found by ppm for each of the world regions.

It also appears that interaction of GEM with powerplantmatching can be improved. In particular, some side-effects of mixing GEM data with other data sources can be expected for the generation sites with a multiple power blocks with similar names. That is linked with the fact that ppm heavily relays on the names when making matching of the generation capacities.

Would be also great to capture more data on existing RES capacities, which could be probably resolved by updating or enhancing GEM resources included into ppm

@ekatef
Copy link
Member Author

ekatef commented Aug 11, 2024

Is linked with #407 and #753

@ekatef
Copy link
Member Author

ekatef commented Aug 11, 2024

Interestingly, wind power plants are included into the ppm, as it appears from the specification of the data sources included, there are data for the major wind power plants in Uruguay:
image

So, it appears that something goes wrong in matching for GEM, even without interactions with other databases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant