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

Updates to support BEA 2017 Schema data release #280

Merged
merged 88 commits into from
Mar 19, 2024
Merged

Conversation

bl-young
Copy link
Collaborator

@bl-young bl-young commented Feb 28, 2024

  • Adds data objects for 2017 schema using new schema suffix: _17sch
    • 2017 Detail tables (Make, Use, Supply, Use_SUT)
    • 2017-2022 Summary tables
    • 2017 MasterCrosswalk
    • 2012 schema objects renamed with _12sch
  • Drops support for building sector level models
  • Adjusts downloading of BEA data to store objects within local/USEEIO-Input folder
  • Implemented warning if sectors in TbS do not align with model schema (e.g., TbS w/ 2012 NAICS which does not align with the model crosswalk); this could be updated to allow for more NAICS mapping within the satellite table in the future.
  • Adds test for detail and summary model w/ 2017 schema (v3.0)

WesIngwersen and others added 30 commits October 12, 2023 09:23
… data read function names to remove 2012schema or 2012 as they function without that to grab newest data
# Conflicts:
#	data-raw/BEAData_Detail.R
@bl-young bl-young marked this pull request as ready for review February 28, 2024 21:56
@bl-young
Copy link
Collaborator Author

ok @WesIngwersen I think this should be ready to go.

@WesIngwersen
Copy link
Collaborator

Please check that the Sector level IO tables are never loaded for a supporting purpose

@WesIngwersen
Copy link
Collaborator

WesIngwersen commented Mar 6, 2024

I see one modelspec updated - the 2.1 model. Let's not use that specfor 2.1.. That should be a 3.0.

@bl-young
Copy link
Collaborator Author

bl-young commented Mar 6, 2024

I see one modelspec updated - the 2.1 model. Let's not use that specfor 2.1.. That should be a 3.0.

Yes I didn't have a great handle for how we wanted to handle the naming schema for models using 2017 IO schema. I can change it to 3.0

@bl-young
Copy link
Collaborator Author

Please check that the Sector level IO tables are never loaded for a supporting purpose

I am not seeing any.

I see one modelspec updated - the 2.1 model. Let's not use that specfor 2.1.. That should be a 3.0.

Ok this is done.

@bl-young
Copy link
Collaborator Author

new errors in testing arising only on mac seem to be associated with the new release of arrow 15.0.1 (was passing under 14.0.0.2)

@bl-young bl-young merged commit 4317133 into develop Mar 19, 2024
6 of 8 checks passed
@bl-young bl-young deleted the 2017MakeUse branch March 19, 2024 03:31
@bl-young bl-young mentioned this pull request Mar 22, 2024
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

Successfully merging this pull request may close these issues.

2 participants