Skip to content

Latest commit

 

History

History
92 lines (72 loc) · 4.49 KB

README.md

File metadata and controls

92 lines (72 loc) · 4.49 KB

NJcomCOVIDData

Functionality

This code scrapes the data from NJ.com on a daily basis (12 PM EST --> Pushed to 2 PM EST, 4/11/2020 published at 12:30 PM EST). The data is parsed to extract the City, County, Cases of COVID-19, as well as any reported deaths and recoveries. In my opinion the data set is most likely not as robust and accurate as would be ideal. For example, counties have stopped reporting city level data since this project was created, while other counties have never provided a break down.

Data

The extracted data is then formatted and joined with a ZIP list using City and County to handle cities that share a name (i.e.,Franklin is a town in Sussex, Gloucester, Warren, Hunterdon and Somerset). The data is also aggregated by ZIP to deal with cities that share ZIP Codes. For example, 08053 zones for Marlton (recommended) and Evesham (recognized). It also zones for

  • EVESBORO NJ
  • EVESHAM TWP NJ
  • KRESSON NJ
  • MARLTON LAKES NJ
  • NORTH MARLTON NJ
  • PINE GROVE NJ

To explore this further take a look at the USPS, ZIP Code lookup tool.

For cities that have more than one ZIP like Newark, Camden, Edison, etc. it appears the default behavior is to join the cases, deaths, and recoveries data to each of the ZIPs. This is a gotcha for aggregation. The ZIP version of the output drops duplicate (City, County) tuples and keeps the first. The values are then safely summed to provide a total per ZIP. Additionally the complete CSVs use the number of ZIPs per (City, County) tuple and the provide the Adjusted Cases by dividing Cases by Shared ZIPs.

Output

The data is then exported as three variants to an AWS S3 Bucket and they are sorted by Folder to keep each type together and sorted by date. The variants are:

  1. MM-DD-YYYY-complete.csv has County, City, Cases, Deaths, Recoveries, Zip Code, Shared ZIPs, Adjusted Cases. These are in the Complete folder.
  2. MM-DD-YYYY-cases.csv has Zip Code, City, Cases. These are in the Cases folder.
  3. MM-DD-YYYY-zips.csv has Zip Code, Cases aggregate. These are in the ZIPs folder.
  4. MM-DD-YYYY-missing-ZIPs.csv has the empty Zip Code column, City, County. This is only written if any ZIPs are missing from the master NJzips.csv file. These are in the MissingZIPs folder.

Additionally, the code in the .py creates copies of the above variants starting with current. This allows bookmarking to the current file or using the data for a visualization analysis, or other use. These are together in the Active folder.

Using Google Sheets and the import data function (=IMPORTDATA("https://athenedyne-covid-19.s3.amazonaws.com/Active/current-complete.csv")), one can connect to Tableau to create an interactive Viz that stays up to date.

Automation

The Lambda script is set up on AWS Lambda to run at 2 PM EST daily, updating the S3 Bucket. It was originally scheduled for Noon but the article is not necessarily ready in time.

Additional Files

The ZIPs were collected into NJzips.csv which is somewhat complete, as it may be missing ZIPs for towns that share ZIPs. It does contain ZIPs for towns on the page as of 04/16/2020.

The index.html file is from an answer on the AWS forum by J. Patel on 5/3/2011. The pages uses JS to generate HTML text to list all of the files in the S3 bucket. I modified it to skip index.html.

Additional Notes

This repo can be used locally (.ipynb recommended) or as an AWS Lambda (when zipped with dependencies). When used as a Lambda it's helpful to know that AWS is running a Linux variant so the pandas and numpy libraries will need to be for a Linux system. I'm running MacOS X so I needed to source my libraries from PyPi:

This is laid out really well in AWS Lambda with Pandas and NumPy by Ruslan Korniichuck.