Data Access
There are many different ways to download or access OEPS data, find the one that works best for you. You may also be interested in our code resources page with notebooks and tutorials.
Direct Download
Aggregated Data Packages
OEPS contains data for 300+ variables split across 50+ CSV files, at 4 different geography levels (state, county, tract, and zip-code tabulation area). The scope of this content can make data access complex, so we have created two consolidated data packages (DSuite2018 and DSuite2023) to make it as easy as possible to get started. Each package contains:
- Four data CSVs, one each for geography level.
- A data dictionary (MS Excel format) summarizing which data year is included for each variable.
- A corresponding geometry file for each CSV (zipped shapefile).
- Markdown-formatted metadata documents for each variable.
- JSON schemas for all content, following Frictionless Data Package v1 specifications.
DSuite2018
The 2018 data package is centered around the 2018 ACS. In some cases variables are not available in that year, so we have included content from within a few years. The year for each data point is listed in the data dictionary.
DSuite2023
The 2023 data package is centered around the 2023 ACS. In some cases variables are not available in that year, so we have included content from within a few years. The year for each data point is listed in the data dictionary.
All data by year
Looking for historical data, or years outside of what is included in the data packages above? Use the individual CSVs listed below to find what you need. CSVs are grouped by geography (state, county, tract, zcta), and tend to be consolidated one-per-year. However, you may see some exceptions to this where data from the same year must be joined to different geography files.
We have generated a data dictionary for each geography level that summarizes what variables and which years are available.
State
Data Year | File | Join to |
---|---|---|
1980 | state-1980.csv | geo-2010-state |
1990 | state-1990.csv | geo-2010-state |
2000 | state-2000.csv | geo-2010-state |
2010 | state-2010.csv | geo-2018-state |
2010 | state-providers-2010.csv | geo-2018-state |
2013 | state-2013.csv | geo-2018-state |
2014 | state-2014.csv | geo-2018-state |
2015 | state-2015.csv | geo-2018-state |
2016 | state-2016.csv | geo-2018-state |
2017 | state-2017.csv | geo-2018-state |
2018 | state-2018.csv | geo-2018-state |
2019 | state-2019.csv | geo-2018-state |
2020 | state-2020.csv | geo-2018-state |
2021 | state-2021.csv | geo-2018-state |
2022 | state-2022.csv | geo-2020-state |
2023 | state-2023.csv | geo-2020-state |
2025 | state-2025.csv | geo-2020-state |
County
Data Year | File | Join to |
---|---|---|
1980 | county-1980.csv | geo-2010-county |
1990 | county-1990.csv | geo-2010-county |
2000 | county-2000.csv | geo-2010-county |
2010 | county-2010.csv | geo-2010-county |
2010 | county-providers-2010.csv | geo-2018-county |
2014 | county-2014.csv | geo-2018-county |
2015 | county-2015.csv | geo-2018-county |
2016 | county-2016.csv | geo-2018-county |
2017 | county-2017.csv | geo-2018-county |
2018 | county-2018.csv | geo-2018-county |
2019 | county-2019.csv | geo-2018-county |
2020 | county-2020.csv | geo-2018-county |
2021 | county-2021.csv | geo-2018-county |
2022 | county-2022.csv | geo-2020-county |
2023 | county-2023.csv | geo-2020-county |
2025 | county-2025.csv | geo-2020-county |
Tract
Data Year | File | Join to |
---|---|---|
1980 | tract-1980.csv | geo-2010-tract |
1990 | tract-1990.csv | geo-2010-tract |
2000 | tract-2000.csv | geo-2010-tract |
2010 | tract-ruca-2010.csv | geo-2018-tract |
2010 | tract-2010.csv | geo-2018-tract |
2010 | tract-providers-2010.csv | geo-2018-tract |
2014 | tract-sdoh-2014.csv | geo-2018-tract |
2014 | tract-2014.csv | geo-2018-tract |
2018 | tract-2018.csv | geo-2018-tract |
2019 | tract-2019.csv | geo-2018-tract |
2020 | tract-2020.csv | geo-2018-tract |
2021 | tract-2021.csv | geo-2018-tract |
2022 | tract-2022.csv | geo-2020-tract |
2023 | tract-2023.csv | geo-2020-tract |
2025 | tract-2025.csv | geo-2020-tract |
Zip Code Tabulation Area (ZCTA)
Data Year | File | Join to |
---|---|---|
2010 | zcta-ruca-2010.csv | geo-2018-zcta |
2018 | zcta-2018.csv | geo-2018-zcta |
2019 | zcta-2019.csv | geo-2018-zcta |
2020 | zcta-2020.csv | geo-2018-zcta |
2021 | zcta-2021.csv | geo-2018-zcta |
2022 | zcta-2022.csv | geo-2020-zcta |
2023 | zcta-2023.csv | geo-2020-zcta |
2025 | zcta-2025.csv | geo-2020-zcta |
Geography Files
For spatial analysis, OEPS CSVs must be joined to geographic data from the US Census Bureau's Cartographic Boundary files (500k scale). Direct download links are provided below for the following formats: Shapefile, GeoJSON, or PMTiles. Make sure to pick the correct join file for your dataset, based on the tables above.
Id | Download links |
---|---|
geo-2010-county | shp, geojson, pmtiles |
geo-2010-state | shp, geojson, pmtiles |
geo-2010-tract | shp, geojson, pmtiles |
geo-2018-county | shp, geojson, pmtiles |
geo-2018-state | shp, geojson, pmtiles |
geo-2018-tract | shp, geojson, pmtiles |
geo-2018-zcta | shp, geojson, pmtiles |
geo-2020-county | shp, geojson, pmtiles |
geo-2020-state | shp, geojson, pmtiles |
geo-2020-tract | shp, geojson, pmtiles |
geo-2020-zcta | shp, geojson, pmtiles |
You can learn more about how we prepare and generate these geography files at geodata.healthyregions.org ↗ .
Tips for joining to geography files:
- Make sure to link each CSV with the proper geometry file, using the tables above.
- Use the HEROP_ID field to join, it is present in all CSV and geometry files (other common identifiers like ZIP5 or FIPS may also be available).
- In Connecticut: For county and tract data from 2022 or later you should use 2022 geographies (not yet provided here) because county (and therefore tract) FIPS ids changed between 2021 and 2022. To translate 2022 tracts back to 2020 geometries, you can use these crosswalks from CT Data Collaborative.
Programmatic Access
oepsData — R Package
We maintain a small R package called oepsData. This package is the best way for researchers who use R to load and analyze OEPS data directly, without the need to download CSVs or Shapefiles and worry about joins.
- Documentation: Learn how to install and use the package.
- Usage examples: Within the package docs we have a few examples of what it looks like to load and use OEPS data.
- GitHub: Use the GitHub repo to report issues you have with the package, or suggest new features or datasets.
Current release: v0.1
Google BigQuery
We have loaded the OEPS data warehouse into Google BigQuery, a data storage platgorm that provides the ability for researchers to run SQL queries (including spatial queries) to retrieve or perform analysis on specific data subsets. Google publishes many different clients through which you can access a BigQuery database, and for R users there is bigrquery. Here's how to get started:
- Introduction to OEPS in Google BigQuery: The oepsData documentation includes a detailed overview that is relevant no matter what client you use.
- Setting up BigQuery in R: The oepsData documentation also has a walkthrough guide illustrating how R users can connect directly to our data in BigQuery.
- Database Table Reference: Full reference document, provides the project id and the names of all tables and columns.