WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-007-30863

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.

Within0.5 mi1 mi2 mi3 mi5 mi10 mi25 miof API 42-007-30863Clear

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.

3 LOG FILES ON 3 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1

Well DistancemiLogas describedIntervalft, as filedDatereceived
State Tract 277 #242-355-33549Nueces, TX · Lamar Oil & Gas Inc.1.39Acoustic PorosityTIFFHIGH RESOLUTION INDUCTION LONG SPACED SONIC2,760 to 11,672Feb 2, 2007run Sep 18, 2003
State Tract 277 #342-355-33581Nueces, TX · Lamar Oil & Gas Inc.1.43Neutron PorosityTIFFneutron log with gamma ray & ccl9,132 to 9,708Feb 9, 2007run Mar 23, 2005
State Tract 284 #142-355-33710Nueces, TX · Lamar Oil & Gas Inc.1.98ACOUSTIC POROSITYTIFF2,625 to 13,062Sep 19, 2008run May 17, 2005

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.