WELL LOGS · UNITED STATES · ONE ROW PER LOG
Well logs within 2 mi of API 42-417-01547
Well logs loaded into Petrora from the regulators' log indexes, newest received first: what each measures, whether it is a digital LAS file or an image, the interval filed for it, and the formations it spans by the well's own tops. Loaded so far for Texas; more states and data sources will follow. Petrora lists these logs; each well's page links to the regulator for the files.
Distances are to the nearest location on file for each well (a horizontal has several along its path), in miles. Locations are surface and path points as mapped, not bottom-hole surveys.
19 LOG FILES ON 17 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1
| Well | Distancemi | Logas described | Intervalft, as filed | Datereceived |
|---|---|---|---|---|
| Diller Virginia #40642-417-38590Shackelford, TX · Crow Ken | 0.48 | NEUTRON POROSITYTIFF | 100 to 604 | Aug 2, 2011run May 18, 2006 |
| Diller Virginia #40642-417-38590Shackelford, TX · Crow Ken | 0.48 | RESISTIVITYTIFF | 100 to 604 | Aug 2, 2011run May 18, 2006 |
| Diller Virginia #100742-417-38741Shackelford, TX · Crow Ken | 0.51 | RESISTIVITYTIFF | 100 to 670 | May 28, 2009run Oct 17, 2007 |
| Diller Virginia #2T42-417-39451Shackelford, TX · Crow Ken | 0.80 | RESISTIVITYTIFF | 30 to 557 | Jan 19, 2015run Dec 27, 2013 |
| Diller Virginia #50642-417-38592Shackelford, TX · Crow Ken | 0.80 | RESISTIVITYTIFF | 100 to 613 | Jul 23, 2008run May 12, 2006 |
| Diller Virginia #10542-417-38550Shackelford, TX · Crow Ken | 1.13 | RESISTIVITYTIFF | 50 to 650 | Dec 6, 2017run Nov 14, 2005 |
| Diller Virginia #70742-417-38719Shackelford, TX · Crow Ken | 1.14 | RESISTIVITYTIFF | 100 to 1,000 | Oct 9, 2008run Aug 11, 2007 |
| Diller Virginia #30642-417-38591Shackelford, TX · Crow Ken | 1.15 | RESISTIVITYTIFF | 100 to 650 | Jun 13, 2011run May 12, 2006 |
| Diller Virginia #90742-417-38742Shackelford, TX · Crow Ken | 1.20 | RESISTIVITYTIFF | 100 to 943 | Oct 3, 2008run Sep 8, 2007 |
| Diller Virginia #100842-417-38859Shackelford, TX · Crow Ken | 1.23 | RESISTIVITYTIFF | 40 to 634 | Jan 23, 2009run Aug 14, 2008 |
| Diller Virginia #110842-417-38860Shackelford, TX · Crow Ken | 1.23 | RESISTIVITYTIFF | 50 to 605 | Jan 16, 2009run Aug 27, 2008 |
| Diller Virginia #80742-417-38729Shackelford, TX · Crow Ken | 1.24 | RESISTIVITYTIFF | 100 to 788 | Mar 15, 2010run Aug 27, 2007 |
| Schkade #4__42-417-01633Shackelford, TX · Roark & Hooker | 1.65 | RESISTIVITYTIFF | 130 to 2,557 | May 30, 2012run Jul 28, 1963 |
| Schkade Farm #542-417-39440Shackelford, TX · Mc Glover LLC | 1.66 | RESISTIVITYTIFF | 0 to 615 | Apr 21, 2014run Oct 16, 2013 |
| Schkade Farm #142-417-39116Shackelford, TX · Glover Michael C. | 1.69 | NEUTRON/DENSITY POROSITYTIFF | 20 to 532 | Dec 22, 2010run Sep 29, 2010 |
| Schkade Farm #142-417-39116Shackelford, TX · Glover Michael C. | 1.69 | RESISTIVITYTIFF | 20 to 536 | Dec 22, 2010run Sep 29, 2010 |
| Schkade Farm #342-417-39277Shackelford, TX · Mc Glover LLC | 1.72 | RESISTIVITYTIFF | 50 to 540 | Mar 11, 2013run Jun 20, 2012 |
| Schkade Farm #242-417-39179Shackelford, TX · Mc Glover LLC | 1.72 | RESISTIVITYTIFF | 50 to 541 | Jan 5, 2012run Sep 7, 2011 |
| Beaty Patsy #342-417-38760Shackelford, TX · Dino Operating LLC | 1.84 | RESISTIVITYTIFF | 50 to 800 | Nov 4, 2008run Jan 16, 2008 |
About this data
Well logs loaded into Petrora from the regulators' log indexes, so far for Texas, with more states and data sources to follow; not necessarily every log that exists. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it. A formation is spanned where the log's filed interval overlaps it in the well's own formation tops; both are measured depths as filed, so a horizontal's lateral is counted in the formation it ends in. Kinds are read from the regulator's description of each log, not from its curves. The date is when the log entered the RRC's imaged log database; a run date is shown where the index gives a different one (mostly logs before 2017: since digital filing began that year, the index gives the filing date for both). Nothing is estimated.
Developers: this page as JSON is GET /v1/data/logs, documented in the API reference.