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.

  • ASacroc Unit #270-5
FormationA
Yates1,555 MD 865
Yates - High Fluids and/OR Gas F1,555 MD 865
San Andres - High Flows, H2S, Co734 MD 1,686
San Andres734 MD 1,686
Glorieta-83 MD 2,503
Clear Fork-266 MD 2,686
Wichita-1,954 MD 4,374
Wichita Albany-1,954 MD 4,374
Wichita Albany - Over Pressured-1,954 MD 4,374
Wolfcamp-2,391 MD 4,811
Coleman Junction-2,391 MD 4,811
Coleman Junction - Possible Lost-2,391 MD 4,811
Cisco-4,188 MD 6,608
Canyon-4,456 MD 6,876
Canyon - Active CO2 Flood-4,456 MD 6,876

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.