I know that it’s been a long, long time since I’ve posted to this site. I’ve been involved with a tastily difficult separation of a subsidiary from its parent, both data- and software-wise, with a very tight deadline that was just met. Now I can get back to updating this site with new content and data.
To that end, I’ll be posting some Power BI files that’ll help others massage and visualize the fracking data that would otherwise be difficult to massage in a convenient manner. Power BI Desktop, which is free, can access a variety of databases, file-types (e.g. CSV and JSON), and web APIs to obtain its data. It’ll take me a while, but not as long as the gap that occurred during the aforementioned transition.
Apologies to all concerned as I’ve undertaken a new “day job” that’s taking all of my time and energy, enough so that I didn’t even notice that FracFocus.org’s download page now states that the Excel-friendly CSV download is “under maintenance.”
I’ll have some Excel and SQLite-friendly datasets out for y’all’s consumption shortly. I figure that might help until FracFocus.org gets its act together in the meantime.
A few months ago, I noted that earthquakes for Oklahoma after 2017-03-01 were not showing up in the NCEDC download. Vexed by this, I immediately went searching for an alternative source of earthquake information. Finally, I found the ANSS ComCat catalog, but could only access the full download of earthquakes via a ReSTful API that limited rowsets to 20,000 rows per request. Knowing those limitations, I authored a Python 3 program that would download earthquakes one month at a time, starting from 1900-01-01.
The preceding download has been accomplished and the dataset has been downloaded from 1900-01-01 to the present. I can confirm that Oklahoma’s information now appears within the dataset from 1974 to the present, hence I’ve pushed the earthquake dataset to the AWS S3 quake-info bucket. When I’ve done so, I’ll post links to the actual Python projects at GitHub that download (PyQuakeReSTer) and reverse-geocode (PyGeoCoderRev) the data prior to its import into a SQLite3 database for subsequent analysis.
FracFocus.org’s CSV data has been imported, transformed, and augmented with chemical toxicities by the author of this blog resulting in the file available at the link below:
FracFocus.org’s CSV data has been imported, transformed, and augmented with chemical toxicities by the author of this blog resulting in the file available at the link below:
FracFocus.org’s CSV data has been imported, transformed, and augmented with chemical toxicities by the author of this blog resulting in the file available at the link below:
FracFocus.org’s CSV data has been imported, transformed, and augmented with chemical toxicities by the author of this blog resulting in the file available at the link below:
I just noticed that Oklahoma quakes after 2017-02-28 are no longer present in the ANSS Earthquake Catalog. I’ll have to find an alternative source of earthquake data, likely ComCat, from which to pull.
The new FracFocusCSV files, found within FracFocus.org’s FracFocusCSV.zip archive, lend themselves to blending with chemical toxicities using the CASNumber column of each row. I’ve modified the PyZip2Src2Tgt project, on the “toxicities” branch, to blend the appropriate chemical toxicity based upon the CASNumber of the row in question. The data blending with chemical toxicities has not yet been checked for validity, so if you use the program, you’ll need to verify its results.
The new FracFocusCSV files, found within FracFocus.org’s FracFocusCSV.zip archive, lend themselves to blending with chemical toxicities using the CASNumber column of each row with relative ease. In the near future, I’ll be releasing the combined FracFocusCSV.tsv file with chemical toxicities blended within. As I already possess the chemical toxicity data, it’ll come down to modifying the PyZip2Src2Tgt program to accommodate blending the FracFocusCSV chemical declaration data with the chemical toxicity data based upon the “CASNumber” key column.
Fracking Data 