stateior

Prepares US state two-region Make and Use tables

https://github.com/usepa/stateior

Science Score: 49.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
    Found 5 DOI reference(s) in README
  • Academic publication links
    Links to: zenodo.org
  • Committers with academic emails
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (17.2%) to scientific vocabulary

Keywords

ord

Keywords from Contributors

interpretability standardization hack
Last synced: 7 months ago · JSON representation

Repository

Prepares US state two-region Make and Use tables

Basic Info
  • Host: GitHub
  • Owner: USEPA
  • License: mit
  • Language: R
  • Default Branch: master
  • Homepage:
  • Size: 143 MB
Statistics
  • Stars: 10
  • Watchers: 7
  • Forks: 14
  • Open Issues: 4
  • Releases: 5
Topics
ord
Created over 5 years ago · Last pushed 12 months ago
Metadata Files
Readme License Zenodo

README.md

stateior

R CI/CD test DOI StateIO paper <!-- badges: end -->

stateior is an R package for building multi-regional economic input-output (MRIO) tables of states in the United States, refered to as StateIO models. Currently, stateior is capable of creating IO tables for each US state and building two-region MRIO models based on those state IO tables at the BEA Summary level of resolution in the US for all years from 2012-2020. The two regions are State of Interest (SoI) and Rest of the US (RoUS). stateior was initially conceived in support of creating state-specific versions of USEEIO models, but may be used for other purposes where state input-output tables are used. The methodology used to build the StateIO models is described in a paper in International Regional Science Review. The package is intended to add transparency and reproducibility to the complex process of generating subnational input-output tables, which are not compiled by any statistical agency.

stateior implements a robust commodity-industry modeling framework that models supply, use and trade of commodities by industries and final users in 50 U.S. states plus the District of Columbia and includes international import and export. stateior offers various functions for building, validating, visualizing, writing, and loading StateIO models. stateior is in a beta development state while the complete methodology and StateIO data products are under external peer-review.

See the Wiki for advanced uses, details about modeling approach, data and metadata, and how to contribute to stateior.

Usage

There are two primary ways to use stateior. 1. To access the final data products in an R environment. This usage is the most simple and rapid and all that is required where the intention is only to review and use the two-region Make and Use tables. 2. To study, run, modify the source code for any or all of the model building steps, from raw data acquisition to final two-region table assembly. This is a developer use.

Use for Accessing Final Data Products (usage type #1)

Install the most recent release version of stateior and attach it to the current R session. See Releases for all previously released versions. Note these steps will automatically install other R packages required by devtools and stateior.

r install.packages("devtools") devtools::install_github("USEPA/stateior") library(stateior)

```r

For a specific release:

devtools::install_github("USEPA/stateior@0.2.1") ```

Load desired StateIO data. See One Region Data and Two Region Data for names and details of one- and two-region MRIO data sets that are currently available, respectively.

```r

One-Region Data

Load the state one-region (state only) domestic Use tables for 2012 for all states.

This will download the data product from a remote server and load it into your R session as an R list.

OneRegionDomesticUse2012 <- loadStateIODataFile("StateSummaryDomesticUse2012")

Select the Georgia Use table.

This will put this table into a standard R data frame named 'GADomesticUse2012'.

GADomesticUse2012 <- OneRegionDomesticUse_2012[["Georgia"]]

Two-Region Data

Load the two-region domestic Use tables for 2012 for all states.

This will download the data product from a remote server and load it into your R session as an R list.

TwoRegionDomesticUse2012 <- loadStateIODataFile("TwoRegionSummaryDomesticUse2012")

Select the two-region Use table for Georgia and Rest of the US.

This will put this table into a standard R data frame named 'GATwoRegionDomesticUse2012'.

GATwoRegionDomesticUse2012 <- TwoRegionDomesticUse_2012[["Georgia"]] ```

If viewing either one-region or two-region data of a specific state in Excel spreadsheet is preferred, export it to a csv file in a given outputfolder.

```r

Export 2012 Georgia Use tables to a csv file.

writeStateIODatatoCSV <- ("StateSummaryDomesticUse_2012", "Georgia", outputfolder)

Export 2012 two-region Use table for Georgia and Rest of the US to a csv file.

writeStateIODatatoCSV <- ("TwoRegionSummaryDomesticUse_2012", "Georgia", outputfolder) ```

Employment data is also available for each state and year, containing employment by BEA Summary sector.

```r Employment_2012 <- getStateEmploymentTable(2012)

BEA2012Summary_Code State Emp

1 111CA Alabama 38191

2 113FF Alabama 15773

3 211 Alabama 4334

4 212 Alabama 8205

```

Industry output data is also available, and can be used to calculate the direct requirements matrix.

```r OneRegionIndustryOutput2012 <- loadStateIODataFile("StateSummaryIndustryOutput2012") GAIndustryOutput2012 <- OneRegionIndustryOutput_2012[["Georgia"]]

Drop extra rows from the DomesticUse table; these do not correspond to actual BEA Summary industries.

GADomesticUse2012 <- GADomesticUse2012[!rownames(GADomesticUse2012) %in% c("V001", "V002", "V003", "Used", "Other"), ]

Calculate the direct requirements matrix

GADirectRequirements2012 <- GADomesticUse2012 / GAIndustryOutput2012$Output ```

Use for Developers (usage type #2)

For studying, replicating or modify the code, users will want to clone or copy the source code and review the code in R. See more in Instructions for Developers.

Disclaimer

The United States Environmental Protection Agency (EPA) GitHub project code is provided on an "as is" basis and the user assumes responsibility for its use. EPA has relinquished control of the information and no longer has responsibility to protect the integrity , confidentiality, or availability of the information. Any reference to specific commercial products, processes, or services by service mark, trademark, manufacturer, or otherwise, does not constitute or imply their endorsement, recommendation or favoring by EPA. The EPA seal and logo shall not be used in any manner to imply endorsement of any commercial product or activity by EPA or the United States Government.

Owner

  • Name: U.S. Environmental Protection Agency
  • Login: USEPA
  • Kind: organization
  • Location: United States of America

GitHub Events

Total
  • Fork event: 5
  • Create event: 6
  • Release event: 2
  • Issues event: 13
  • Watch event: 3
  • Delete event: 6
  • Issue comment event: 28
  • Member event: 1
  • Push event: 105
  • Pull request review comment event: 2
  • Gollum event: 1
  • Pull request review event: 4
  • Pull request event: 16
Last Year
  • Fork event: 5
  • Create event: 6
  • Release event: 2
  • Issues event: 13
  • Watch event: 3
  • Delete event: 6
  • Issue comment event: 28
  • Member event: 1
  • Push event: 105
  • Pull request review comment event: 2
  • Gollum event: 1
  • Pull request review event: 4
  • Pull request event: 16

Committers

Last synced: about 2 years ago

All Time
  • Total Commits: 685
  • Total Committers: 5
  • Avg Commits per committer: 137.0
  • Development Distribution Score (DDS): 0.133
Past Year
  • Commits: 21
  • Committers: 4
  • Avg Commits per committer: 5.25
  • Development Distribution Score (DDS): 0.333
Top Committers
Name Email Commits
MoLi7 m****i@g****m 594
Elon Cha 5****a 46
GitHub Actions Bot 4****] 16
WesIngwersen i****y@e****v 15
Ben Young B****g@e****m 14
Committer Domains (Top 20 + Academic)

Issues and Pull Requests

Last synced: 10 months ago

All Time
  • Total issues: 25
  • Total pull requests: 29
  • Average time to close issues: 4 months
  • Average time to close pull requests: 18 days
  • Total issue authors: 8
  • Total pull request authors: 3
  • Average comments per issue: 3.6
  • Average comments per pull request: 0.76
  • Merged pull requests: 27
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 8
  • Pull requests: 9
  • Average time to close issues: 3 months
  • Average time to close pull requests: 21 days
  • Issue authors: 3
  • Pull request authors: 2
  • Average comments per issue: 2.88
  • Average comments per pull request: 0.67
  • Merged pull requests: 9
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • bl-young (9)
  • WesIngwersen (8)
  • brandones (2)
  • MoLi7 (1)
  • willspisak (1)
  • edwardxtgvivid (1)
  • alaitzaritza (1)
  • AZFARHAD24511 (1)
Pull Request Authors
  • bl-young (19)
  • MoLi7 (16)
  • brandones (2)
Top Labels
Issue Labels
enhancement (5) bug (4) Data Commons (3) invalid (1)
Pull Request Labels