-
Notifications
You must be signed in to change notification settings - Fork 12
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
Provide function to access employment counts #43
Comments
We have this type of functionality in the model building package useeior. We're using useeior to build state-level two region environmentally-extended input-output models and calculate equivalents to multipliers, including for employment. The environmental extensions are totally optional. Here is an example model output for Colorado with link that include the description of the code that was used. Due to resource constraints and a small team maintaining all of our Tools for Industrial Ecology Modeling of which this package is a part of, we don't plan to add that kind of equivalent functionality into stateior at this time. thanks for your interest! |
I see. That looks a lot more complicated to use. Would you consider PRs to add this kind of functionality to |
Sure, exporting more functions or wrapping them with some simple functionality is fine. Thanks for your offer, i look forward to reviewing the PR. |
Opened #44 |
Calculating employment multipliers requires access to per-industry employment averages. Right now
stateior
does not, as far as I know, provide any way to access that information, despite the fact that that information is used in producing the IO tables. Sectoral employment from elsewhere (e.g. QCEW) generally does not align with the BEA Summary IO 2012 Schema. I am able to get the necessary information using the following code, mostly cribbed from getStateEmploymentbyBEASummary:stateior
should simply export a function likegetStateEmploymentTable
to make employment data accessible.ASIDE: Why not do the same for the Leontief matrices?
The text was updated successfully, but these errors were encountered: