WELL LOGS · UNITED STATES · ONE ROW PER LOG
Well logs within 2 mi of API 42-355-81237
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.
2 LOG FILES ON 2 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1
| Well | Distancemi | Logas described | Intervalft, as filed | Datereceived |
|---|---|---|---|---|
| State Tract 431 #142-355-33963Nueces, TX · TR Offshore LLC | 1.08 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 7,800 to 8,679 | Dec 21, 2012run Oct 31, 2009 |
| State Tract 433 Gas Unit #242-355-33651Nueces, TX · Petrogulf Corporation | 1.29 | Combination: Resistivity/Neutron Density PorosityTIFFHIGH DEFINITION INDUCTION COMP. Z-DENSILOG COMP. NEUTRON GAMMA RAY LOG | 2,038 to 8,963 | May 20, 2008run Dec 22, 2004 |
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.