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.

  • ALink VJ Ranch 25-36 H #733H
FormationA
Rustler2,142 MD 705
Salt Top1,726 MD 1,121
Base of Salt-1,033 MD 3,880
Lamar-1,229 MD 4,076LAMAR LIMESTONE
Bell Canyon-1,246 MD 4,093
Delaware-1,246 MD 4,093
Cherry Canyon-2,198 MD 5,045
Brushyporosity-3,406 MD 6,253
Brushy Canyon-3,558 MD 6,405
Bone Springs Lime-5,131 MD 7,978
Bone Spring-5,174 MD 8,021
1ST Bone Spring-6,136 MD 8,983
2ND Bone Spring-6,749 MD 9,596
3RD Bone Spring-7,253 MD 10,100
Wolfcamp-8,217 MD 11,064
Wolfcamp U3 Bow-8,790 MD 11,637
Wolfcamp U4-8,925 MD 11,772

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.