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.

  • ABowen Davis Unit 1 #753H
FormationA
Rustler2,434 MD 665
Tamarisk Anhydrite2,362 MD 737
Salt Top2,263 MD 836
Base of Salt-1,644 MD 4,743
Lamar-1,850 MD 4,949LAMAR LIMESTONE
Bell Canyon-1,876 MD 4,975
Delaware-1,880 MD 4,979
Cherry Canyon-2,825 MD 5,924
Brushyporosity-4,054 MD 7,153
Brushy Canyon-4,152 MD 7,251
Bone Springs Lime-5,624 MD 8,723
Bone Spring-5,664 MD 8,763
Leonard-5,743 MD 8,842LEONARD A SHALE
1ST Bone Spring-6,639 MD 9,738
2ND Bone Spring-7,165 MD 10,264
3RD Bone Spring-8,037 MD 11,136
Wolfcamp-8,590 MD 11,689

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.