MAPS · WELL LOGS · UNITED STATES · ONE POINT PER WELL

Well log map within 2 mi of API 42-311-36812

Wells with logs loaded into Petrora from the regulators' log indexes, one point each, violet where a matching log is digital (LAS). The filters are the log search's; a point opens the well's logs. Loaded so far for Texas; more states and data sources will follow.

Within0.5 mi1 mi2 mi3 mi5 mi10 mi25 miof API 42-311-36812Clear

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.

Loading the map…
Loading the map…

a matching log is digital (LAS)  images only

One point per well, where it is drawn on the well record or, failing that, the RRC's map of wells with logs; a horizontal's lateral runs from there. Wells with no location on file are counted above and not drawn.

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.