Update EIA 757A column mapping to correctly rename columns#5107
Merged
Update EIA 757A column mapping to correctly rename columns#5107
Conversation
zaneselvans
approved these changes
Mar 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Closes #4722
What problem does this address?
EIA 191 and 757A extraction was not renaming columns as expected. The problem is partially addressed in #5058, but this extends the solution to EIA 757A.
What did you change?
Correctly call the
any_yearpartition in the extractor. Rename the columns to match our naming protocols rather than the exported names from EIA, and test that the raw columns are correctly renamed.Testing
How did you make sure this worked? How can a reviewer verify this?
Test the extraction and verify that column names are not what they were in the original source files.
To-do list
pixi run pre-commit-runto run linters and static code analysis checks.pixi run pytest-cilocally to ensure that the merge queue will accept your PR.