oepsData Package Documentation

Chapter 1 Introduction

The Opioid Environment Policy Scan (OEPS) is an open-source data warehouse created by the Healthy Regions & Policies Lab to support researchers in studying and modeling the opioid risk environment. This website is intended as a starting place for researchers interested in using the OEPS data, especially using R.

1.1 In this documentation

• Getting started
  • How to install the package
• Usage
  • Explanation of available functions
• Examples
  • Some quick examples of how oepsData can be used
• Getting OEPS Data from BigQuery
  • How to access OEPS data in Google BigQuery
  • While the examples demonstrate usage of the R package bigrquery, this section will be helpful regardless of which client libary you use to access BigQuery.

1.2 Links

• healthyregions/oepsData
  • Repository for this R package, please record bugs or feature requests in the repo issues
• OEPS Explorer
  • The main project website for OEPS
• healthyregions/oeps
  • The main repository for the OEPS Explorer frontend app and backend ETL app

1.3 Data Sources

All OEPS data is pulled from GeoDaCenter/opioid-policy-scan/v2.0.

Geospatial data comes from our own derivatives of US Census Cartographic Boundary files (500k scale):

• State: https://herop-geodata.s3.us-east-2.amazonaws.com/oeps/state-2010-500k-shp.zip
• County: https://herop-geodata.s3.us-east-2.amazonaws.com/oeps/county-2010-500k-shp.zip
• Tract: https://herop-geodata.s3.us-east-2.amazonaws.com/oeps/tract-2010-500k-shp.zip
• ZCTA: https://herop-geodata.s3.us-east-2.amazonaws.com/oeps/zcta-2018-500k-shp.zip

Note: Because we use 2010 Census boundaries for state, county, and tracts data, there are a few tracts that get left out when the join is made. A more detailed explanation of this can be found in ticket #20, big thank you to @csarapas for finding this bug. We hope to address this in a future release.

1.4 Releases

v0.1.0 December 2024 - Initial release.