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

update detail industry spec for use in useeio #396

Merged
merged 6 commits into from
Dec 6, 2023
Merged
Show file tree
Hide file tree
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion flowsa/methods/flowbysectormethods/Detail_Make.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,6 @@ source_names:
activity_to_sector_mapping: BEA_2012_Summary
primary_action_type: Consumed # speeds processing
# Drop unneeded codes
exclusion_fields:
exclusion_fields:
ActivityConsumedBy: ['Other', 'Used', 'Total Industry Output']
ActivityProducedBy: ['Total Commodity Output']
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
# the exisiting summary level national FBS (method 1), except where Direct attribution
# is available at the detail level and uses the GHGI as the primary source

!include:BEA_detail_target.yaml
!include:USEEIOv2_detail_target.yaml
# year: &ghgi_year 2019
target_naics_year: 2012
geoscale: national
Expand Down Expand Up @@ -60,18 +60,22 @@ attribution_sources:
_sources_to_cache:
Detail_Use_YEAR: ## Update year
!include:Detail_Use_SUT.yaml
industry_spec: !include:USEEIOv2_detail_target.yaml:industry_spec
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm wondering if these FBS should still use the BEA_detail_target schema?

(I don't think it will make a difference in this case)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fine by me if you want to drop it - I agree that it won't make a difference for this FBS. I included the industry spec here because if we are pulling in an industry spec from Detail_USE_SUT.yaml, I figured we might as well pull in the target industry spec instead of what we have in the Detail Use yaml. But I don't have strong feelings

# year: *ghgi_year
source_names:
BEA_Summary_Use_SUT:
!include:Detail_Use_SUT.yaml:source_names:BEA_Summary_Use_SUT
industry_spec: !include:USEEIOv2_detail_target.yaml:industry_spec
# year: *ghgi_year

Detail_Supply_YEAR:
!include:Detail_Supply.yaml
industry_spec: !include:USEEIOv2_detail_target.yaml:industry_spec
# year: *ghgi_year
source_names:
BEA_Summary_Supply:
!include:Detail_Supply.yaml:source_names:BEA_Summary_Supply
industry_spec: !include:USEEIOv2_detail_target.yaml:industry_spec
# year: *ghgi_year

source_names:
Expand Down
37 changes: 37 additions & 0 deletions flowsa/methods/flowbysectormethods/USEEIOv2_detail_target.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
# This file can be used to set up target NAICS for a detail level model
# NAICS are targeted to enable 1:1 correspondence between NAICS and BEA
# Detail sectors. The waste sectors (562) are targeted to NAICS 6 and NAICS
# to align with the waste disaggregation in useeior

# To use in an FBS method add
# !include:USEEIOv2_detail_target.yaml
# to the top of the method replacing the three parameters below


industry_spec:
default: NAICS_3
NAICS_4: ['111', '112', '212', '221', '311', '312', '313', '314',
'321', '327', '331', '332', '334', '336', '337', '423',
'424', '512', '515', '517', '518', '522', '523', '524',
'532', '541', '561', '611', '621', '623', '624', '711',
'713', '722', '811', '812', '813',]
NAICS_5: ['1111', '1121', '2122', '2123', '3112', '3114', '3115',
'3118', '3119', '3121', '3141', '3219', '3221', '3222',
'3231', '3241', '3251', '3253', '3255', '3256', '3259',
'3261', '3262', '3273', '3279', '3314', '3315', '3323',
'3324', '3327', '3331', '3339', '3342', '3346', '3351',
'3352', '3359', '3361', '3363', '3371', '3399', '5111',
'5112', '5191', '5241', '5416', '5419']
NAICS_6: ['23', '21311', '31111', '31122', '31151', '31161', '32229',
'32311', '32412', '3252', '3254', '32799', '33131',
'33141', '33211', '33291', '33299', '33311', '33324',
'33331', '33341', '33351', '33361', '33391', '33399',
'33411', '33441', '33451', '33522', '33531', '33591',
'33599', '33611', '33621', '33641', '33661', '33699',
'33712', '33721', '33911', '51731', '52411', '54151',
'562', '72251','92', 'F010']
NAICS_7: ['562212', '562219', '562920']
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm trying to remember where we define the 7-digit sectors for waste?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

waste naics are defined here in the HIO repo - we should add those names to crosswalks in flowsa for 2012 and 2017 naics. I can do that in a few hours

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the 7-digit waste NAICS are included in the flowsa naics crosswalks


target_naics_year: 2017
# This schema was created for 2017 NAICS but should also work for the schema
# for the 2012 tables using 2012 NAICS
Loading