search

GeoDaCenter / opioid-policy-scan

The Opioid Environment Policy Scan provides access to data at multiple spatial scales to help characterize the multi-dimensional risk environment impacting opioid use in justice populations across the United States.
13 stars 14 forks source link

Update access to opioid treatment program data tables (and fix a typo in the Health tables) #53

Closed bucketteOfIvy closed 1 year ago

bucketteOfIvy commented 1 year ago

(Quick note: this PR should only be accepted after #52 is resolved; leaving this as a draft until then!)

The current Access07 files (access to opioid treatment programs data tables) were seemingly under construction when uploaded, and only consist of shapefile information and distance to nearest provider (screenshot of a few rows from them below as Github dislikes showing large CSVs). The actual drive time metrics themselves do not seem to have been calculated, although the Python script and geocoded OPT dataset both exist.

As the Python script and geocoded locations files existed anyway, I went ahead and re-ran those files (with a little troubleshooting) to generate the missing data. The data already present did not feature their generating code, so I used the other access_[resource].R files as a template to recalculate the distance from tract/zcta centroid to nearest OTP, and then merged those distances together with the drive times.

I did not aggregate up to the County/State level from tract level, but can do so if needed.

bucketteOfIvy commented 1 year ago

Quick additional comment on this: commit 51b68ab9ad059261a17858d0622421df298047e7 featured a typo in the file name. Commit 13ee71f87c974b1f837474ec0b0dd94ccda9c221 fixes that typo, and featured in this PR.

mradamcox commented 1 year ago

Changed the base branch to an intermediate branch made from main, in order to resolve merge conflicts.