Time domain versus depth domain – storage
You can work in both the time and the depth domains. However, not all objects are supported in the time domain.
| Can be used in the time domain? | Conversion methods available | Can be used in the depth domain? | |
|---|---|---|---|
|
Seismic volumes |
Yes |
Time to Depth |
Yes |
|
Polyline sets |
Yes |
Time to Depth Depth to Time |
Yes |
|
Tri-meshes (triangulated surfaces) |
Yes |
Time to Depth Depth to Time |
Yes |
|
2D grids |
Yes |
Time to Depth Depth to Time |
Yes |
| Point sets | Yes |
- |
Yes |
|
3D grids |
No |
- |
Yes |
|
Wells |
No |
- |
Yes |
|
Well markers |
No |
- |
Yes |
|
Well designs |
No |
- |
Yes |
The support of workflow processes in the different domains also corresponds to the table above. In more detail, the following workflow processes can be used in the time and depth domains:
- Data Import – time domain objects can be imported by explicitly specifying the depth unit in time. This can be done either in the file header (in case the file format supports this) or using the Data Import Validation dialog, in which you can specify the depth units for imported data. See Importing, creating and exporting your data for more information.
- Seismic Interpretation – interpretation products (i.e. polyline sets, point sets, tri-meshes, and 2D grids) can be stored in both domains depending on the seismic volume on which they are based. In addition, the associated Editing Tools can be used in both time and depth domain.
Note that workflow processes other than Seismic Interpretation are confined to the depth domain.