X

Track changes made to this page

If you find this page useful and would like to be notified of changes made to this page, start by inputting your email below.



Privacy policy
Close this window

powered by ChangeDetection

Difference between revisions of "Pennsylvania Oil and Gas Data Sources"

 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[Category:Documentation]]
+
__TOC__
 +
=Pennsylvania Data Releases=
  
==May 2015 Production Update==
 
  
Updating Production data. Extra column for WELL_API had to be added, using Well Permit #. Excel formula ="37-"&B2 was used to produce WELL_API values. Well Permit # renamed to WELL_API_COUNTY_ID. Extra columns WELL_COUNTRY set to "United States" and WELL_STATE_CODE set to "PA".
+
==Pennsylvania v0.1 Alpha (March 2013)==
 +
Originally called the Oil and Gas Wells Database (O&GWDB), this was the very first build of what would become WellWiki. The project was released internally only and contained data on approximately 130,000 wells gathered from the Pennsylvania Department of Environmental Protection. These data included permits, spuds, and compliance reports (from Jan 1900 to Feb 2013) and production and waste reports (from 2000 to mid-2012). The project team consisted of Joel Gehman, Dror Etzion, and Diego Mastroianni.
  
  
Needed to specify that lines were delimited by \n instead of auto to get around PHP "invalid comma count error." There was a typo in one cell for a sheet that had a "\" character, which produced another invalid column count error. Also renamed all columns in CSV to columns in SQL db as follows:
+
==Pennsylvania v1.0 (May 2014)==
 +
WellWiki was publicly launched. The launch coincided with the release of Pennsylvania v1.0, which consisted of data from the Pennsylvania Department of Environmental Protection on approximately 150,000 oil and gas wells. The project team included Joel Gehman and Michael Hall. Our technology environment consisted of a single server with a 45GB drive and 4GB RAM. The initial software stack included Ubuntu 12.04.4 LTS, MySQL 5.5.31, Apache 2.22.2, PHP, PHPMyAdmin, Pure-FTPd, and SSH.  
  
  
WELL_API, WELL_API_COUNTY_ID, PERIOD_ID, PRODUCTION_INDICATOR, WELL_STATUS, FARM_NAME,WELL_ID, SPUD_DATE, GAS_QUANTITY_MCF, GAS_PRODUCTION_DAYS, CONDENSATE_QUANTITY_BBL, CONDENSATE_PRODUCTION_DAYS, OIL_QUANTITY_BBL, OIL_PRODUCTION_DAYS, AVERAGED, OPERATOR_NAME, OPERATOR_ID, WELL_COUNTY, WELL_MUNICIPALITY, LATITUDE_DECIMAL, LONGITUDE_DECIMAL, UNCONVENTIONAL, CONFIGURATION, HOME_USE, REPORTING_PERIOD, COMMENT_REASON, COMMENT_TEXT, WELL_COUNTRY, WELL_STATE_CODE
+
==Pennsylvania v1.1 (July 2014)==
 +
This update expanded our coverage of Pennsylvania to encompass approximately 250,000 oil and gas wells.
  
  
which needs to be entered on the import screen for PHPmyAdmin to upload correctly for column headers.
+
==Pennsylvania v2.0 (November 2014)==
 +
This update expanded WellWiki’s coverage of Pennsylvania oil and gas wells to include data through October 2014. With its release, WellWiki’s total coverage reached approximately 878,000 wells, primarily due to the inclusion of expanded production data. The project team consisted of Joel Gehman and Michael Hall. Data for this update were obtained from the Pennsylvania Department of Environmental Protection and included the following reports: permits, spuds, production, waste, compliance, and well pads.  
  
  
An excel macro has been written and stored on google drive in order to automate this process.
+
==Pennsylvania v3.0 (June 2015)==
 +
This update expanded WellWiki’s coverage of Pennsylvania oil and gas wells to include data through May 2015. With its release, WellWiki’s total coverage reached 1.5 million wells. Data for this update were obtained from the Pennsylvania Department of Environmental Protection and included the following reports: permits, spuds, and compliance. Production data spanned from 1980 (the earliest period available) to March 31, 2015 (the latest period available). Waste data spanned from 1995 (the earliest period available) to March 31, 2015 (the latest period available). However, waste records for 1980-1994, inclusive, were not available for download at the time of this update. As part of this upgrade, we created the Pennsylvania Oil and Gas Data Sources wiki page and began footnoting the sources of all data displayed on WellWiki. The project team consisted of Joel Gehman, Mason Strong and Hailey Musselman.
  
  
In addition to removing the \ character from CSVs, they must also be processed to remove the quotation character " to allow for proper importation. Older yearly CSV files (non-monthly) were split using a CSV split utility in order to meet MySQL's 2048KiB filesize limit
+
==Pennsylvania v4.0 (February 2018)==
 +
This update expanded WellWiki’s coverage of Pennsylvania oil and gas wells. The project team consisted of Joel Gehman and Keith Mills.
  
  
Duplicate entries were discovered in the production table. Entries were removed by producing a new temporary table with the same structure but a primary key consisting of the WELL_ID and production date. Data was copied over with a INSERT IGNORE statement, old data in production was dropped, and unique data copied back to the production table.
+
==Pennsylvania v5.0 (June 2019)==
 +
This update expanded WellWiki’s coverage of Pennsylvania oil and gas wells to include data available through April 2019. Data for this update were obtained from the Pennsylvania Department of Environmental Protection and included the following reports:
  
  
==Waste==
+
  •  Permits<ref>{{cite web
Insert WELL_API in leftmost column
+
| title = Permits Issued Detail Report
Insert WELL_STATE_CODE after column P
+
| url = http://www.depreportingservices.state.pa.us/ReportServer/Pages/ReportViewer.aspx?/Oil_Gas/Permits_Issued_Detail
Insert COUNTRY after WELL_STATE_CODE
+
| accessdate = 2019-05-21 }}</ref>    - 223,184 records from 1800-01-01 to 2019-05-20
No DB comments
 
No SPUD_DATE_TEXT
 
  
CSVs were uploaded to /var/lib/mysql/wells_db/ with owner and group changed to mysql.
+
  •  Spuds<ref>{{cite web
They were then added to the waste table via:
+
| title = Spud Data Report
LOAD DATA INFILE 'WasteExport2014-2.csv'
+
| url = http://www.depreportingservices.state.pa.us/ReportServer/Pages/ReportViewer.aspx?/Oil_Gas/Spud_External_Data
 +
| accessdate = 2019-05-16 }}</ref>      - 213,664 records from 1800-01-01 to 2019-04-30
  
INTO TABLE waste
+
  •  Production<ref>{{cite web
 +
| title =Oil and Gas Production Reports
 +
| url = http://www.depreportingservices.state.pa.us/ReportServer/Pages/ReportViewer.aspx?%2fOil_Gas%2fOil_Gas_Well_Production
 +
| accessdate = 2019-05-21 }}</ref>  - 2,305,539 records relating to 148,847 unique wells from 1980-01-01 to 2019-03-31.
  
FIELDS TERMINATED BY ','
+
  •  Waste<ref>{{cite web
 +
| title =Oil and Gas Waste Reports
 +
| url = http://www.depreportingservices.state.pa.us/ReportServer/Pages/ReportViewer.aspx?%2fOil_Gas%2fOil_Gas_Well_Waste
 +
| accessdate = 2019-05-21 }}</ref>      - 1,270,740 records relating to 89,734 unique wells from 1980-01-01 to 2019-03-31.
  
ENCLOSED BY '"'
+
  •  Compliance<ref>{{cite web
 +
| title =Oil and Gas Compliance Report
 +
| url = http://www.depreportingservices.state.pa.us/ReportServer/Pages/ReportViewer.aspx?/Oil_Gas/OG_Compliance
 +
| accessdate = 2019-05-21 }}</ref>  - 452,647 records relating to 122,490 unique wells from 1950-01-01 to 2019-05-20.
  
LINES TERMINATED BY '\n'
+
  •  Well Pads<ref>{{cite web
 +
| title = Oil and Gas Well Pad Report
 +
| url = http://www.depreportingservices.state.pa.us/ReportServer/Pages/ReportViewer.aspx?/Oil_Gas/Well_Pads
 +
| accessdate = 2019-05-21 }}</ref>  - 13,095 records from 1800-01-01 to 2019-05-20.
  
IGNORE 1 ROWS
 
  
(WELL_API, WELL_API_COUNTY_ID, PERIOD_ID, WELL_STATUS, FARM_NAME, WELL_ID, @SPUD_DATE_TMP, WASTE_TYPE, WASTE_QUANTITY, UNITS, DISPOSAL_METHOD, AVERAGED, OPERATOR_NAME, OPERATOR_OGO, WELL_COUNTY, WELL_MUNICIPALITY, WELL_STATE_CODE, WELL_COUNTRY, LATITUDE_DECIMAL, LONGITUDE_DECIMAL, UNCONVENTIONAL, CONFIGURATION, HOME_USE, WASTE_FACILITY_PERMIT_ID, WASTE_FACILITY_NAME, FACILITY_ADDRESS_1, FACILITY_ADDRESS_2, FACILITY_CITY, FACILITY_STATE, FACILITY_ZIP_CODE, FACILITY_PHONE, FACILITY_LATITUDE, FACILITY_LONGITUDE, REPORTING_PERIOD, COMMENT_REASON, COMMENT_TEXT)
+
Overall, this upgrade resulted in the generation of {{PAGESINCATEGORY:Pennsylvania_Wells}} new or modified Pennsylvania Well Pages; {{PAGESINCATEGORY:Pennsylvania_Operators}} new or modified Pennsylvania Operator Pages; 1,115 new or modified Pennsylvania County and Municipality Pages; and {{PAGESINCATEGORY:Pennsylvania_Well_Pads}} new or modified Pennsylvania Well Pad Pages. The team for this project consisted of Joel Gehman, Cole Miller and Ankesh Kumar.
SET SPUD_DATE = STR_TO_DATE(@SPUD_DATE_TMP, '%m/%d/%Y');
 
  
  
CSVs for Compliance, Permits, and SPUD dates were obtained from http://www.portal.state.pa.us/portal/server.pt/community/oil_and_gas_reports/20297 using their respectively linked utilities. Maximum date range from 01/01/1800 to 05/26/2015 was used to obtain data. Default settings for all categories were appropriate except for "inspections with violations only" for compliance, which had to be set to "no" in order to properly obtain all compliance records.
+
==Pennsylvania v6.0 (July 2019)==
 +
In terms of its explicit data contents, this update utilized the same data underlying our v5.0 release. However, whereas all prior Pennsylvania releases utilized our original database design, we built Pennsylvania v6.0 on an expanded version of the database design that accompanied our release of Alberta v2.0<ref>{{cite web | title = Alberta v2.0 Oil and Gas Data Sources | url = http://wellwiki-new-uat.bus.ualberta.ca/wiki/Alberta_Oil_and_Gas_Data_Sources#Alberta_v2.0_.28December_2018.29}}</ref>. Incorporating the Pennsylvania data into this database schema necessitated several enhancements. Notably, the Pennsylvania Department of Environmental Protection provides data on “Well Pads,” basically sites where more than one well may be permitted from the same location. To accommodate these data, we incorporated a new Well Pads table into our database schema. Additionally, the Pennsylvania Department of Environmental Protection reports extensive data regarding inspections, violations, and fines. Comparable data are not available in Alberta, the jurisdiction that served as the basis for our original development of the new database schema. Accordingly, we added new tables related to Inspections, Violations, and Penalties.
  
  
==SPUD:==
+
We also made several enhancements to our display and reporting of Pennsylvania oil and gas data on WellWiki. First, Pennsylvania has changed its production and waste reporting requirements for unconventional several times, from annual to semiannual to monthly. Additionally, during this transition there was an odd reporting period that spanned from July 2009 to June 2010. Although it is a crude approximation, for reporting purposes on WellWiki’s production table, we divided the values for this period in half, assigning them equally to two new periods we created: 2009-2 and 2010-1. We then aggregated all available data into annual periods, plus reported any data available for years not yet completed. For instance, if well reported production from 2000-0 to 2019-03, meaning for the full calendar year 2000, through to March 2019, we would report annual values for the 2000 to 2018 period, plus monthly values (if any) for the January to March 2019 period. Our Production table now also includes information on the well operator at the time the production was reported. This makes it apparent whether a well has been bought and sold during its operating history.
  
Only records past 2014/10/13 were used to avoid data duplication.
 
  
 +
We also expanded the data displayed on our Operator, and County and Municipality Pages, notably to include “operator” on County and Municipality Pages and "County" and “Municipality” on Operator Pages. This mirrors an enhancement we made as part of our Alberta v3.0<ref>{{cite web | title = Alberta v3.0 Oil and Gas Data Sources | url = http://wellwiki-new-uat.bus.ualberta.ca/wiki/Alberta_Oil_and_Gas_Data_Sources#Alberta_v3.0_.28May_2019.29}}</ref> update. Finally, this release incorporated data from our Fracking Chemicals v2.0 update. In total, 8,307 Pennsylvania wells reported data through FracFocus; we include those data for each well. Data on Fracking Activities are obtained primarily from FracFocus. For complete details see the Fracking Activities Data Sources<ref>{{cite web | title = Fracking Activities Data Sources | url = http://wellwiki-new-uat.bus.ualberta.ca/wiki/Fracking_Activities_Data_Sources}}</ref> page.
  
Need to prepend "37-" to all entries in WELL_API
 
  
WELL_API can be cloned without "37-" for WELL_API_COUNTY_ID
+
Overall, this upgrade resulted in the generation of {{PAGESINCATEGORY:Pennsylvania_Wells}} new or modified Pennsylvania Well Pages; {{PAGESINCATEGORY:Pennsylvania_Operators}} new or modified Pennsylvania Operator Pages; 1,115 new or modified Pennsylvania County and Municipality Pages; and {{PAGESINCATEGORY:Pennsylvania_Well_Pads}} new or modified Pennsylvania Well Pad Pages. The team for this project consisted of Joel Gehman, Cole Miller and Ankesh Kumar. Funding for the project was provided in part by financial support from the Social Sciences and Humanities Research Council of Canada and the University of Alberta, as well as in-kind support University of Alberta School of Business.
  
Delete REGION column
 
  
Change WELL_CODE_DESC to WELL_TYPE
+
==References==
 +
<references/>
 +
__NOEDITSECTION__
  
Delete WELL_STATUS
+
[[Category:Documentation]]
 
 
Add State Code and Country Column before FARM_NAME
 
 
 
No Farm Well NO
 
 
 
 
 
LOAD DATA INFILE 'cleanedSPUD.csv'
 
 
 
INTO TABLE spud FIELDS TERMINATED BY ','
 
 
 
ENCLOSED BY '"'
 
 
 
LINES TERMINATED BY '\n'
 
 
 
IGNORE 1 ROWS
 
 
 
(@SPUD_DATE_TMP, WELL_API, WELL_API_COUNTY_ID, OPERATOR_OGO, OPERATOR_NAME, WELL_COUNTY, WELL_MUNICIPALITY, WELL_STATE_CODE, WELL_COUNTRY, FARM_NAME, WELL_TYPE, LATITUDE_DECIMAL, LONGITUDE_DECIMAL, CONFIGURATION, UNCONVENTIONAL)
 
SET SPUD_DATE = STR_TO_DATE(@SPUD_DATE_TMP, '%m/%d/%Y');
 
 
 
 
 
==PERMITS:==
 
Grabbed all permits from 2014-10-09 to 2015-05-27
 
 
 
delete REGION
 
 
 
Insert column before WELL_API, prepend with "37-" with WELL_API entries. Old
 
 
 
Insert state code and country columns after municipality
 
 
 
Delete LATITUDE_DEGREES, LONGITUDE_DEGREES
 
 
 
No PERMIT_ISSUED_DATE, DB_COMMENTS, SPUD_DATE_TEXT, permit_application_date, permit_issue_date, permit_status, proposed_total_depth
 
 
 
 
 
LOAD DATA INFILE 'perms.csv'
 
 
 
INTO TABLE permit FIELDS TERMINATED BY ','
 
 
 
ENCLOSED BY '"'
 
 
 
LINES TERMINATED BY '\n'
 
 
 
IGNORE 1 ROWS
 
 
 
(WELL_COUNTY, WELL_MUNICIPALITY, WELL_STATE_CODE, WELL_COUNTRY, PERMIT_ISSUED_DATE, OPERATOR_NAME, APPLICATION_TYPE, AUTHORIZATION_DESCRIPTION, WELL_API, WELL_API_COUNTY_ID, UNCONVENTIONAL, CONFIGURATION, WELL_TYPE, FARM_NAME, @SPUD_DATE_TMP, LATITUDE_DECIMAL, LONGITUDE_DECIMAL, OPERATOR_OGO, OPERATOR_ADDRESS, OPERATOR_CITY, OPERATOR_STATE, OPERATOR_ZIP, AUTHORIZATION_ID, CLIENT_ID, PRIMARY_FACILITY_ID) SET SPUD_DATE = STR_TO_DATE(@SPUD_DATE_TMP, '%m/%d/%Y');
 
 
 
 
 
==Compliance:==
 
 
 
There were issues inserting for compliance due to foreign key constraints being invalidated. This could be overridden using SET foreign_key_checks = 0; on the table prior to insertion, and then re-enabling it with SET foreign_key_checks = 1; after insertion, but this could potentially be unwise. The problem could have also been circumvented via the "IGNORE" clause after LOAD DATA INFILE 'filename' however apparently there is a bug in MySQL for innoDB tables and IGNORE in this particular instance. For the time being, data was not uploaded.
 
 
 
Otherwise, the process is the same as detailed above, with the following specifics:
 
 
 
Compliance data provided by PADEP also provides the required information for penalty and fines tables. These tables make use of automatically generated primary/foreign keys rather than WELL_API as their identifier.
 
 
 
Delete OPERATOR, FARM_NAME, UNCONVENTIONAL, SITE_ID, SITE_NAME, FACILITY, REGION, COUNTY, MUNICIPALITY, everything regarding violation, RESOLUTION_REASON_CODE_DESCRIPTION, all rows relating to ENFORCEMENT, PENALTIES, TOTAL_AMOUNT_COLLECTED
 
INSPECTION_ID is INSP_ID not INSP_ID_PK (which auto-increments)
 
API_PERMIT needs to be pre-pended with "37-"
 
 
 
Use dates from 2014-9-10 to 2015-05-27
 
 
 
 
 
LOAD DATA INFILE 'comp.csv' IGNORE
 
 
 
INTO TABLE compliance FIELDS TERMINATED BY ','
 
 
 
ENCLOSED BY '"'
 
 
 
LINES TERMINATED BY '\n'
 
IGNORE 1 ROWS
 
(INSP_ID, INSPECTION_DATE, INSPECTION_TYPE, WELL_ID_FK, INSP_CATEGORY, INSPECTION_RESULT_DESC, INSP_COMMENT)
 
SET INSPECTION_DATE = STR_TO_DATE(@INSPECTION_DATE_TMP, '%m/%d/%Y')
 

Latest revision as of 14:51, 29 August 2019

Pennsylvania Data Releases

Pennsylvania v0.1 Alpha (March 2013)

Originally called the Oil and Gas Wells Database (O&GWDB), this was the very first build of what would become WellWiki. The project was released internally only and contained data on approximately 130,000 wells gathered from the Pennsylvania Department of Environmental Protection. These data included permits, spuds, and compliance reports (from Jan 1900 to Feb 2013) and production and waste reports (from 2000 to mid-2012). The project team consisted of Joel Gehman, Dror Etzion, and Diego Mastroianni.


Pennsylvania v1.0 (May 2014)

WellWiki was publicly launched. The launch coincided with the release of Pennsylvania v1.0, which consisted of data from the Pennsylvania Department of Environmental Protection on approximately 150,000 oil and gas wells. The project team included Joel Gehman and Michael Hall. Our technology environment consisted of a single server with a 45GB drive and 4GB RAM. The initial software stack included Ubuntu 12.04.4 LTS, MySQL 5.5.31, Apache 2.22.2, PHP, PHPMyAdmin, Pure-FTPd, and SSH.


Pennsylvania v1.1 (July 2014)

This update expanded our coverage of Pennsylvania to encompass approximately 250,000 oil and gas wells.


Pennsylvania v2.0 (November 2014)

This update expanded WellWiki’s coverage of Pennsylvania oil and gas wells to include data through October 2014. With its release, WellWiki’s total coverage reached approximately 878,000 wells, primarily due to the inclusion of expanded production data. The project team consisted of Joel Gehman and Michael Hall. Data for this update were obtained from the Pennsylvania Department of Environmental Protection and included the following reports: permits, spuds, production, waste, compliance, and well pads.


Pennsylvania v3.0 (June 2015)

This update expanded WellWiki’s coverage of Pennsylvania oil and gas wells to include data through May 2015. With its release, WellWiki’s total coverage reached 1.5 million wells. Data for this update were obtained from the Pennsylvania Department of Environmental Protection and included the following reports: permits, spuds, and compliance. Production data spanned from 1980 (the earliest period available) to March 31, 2015 (the latest period available). Waste data spanned from 1995 (the earliest period available) to March 31, 2015 (the latest period available). However, waste records for 1980-1994, inclusive, were not available for download at the time of this update. As part of this upgrade, we created the Pennsylvania Oil and Gas Data Sources wiki page and began footnoting the sources of all data displayed on WellWiki. The project team consisted of Joel Gehman, Mason Strong and Hailey Musselman.


Pennsylvania v4.0 (February 2018)

This update expanded WellWiki’s coverage of Pennsylvania oil and gas wells. The project team consisted of Joel Gehman and Keith Mills.


Pennsylvania v5.0 (June 2019)

This update expanded WellWiki’s coverage of Pennsylvania oil and gas wells to include data available through April 2019. Data for this update were obtained from the Pennsylvania Department of Environmental Protection and included the following reports:


 •  Permits[1]     - 223,184 records from 1800-01-01 to 2019-05-20
 •  Spuds[2]       - 213,664 records from 1800-01-01 to 2019-04-30
 •  Production[3]  - 2,305,539 records relating to 148,847 unique wells from 1980-01-01 to 2019-03-31.
 •  Waste[4]       - 1,270,740 records relating to 89,734 unique wells from 1980-01-01 to 2019-03-31.
 •  Compliance[5]  - 452,647 records relating to 122,490 unique wells from 1950-01-01 to 2019-05-20.
 •  Well Pads[6]   - 13,095 records from 1800-01-01 to 2019-05-20.


Overall, this upgrade resulted in the generation of 270,818 new or modified Pennsylvania Well Pages; 9,002 new or modified Pennsylvania Operator Pages; 1,115 new or modified Pennsylvania County and Municipality Pages; and 3,798 new or modified Pennsylvania Well Pad Pages. The team for this project consisted of Joel Gehman, Cole Miller and Ankesh Kumar.


Pennsylvania v6.0 (July 2019)

In terms of its explicit data contents, this update utilized the same data underlying our v5.0 release. However, whereas all prior Pennsylvania releases utilized our original database design, we built Pennsylvania v6.0 on an expanded version of the database design that accompanied our release of Alberta v2.0[7]. Incorporating the Pennsylvania data into this database schema necessitated several enhancements. Notably, the Pennsylvania Department of Environmental Protection provides data on “Well Pads,” basically sites where more than one well may be permitted from the same location. To accommodate these data, we incorporated a new Well Pads table into our database schema. Additionally, the Pennsylvania Department of Environmental Protection reports extensive data regarding inspections, violations, and fines. Comparable data are not available in Alberta, the jurisdiction that served as the basis for our original development of the new database schema. Accordingly, we added new tables related to Inspections, Violations, and Penalties.


We also made several enhancements to our display and reporting of Pennsylvania oil and gas data on WellWiki. First, Pennsylvania has changed its production and waste reporting requirements for unconventional several times, from annual to semiannual to monthly. Additionally, during this transition there was an odd reporting period that spanned from July 2009 to June 2010. Although it is a crude approximation, for reporting purposes on WellWiki’s production table, we divided the values for this period in half, assigning them equally to two new periods we created: 2009-2 and 2010-1. We then aggregated all available data into annual periods, plus reported any data available for years not yet completed. For instance, if well reported production from 2000-0 to 2019-03, meaning for the full calendar year 2000, through to March 2019, we would report annual values for the 2000 to 2018 period, plus monthly values (if any) for the January to March 2019 period. Our Production table now also includes information on the well operator at the time the production was reported. This makes it apparent whether a well has been bought and sold during its operating history.


We also expanded the data displayed on our Operator, and County and Municipality Pages, notably to include “operator” on County and Municipality Pages and "County" and “Municipality” on Operator Pages. This mirrors an enhancement we made as part of our Alberta v3.0[8] update. Finally, this release incorporated data from our Fracking Chemicals v2.0 update. In total, 8,307 Pennsylvania wells reported data through FracFocus; we include those data for each well. Data on Fracking Activities are obtained primarily from FracFocus. For complete details see the Fracking Activities Data Sources[9] page.


Overall, this upgrade resulted in the generation of 270,818 new or modified Pennsylvania Well Pages; 9,002 new or modified Pennsylvania Operator Pages; 1,115 new or modified Pennsylvania County and Municipality Pages; and 3,798 new or modified Pennsylvania Well Pad Pages. The team for this project consisted of Joel Gehman, Cole Miller and Ankesh Kumar. Funding for the project was provided in part by financial support from the Social Sciences and Humanities Research Council of Canada and the University of Alberta, as well as in-kind support University of Alberta School of Business.


References