-
Notifications
You must be signed in to change notification settings - Fork 23
Home
flowsa has two objectives:
-
Import environmental (and other types of) data from publicly available datasets, formatting the data into a standardized table, a FlowByActivity dataset. FlowByActivity datasets are largely unchanged from the original data source, with the exception of formatting. Data that are currently available in the FlowByActivity format are listed here. See Creating a FlowByActivity Dataset for details on methodology.
-
Attribute resource use, waste, emissions, and loss to 6-digit North American Industrial Classification (NAICS) Codes, which are economic activities, formatting the data into a standardized FlowBySector table. These new datasets are generally created using multiple FlowByActivity datasets. A list of available FlowBySector datasets can be found here, with a more detailed explanation of methodology found in Creating a FlowBySector Dataset.
- FlowBySector example: The main data source for creating a "Water" FlowBySector table is the USGS, which publishes national water withdrawal information for nine broad categories. One of these categories is "Irrigation Crop", which can only be mapped to 3-digit NAICS ('111' and '112'). To reach the objective of mapping water withdrawal information to 6-digit NAICS, additional FlowByActivity datasets are called on for allocation purposes. In the case of "Irrigation Crop", acreage by crop type and water application rates (gal/acre) by crop type are multiplied to calculate water use by crop type at the 6-digit NAICS. A ratio is calculated for the quantity of water used by a crop out of the total water use calculated using the USDA datasets. This ratio is then multiplied by the USGS water withdrawal information for "Irrigation Crop", allocating the 3-digit NAICS to 6-digits.
- Acreage information is published in the US Department of Agriculture (USDA) Census of Agriculture (CoA) and water application rates are published in the USDA Irrigation and Water Management Survey (IWMS).
- FlowBySector example: The main data source for creating a "Water" FlowBySector table is the USGS, which publishes national water withdrawal information for nine broad categories. One of these categories is "Irrigation Crop", which can only be mapped to 3-digit NAICS ('111' and '112'). To reach the objective of mapping water withdrawal information to 6-digit NAICS, additional FlowByActivity datasets are called on for allocation purposes. In the case of "Irrigation Crop", acreage by crop type and water application rates (gal/acre) by crop type are multiplied to calculate water use by crop type at the 6-digit NAICS. A ratio is calculated for the quantity of water used by a crop out of the total water use calculated using the USDA datasets. This ratio is then multiplied by the USGS water withdrawal information for "Irrigation Crop", allocating the 3-digit NAICS to 6-digits.
- Flow-By-Activity parquets
- Flow-By-Sector parquets
- Metadata JSON
- General Log
- Validation Log
- FlowBySector datasets are used in the USEEIO modeling efforts, where the NAICS are mapped to BEA sector codes and transformed into satellite tables for the purposes of environmentally-extended input-output modeling.
flowsa is developed and maintained by Office of Research & Development (ORD), Center for Environmental Solutions & Emergency Response (CESER), Land Remediation & Technology Division (LRTD), Environmental Decision Analytics Branch (EDAB), U.S. Environmental Protection Agency, Cincinnati, OH 45268. See OMB Memorandum M-16-21 Section 4 & Releasing Open Source Code.
Objectives
Projects Using FLOWSA Output
Install & Run
Example Code
Reading Parquet Files
Using FLOWSA
Loading External FBS Method YAMLs
API Keys
Troubleshooting
Contributing
Creating a Flow-By-Activity Dataset
Creating a Flow-By-Activity Crosswalk
Creating a Flow-By-Sector Dataset
FBA and FBS Naming Convention
NAICS Crosswalk
Available Data
Flow Classes
Flow-By-Activity Datasets
Flow-By-Sector Datasets
Data Storage
EPA's Tools for Industrial Ecology
Suggested Citations for FLOWSA and FBS Data
Publications and Presentations
Acknowledgements