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 "Ohio Oil and Gas Data Sources"

(References)
 
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
__TOC__
 +
=Ohio Data Releases=
 +
 +
 +
==Ohio v1.0 (September 2014)==
 +
This was the first release of Ohio oil and gas data on WellWiki. This release included data reported by the Ohio Department of Natural Resources through August 2014. The data for this release were derived from the Risk Based Data Management System (RBDMS). By this point our server infrastructure consisted of a single virtual machine, with 2 CPUs, 6GB RAM and 1TB drive.
 +
 +
 +
==Ohio v2.0 (July 2015)==
 +
This release added 747 wells, approximately 18,000 inspection and 655 violation records, and 51,470 production records for 2014 and 2015. We also updated various location, spud, and county information and enhanced our database to include Inspection Type for all compliance records. As part of this update we created two new pages: Ohio Oil and Gas Data Sources and Ohio Technical Information. We also implemented code to automate the referencing of source information for all Ohio pages. The team for this project consisted of Joel Gehman, Mason Strong, and Hailey Musselman.
 +
 +
 +
==Ohio v3.0 (July 2019)==
 +
This release expanded WellWiki’s coverage of Ohio oil and gas wells to include data available through April 2019. Data for this update were obtained from the Ohio Risk Based Data Management System and included the following tables:
  
__TOC__
+
  •  Codes: This table defines the codes that are used in other tables. It was used to convert codes to full names for some of the fields in other tables.   
 +
 
 +
  •  Company: Contains operator names, codes, addresses, and phone numbers. Also gives alternate aliases for some operators.
 +
 
 +
  •  County: Lists all of the counties in Ohio.
 +
 
 +
  •  Formatn: Lists all of the oil formations found in Ohio.
 +
 
 +
  •  Perfs: Contains perforation treatment data for Ohio wells.
 +
 
 +
  •  Production: Contains production data for wells in Ohio. Includes quantities of oil, gas, and waste water produced.
 +
 
 +
  •  tblCivilTownships: Lists Municipalities in Ohio.
 +
 
 +
  •  tblInspection: Contains well inspection data, specifically only inspections where the well passed the inspection and was in compliance with appropriate codes.
 +
 
 +
  •  tblInspectorStringCement: Contains more inspection data, specifically inspections of cement that was poured around wells.
 +
 
 +
  •  tblInspFail: Contains inspections data, specifically inspections where the well failed the inspection.
 +
 
 +
  •  tblInspFlDesc: Gives comments for inspections in the tblInspFail and specifies what codes the well was found to be in violation of.
 +
 
 +
  •  tblLocational: Gives latitude and longitude data for wells found in the Wells table.
 +
 
 +
  •  tblPad: Lists the well pads found in Ohio.
 +
 
 +
  •  tblPadWells: This table maps the well pads from the tblPad table to their wells from the Wells table.
 +
 
 +
  •  tblPlugWell: Gives the plug back depth for wells that have been plugged. 
 +
 
 +
  •  tblStimulation: Contains Ohio fracking data.
 +
 
 +
  •  Well: Lists all of the wells in Ohio.
 +
 
 +
  •  WellHistry: Records any changes in a well's status over time such as changes in ownership, wells being plugged,  and wells being re-drilled.
 +
 
 +
 
 +
We 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. We used the TIGER/Line coordinate system to map all the wells with lat/long to their respective county and municipality. Finally, this release incorporated data from our Fracking Chemicals v2.0 update. In total, 2,321 Ohio 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.
 +
 
 +
 
 +
Overall, this release resulted in the generation of {{PAGESINCATEGORY:Ohio_Wells}} new or modified Ohio Well Pages; {{PAGESINCATEGORY:Ohio_Operators}} new or modified Ohio Operator Pages; {{#number_format:{{#expr:{{formatnum:{{PAGESINCATEGORY: Ohio_counties}}|R}}+{{formatnum:{{PAGESINCATEGORY:Ohio_Municipalities}}|R}}}}}} new or modified Ohio County and Municipality Pages; and {{PAGESINCATEGORY:Ohio_Well_Pads}} new or modified Ohio Well Pad Pages.The team for this project consisted of Joel Gehman, Michael Boisvert 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.
  
  
== Source Information ==
+
==Ohio v4.0 (January 2021)==
 +
This was the fourth release of Ohio oil and gas data on Wellwiki. All the data for this upgrade came from the Ohio Department of Natural Resources website <ref name = 'a1'>{{cite web | title = OIL & GAS WELL DATABASE | url = https://ohiodnr.gov/wps/portal/gov/odnr/discover-and-learn/safety-conservation/about-odnr/oil-gas/oil-gas-resources/featured-content-3}}</ref>. This update contains data up to November 2020. The tables used from the database are:
  
All data is obtained from an access database hosted at: http://oilandgas.ohiodnr.gov/industry/rbdms
+
•  Codes
  
This database provides information regarding the Wells in Ohio, as well as their production information. Compliance data is also present.
+
•  Company
  
There seems to be no information in the access database pertaining to Penalty, Permit, Violation, or Waste.
+
•  Format
  
==Production==
+
Perfs
Ohio State law mandates that owner of any well capable of producing oil or natural gas must report oil, gas and brine production data from each well they own, on an annual basis by March 31 for the preceding calendar year. Some domestic well owners are exempt and are not required to file production statements.
 
  
Annual production information may be obtained from the production table within the Risk Based Data Management System (RBDMS). The table is available by year beginning in 1984. Each record contains the following fields: production year, county, township, API well number, permit number, owner name, well name, well number, oil (1 barrel = 42 US gallons), gas (1 MCF = 1,000 cubic feet of gas), brine (1 barrel = 42 US gallons), the number of production days, date completed, and the plugging date (where applicable).<ref>[http://oilandgas.ohiodnr.gov/industry/rbdms], Ohio Department of Natural Resources Retrieved 25 june 2015</ref>
+
•  Production
  
== Technical Information for Importing to MySQL==
+
•  tblInspection
As data is in an access database, it is easiest to export the tables required to an excel file, where it can then be edited and saved as a CSV. From here, it can be imported with ease to MySQL using similar procedures as detailed for Pennsylvania[http://wellwiki.org/wiki/Pennsylvania_Oil_and_Gas_Data_Sources].
 
  
 +
•  tblInspectorStringCement
  
'''Production:'''
+
•  tblInspFail
  
Most recent time of update found by searching "34%" in WELL_API for production table, after which PERIOD_ID was sorted in reverse order.
+
•  tblLocational
WELL_API in the form of 34003249030000 instead of 34-003-24903(-0000) like PA.
 
Stored in the MySQL database in this form as well.
 
Not sure how to get the PRODUCTION_ID - we can use DATE_MOD with [$-409]yyyy-MM;@ formatting in excel to obtain a 2015-5 style of PERIOD_ID like the rest of the database. Unsure if this is genuinely accurate as the year of production and the date mod can differ.
 
  
 +
•  tblStimulation
  
'''Well:'''
+
•  Well
  
WELL_API is in the form 34-XXX-XXXXX, access table in the form 34XXXXXXXXXXXX.
+
•  WellHistry
Using excel with =LEFT(A2,2) & "-" & MID(A2,3,3) & "-" & MID(A2,6,5)) we can convert this.
 
  
  
""TODO:""
 
  
There is information regarding Compliance within our MySQL database, but this information needs to be located.
+
Overall, this upgrade resulted in the generation of 272,155 new or modified Ohio Well Pages; 9,097 new or modified Ohio Operator Pages; 1,743 new or modified Ohio Municipality Pages and 88 new or modified Ohio County Pages. The team for this project consisted of Joel Gehman, Cole Miller, and Georgio Cheruvelil. Financial support and in-kind support for this project was provided by the University of Alberta School of Business.
  
  
 +
==References==
 +
<references/>
 +
__NOEDITSECTION__
  
=References=
+
[[Category:Documentation]]
{{reflist}}
 

Latest revision as of 17:21, 15 January 2021

Ohio Data Releases

Ohio v1.0 (September 2014)

This was the first release of Ohio oil and gas data on WellWiki. This release included data reported by the Ohio Department of Natural Resources through August 2014. The data for this release were derived from the Risk Based Data Management System (RBDMS). By this point our server infrastructure consisted of a single virtual machine, with 2 CPUs, 6GB RAM and 1TB drive.


Ohio v2.0 (July 2015)

This release added 747 wells, approximately 18,000 inspection and 655 violation records, and 51,470 production records for 2014 and 2015. We also updated various location, spud, and county information and enhanced our database to include Inspection Type for all compliance records. As part of this update we created two new pages: Ohio Oil and Gas Data Sources and Ohio Technical Information. We also implemented code to automate the referencing of source information for all Ohio pages. The team for this project consisted of Joel Gehman, Mason Strong, and Hailey Musselman.


Ohio v3.0 (July 2019)

This release expanded WellWiki’s coverage of Ohio oil and gas wells to include data available through April 2019. Data for this update were obtained from the Ohio Risk Based Data Management System and included the following tables:

 •  Codes: This table defines the codes that are used in other tables. It was used to convert codes to full names for some of the fields in other tables.    
 •  Company: Contains operator names, codes, addresses, and phone numbers. Also gives alternate aliases for some operators.
 •  County: Lists all of the counties in Ohio.
 •  Formatn: Lists all of the oil formations found in Ohio.
 •  Perfs: Contains perforation treatment data for Ohio wells.
 •  Production: Contains production data for wells in Ohio. Includes quantities of oil, gas, and waste water produced.
 •  tblCivilTownships: Lists Municipalities in Ohio.
 •  tblInspection: Contains well inspection data, specifically only inspections where the well passed the inspection and was in compliance with appropriate codes.
 •  tblInspectorStringCement: Contains more inspection data, specifically inspections of cement that was poured around wells.
 •  tblInspFail: Contains inspections data, specifically inspections where the well failed the inspection.
 •  tblInspFlDesc: Gives comments for inspections in the tblInspFail and specifies what codes the well was found to be in violation of.
 •  tblLocational: Gives latitude and longitude data for wells found in the Wells table.
 •  tblPad: Lists the well pads found in Ohio.
 •  tblPadWells: This table maps the well pads from the tblPad table to their wells from the Wells table.
 •  tblPlugWell: Gives the plug back depth for wells that have been plugged.  
 •  tblStimulation: Contains Ohio fracking data.
 •  Well: Lists all of the wells in Ohio.
 •  WellHistry: Records any changes in a well's status over time such as changes in ownership, wells being plugged,  and wells being re-drilled.


We 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[1] update. We used the TIGER/Line coordinate system to map all the wells with lat/long to their respective county and municipality. Finally, this release incorporated data from our Fracking Chemicals v2.0 update. In total, 2,321 Ohio 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[2] page.


Overall, this release resulted in the generation of 272,158 new or modified Ohio Well Pages; 12,166 new or modified Ohio Operator Pages; 2,047 new or modified Ohio County and Municipality Pages; and 899 new or modified Ohio Well Pad Pages.The team for this project consisted of Joel Gehman, Michael Boisvert 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.


Ohio v4.0 (January 2021)

This was the fourth release of Ohio oil and gas data on Wellwiki. All the data for this upgrade came from the Ohio Department of Natural Resources website [3]. This update contains data up to November 2020. The tables used from the database are:

• Codes

• Company

• Format

• Perfs

• Production

• tblInspection

• tblInspectorStringCement

• tblInspFail

• tblLocational

• tblStimulation

• Well

• WellHistry


Overall, this upgrade resulted in the generation of 272,155 new or modified Ohio Well Pages; 9,097 new or modified Ohio Operator Pages; 1,743 new or modified Ohio Municipality Pages and 88 new or modified Ohio County Pages. The team for this project consisted of Joel Gehman, Cole Miller, and Georgio Cheruvelil. Financial support and in-kind support for this project was provided by the University of Alberta School of Business.


References