Time vs depth: the two domains of seismic

Part 1, Foundations of Seismic

Learning objectives

  • Distinguish two-way travel time (TWT) from real depth and state when each is used
  • Compute depth from time for a single layer and for a stack of layers
  • Differentiate average, interval, and RMS velocities and state the Dix relation
  • Estimate depth uncertainty from velocity uncertainty at a target horizon

Seismic data is almost always displayed with two-way travel time (TWT) on the vertical axis, not depth. This is not a display convention: it is what the instrument measures. The earth, on the other hand, lives in depth. Every number that matters to drilling is a depth: where to set casing, how much overburden the well pays for, where a reservoir starts and ends. The process of converting seismic times to real depths is called time-to-depth conversion, and understanding it well is the difference between an interpreter whose maps match reality and an interpreter whose prospects get drilled in the wrong place.

Why time, not depth?

A seismic source fires and a receiver records the arrival time of returning echoes. That time is all the instrument knows. To turn time into depth, you need the velocity of the rocks the wave travelled through, and velocity is not constant. Shallow shales are slow (1800 to 2400 m/s), carbonates are fast (4000 to 6500 m/s), and every boundary in between changes the local rate at which time converts to depth. The seismic section plots time because time is what was measured; the velocity model plus integration gives you depth.

Almost every display axis labeled "ms" or "s" in interpretation software means two-way travel time. A reflector at 1200 ms TWT means the acoustic wave travelled from the surface down to the reflector and back in 1.2 seconds. Half that, the one-way time, is what you multiply by the velocity to get depth: z=V tTWT/2z = V\,t_{\mathrm{TWT}}/2.

Three velocities appear repeatedly in seismic work. It is worth being precise about which is which.

Average, interval, and RMS velocities

  • Interval velocity (VintV_{\mathrm{int}}): the velocity inside a single layer. This is what a sonic log gives you at a specific depth, and what the Dix equation extracts from RMS velocities.
  • Average velocity (VavgV_{\mathrm{avg}}): the single velocity that, if the entire overburden had that velocity, would produce the same total time-to-a-given-depth as the actual layered medium. Vavg=2ztotal/ttotalV_{\mathrm{avg}} = 2 z_\text{total} / t_\text{total}.
  • RMS velocity (VrmsV_{\mathrm{rms}}): the root-mean-square of the interval velocities, each weighted by the time spent in its layer, Vrms2=βˆ‘iVint,i2 Δti/tV_{\mathrm{rms}}^2 = \sum_i V_{\mathrm{int},i}^2\,\Delta t_i / t. For flat layers and short offsets it is the velocity in the NMO equation, so it is, approximately, what a stacking-velocity analysis picks.

The distinction matters. Stacking velocities approximate RMS velocities, and VrmsV_{\mathrm{rms}} is never less than VavgV_{\mathrm{avg}}: it weights the fast layers more, and the two are equal only where the velocity does not change. Converting time to depth with the stacking velocity as if it were the average velocity therefore puts every reflector too deep, by a few percent in a simple layer cake like the one below and by more where velocity contrasts are strong: on a deep prospect, a hundred metres or more.

The Dix relation

What you pick in velocity analysis is a stacking velocity, which approximates VrmsV_{\mathrm{rms}}. If you have RMS velocities at two successive times t1t_1 and t2t_2, the interval velocity of the layer between those two times is given by the Dix equation:

Vint2=Vrms,22β‹…t2βˆ’Vrms,12β‹…t1t2βˆ’t1V_{\mathrm{int}}^2 = \dfrac{V_{\mathrm{rms},2}^2 \cdot t_2 - V_{\mathrm{rms},1}^2 \cdot t_1}{t_2 - t_1}

This is the Dix inversion: it turns a set of time-and-RMS-velocity pairs from your stacking analysis into a layer-cake interval-velocity model. The model is noisy, because Dix amplifies a pick error by about (Vrms,2/Vint)2 t2/(t2βˆ’t1)(V_{\mathrm{rms},2}/V_{\mathrm{int}})^2\, t_2/(t_2 - t_1), most in intervals that are thin in time, but it is the bridge between what processing gives you and the velocity field you need for depth conversion. In practice, interval-velocity models are smoothed and cross-checked against well sonic data before being trusted for depth work.

The figure below is a four-layer earth: shale, sand, shale and carbonate. Pick a reflector by its two-way time and read its depth, then make one layer's velocity wrong in the model you convert with and see where the error lands.

Time domain vs depth domainTime (ms)β†’Γ— v(z)Depth (m)

The figure opens with the deep shale, layer 3, converted 10% too fast: 3740 m/s for its true 3400 m/s. The reflector picked at 1.500 s lands at 2303 m instead of 2235 m, 68 m too deep, and plate (c) shows where that error is made: nowhere above 0.900 s, steadily through the 400 ms of layer 3, and nowhere below it, where it is simply carried down. Time is fixed by what the wave measured; depth is fixed by what you believe the velocities to be.

Make the error 15%, 3910 m/s, and the reflector moves 102 m, which is 15% of the layer's 680 m. That is the whole rule: a fractional error in a layer's velocity is the same fractional error in its thickness, and every deeper reflector inherits it. The same 15% in the carbonate costs 135 m, because at 4500 m/s its 400 ms are 900 m of rock. Switch the conversion to the stacking velocity and the reflector at the base, 1.700 s, lands 103 m (3.8%) too deep with no velocity error at all.

Depth uncertainty, rule of thumb

For a layer with interval velocity VV and two-way time thickness Ξ”t\Delta t, a fractional velocity error Ξ”V/V\Delta V / V produces a depth error of (Ξ”V/V)(VΞ”t/2)=(Ξ”V/V) h(\Delta V / V)(V \Delta t / 2) = (\Delta V / V)\, h, where hh is the layer's thickness. Errors accumulate downward: every shallow-layer velocity error propagates to every deeper target. Fields with good well control can get to 1 to 3% depth accuracy at the target level; fields with poor control may see 5 to 10%, meaning a 3000 m prospect could be anywhere between 2850 and 3150 m at 5% and between 2700 and 3300 m at 10%. This is why interpreters and drill engineers spend so much time on the velocity model.

One practical detail. Depth conversion can be done two ways: vertical stretch through a velocity model, integrating the interval velocity down each trace (what the figure does, and what most interpretation software does behind the scenes) or ray-tracing (which also accounts for bent ray paths at dipping layers and is more accurate in structurally complex areas). Time migration positions events correctly only where velocity varies slowly sideways; depth migration goes further and outputs the section directly in depth using a 3D velocity volume. In a structurally complex field the cleaner workflow is pre-stack depth migration followed by interpretation in depth, which removes the separate time-to-depth step; the depth image is still only as right as its velocity model, and it is tied to well tops before anyone drills on it.

References

  • Bacon, M., Simm, R., & Redshaw, T. (2003). 3-D Seismic Interpretation. Cambridge University Press.
  • Brown, A. R. (2011). Interpretation of Three-Dimensional Seismic Data (7th ed.). AAPG Memoir 42 / SEG IG13.
  • Yilmaz, Γ–. (2001). Seismic Data Analysis (2 vols.). Society of Exploration Geophysicists.
  • Sheriff, R. E. (2002). Encyclopedic Dictionary of Applied Geophysics. Society of Exploration Geophysicists.

This page is prerendered for SEO and accessibility. The interactive widgets above hydrate on JavaScript load.