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

Allow FERC 714 eia_code values to be categorized differently in different years #678

Open
zaneselvans opened this issue Jul 9, 2020 · 0 comments
Labels
ferc714 Anything having to do with FERC Form 714 glue PUDL specific structures & metadata. Stuff that connects datasets together.

Comments

@zaneselvans
Copy link
Member

Right now we assume that each eia_code in the respondent_id_ferc714 table is associated with either a balancing authority or a utility, across all the years for which there is data. However, we could also categorize them differently on a per-year basis, since over the last 14 years it's possible that some of the entities have gone from reporting as utilities to BAs or vice versa.

It's unclear whether this is necessary, or if it would improve our overall ability to accurately re-allocate demand geographically.

The planning_area_description_ferc714 table might be helpful in figuring this out, as it lists the names of all the utilities which are associated with each value of respondent_id_ferc714 -- it seems like the respondents that are themselves utilities ought to just be associated with... themselves?

We can also compare our categorizations against the ones which were done by hand in Auffhammer et al., at least in outline.

@zaneselvans zaneselvans added glue PUDL specific structures & metadata. Stuff that connects datasets together. ferc714 Anything having to do with FERC Form 714 labels Jul 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ferc714 Anything having to do with FERC Form 714 glue PUDL specific structures & metadata. Stuff that connects datasets together.
Projects
None yet
Development

No branches or pull requests

1 participant