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.

  • APure-University #3
FormationA
Tubb-3,562 MD 6,213TOP TUBB
Wolfcamp-4,686 MD 7,337TOP WOLFCAMP
Cisco-5,330 MD 7,981TOP CISCO
Canyon-5,480 MD 8,131TOP CANYON
Strawn-6,066 MD 8,717TOP STRAWN
Bend-6,276 MD 8,927BEND DETRITAL
Woodford-6,996 MD 9,647TOP WOODFORD
Top Devonian-7,294 MD 9,945
Devonian-7,299 MD 9,950
Top Silurian-8,254 MD 10,905
Sirlurian-8,273 MD 10,924
Silurian-8,273 MD 10,924
Silurain-8,273 MD 10,924
Top Fusselman-8,314 MD 10,965
Fusselman-8,333 MD 10,984
Montoya-8,476 MD 11,127

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.