You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How does powerplantmatching decide if the pojectID refers to a plant's GEM location ID or GEM unit/phase ID?
For example, for the Staudinger power plant there are two units: The coal-fired unit has a list of GEM unit/phase IDs ('G100000109620', 'G100000109621', 'G100000109623', 'G100000109622') while the gas-fired unit is linked to the plant's GEM location ID ('L100000101908'). What is the underlying methodology for this matching?
Those columns are hardcoded into data.py. Have a look in there (just search for GEM location ID etc) and you will find where it has been renamed. Only the global gas power plant tracker uses GEM location ID.
projectID also has no effect on matching process. Only the other columns. As far as I know at least
Thanks for the explanation @lkstrp ! I might be missing something but wouldn't using GEM unit/phase ID across all trackers make more sense? Unles there is a specific reason for this choice, I might check if changing GGPT in data.py accordingly will break anything.
How does
powerplantmatching
decide if thepojectID
refers to a plant'sGEM location ID
orGEM unit/phase ID
?For example, for the Staudinger power plant there are two units: The coal-fired unit has a list of
GEM unit/phase ID
s ('G100000109620', 'G100000109621', 'G100000109623', 'G100000109622') while the gas-fired unit is linked to the plant'sGEM location ID
('L100000101908'). What is the underlying methodology for this matching?The text was updated successfully, but these errors were encountered: