TOOLS · CROSS-SECTION · TEXAS

Well cross-section

Formation tops for up to eight Texas wells side by side, from their completion filings.

How to read it →

Each column is a well, lettered in the order drawn: west to east when every well has a location, or the order you list them (drag a well in the list, or switch to "As listed"). A well with no tops filed is listed but not drawn.

Under the subsea datum depths are elevation minus measured depth, so tops line up regardless of surface terrain; a value above zero sits above sea level. When not every well reports an elevation the section is in measured depth and the columns are not datum-aligned.

Each formation filed in more than one well has its own color, joined between neighboring wells and shaded down to the next formation both filed. Nothing is interpolated.

Where tops come from →

Section · 1 well drawn

One more well with tops draws the section. Add one from the wells nearby, or search for one.

Tops by well

Subsea feet, with measured depth beneath; the name as filed where it differs; a dash where the well has no top filed for the formation.

  • AMeans, J.S. a/C 2 #2267
FormationA
Rustler1,231 MD 1,906
Yates190 MD 2,947
Seven Rivers39 MD 3,098
Queen-599 MD 3,736
Grayburg-908 MD 4,045
San Andres-1,240 MD 4,377SAN ANDRES - CO2 FLOOD, HIGH FLO
Glorieta-2,534 MD 5,671
Clear Fork-2,872 MD 6,009
Tubb-4,062 MD 7,199
Canyon-6,849 MD 9,986
Strawn-7,234 MD 10,371
Atoka-7,615 MD 10,752
Barnett-7,859 MD 10,996
Mississippian-8,662 MD 11,799MISSISSIPPI LIME
Woodford-8,942 MD 12,079
Devonian-9,019 MD 12,156
Wristen-9,309 MD 12,446
Silurian (undifferentiated)-9,526 MD 12,663SILURIAN

About this data

Formation tops and elevations from the RRC dbf900 wellbore file (completion filings), names normalized to the formations registry; well identity from the permit record, location from the shared well record. Subsea is elevation minus measured depth. Nothing between filed tops is estimated.

New to these records? completion reports and the wellbore file

Developers: this page as JSON is GET /v1/data/cross-section, documented in the API reference.