Geometry/Headers

This chapter contains information to assign a geometry,

manipulate trace headers and the Database, and quality
check the Database.

In This Chapter
➲ Geometry Assignment Overview
➲ Geometry Assignment Map
➲ Assigning a Geometry
To assign a geometry, you will need to open one of the
following spreadsheet processes:
➲ 2D Land Geometry Spreadsheet*
➲ 2D Marine Geometry Spreadsheet*
➲ 3D Land Geometry Spreadsheet*
➲ 3D Marine Geometry Spreadsheet*
➲ VSP Geometry Spreadsheet*
➲ Crooked Line Geometry Spreadsheet*

Before, during, and after you assign a geometry, you can use
the following processes to manipulate trace headers and the
Database, and to quality check the Database:

Other Docs Search Page Known Problems

938 ProMAX® Reference

Trace Header Manipulation

➲ Cross Well Header Editing
➲ Database/Header Transfer
➲ Geometry Header Preparation
➲ Header Delete
➲ Header Values
➲ Header to Horizon Table Transfer
➲ Header to Kill Table Transfer
➲ Inline Geometry Header Load
➲ Database/Header Compare
➲ Trace Header Math
➲ VSP Inline Geometry Header Load

Database Manipulation
➲ ASCII/EBCDIC File Import
➲ ASCII/EBCDIC File Export
➲ 3D Poststack Geometry
➲ Assign CDP Flex Binning
➲ Assign Common Ensemble Value
➲ CDP Binning
➲ CDP Taper
➲ Create CDP Database
➲ Database Parameter Merge
➲ Expand Flex Binning
➲ Extract Database Files
➲ Merge Database Files
➲ Pad 3D Stack Volume
➲ Pad Traces
➲ Remove Padded Traces
➲ Samples to Header
➲ Trace Length
➲ Trace Math
➲ UKOOA File Import

Other Docs Search Page Known Problems

939 ProMAX® Reference

Geometry Quality Check

➲ Graphical Geometry QC
➲ Source Receiver Geometry Check
➲ XYGraph

Other Docs Search Page Known Problems

Geometry Assignment Overview940 ProMAX® Reference

Geometry Assignment Overview

Processing data within the ProMAX® system generally

requires that the data be related to a description of the field
geometry used during the data collection process. We use the
term Geometry Assignment to refer to the process of creating
the actual description of the field geometry, and then tieing
that geometry description to the traces which will be used in
subsequent processing flows. The geometry assignment
process assigns each trace to a single shot, receiver, common
depth point, inline, crossline, and offset bin. Other individual
values for each trace, shot, receiver, CDP, and offset bin are
also computed.

The first step in the Geometry Assignment process, the

description of the field geometry, can actually be
accomplished using a number of processes. As detailed later
in this document, the actual use of these processes will
depend, for the most part, on the type of geometry
information that you have available. However, information for
the geometry description will typically come from the trace
headers of the field tapes, from ASCII files provided with the
survey, or from observer’s notes which can be input and
edited by hand.

No matter what process you use to create the field geometry

description, the actual information will be stored within the
ProMAX® database. This database is a collection of binary
files, called the Ordered Parameter Files (OPFs). These files
are organized under the ProMAX® Area/Line directory
structure where each Order is a different subdirectory under
the Line directory. In order to edit the attributes found in the
individual Orders, you can activate a flow containing one of
the Geometry Spreadsheet Editors. These editors serve as the
basic interface to the OPF database. In addition to these
spreadsheet processes, graphical tools and 3D visualization
tools are available for quality control and graphical editing of
the information found in the OPF database.

Having created a valid ProMAX® database, you complete the

geometry assignment process by loading a standard set of
information from the OPF database into the headers of a
dataset which is to be used for further processing. This step
is accomplished by including Inline Geom Header Load
within a processing flow. Assuming that the loading of the

Other Docs Search Page Known Problems

Geometry Assignment Overview941 ProMAX® Reference

headers completes successfully, you will have created a

ProMAX® dataset which is stamped with a global flag as
‘matching the database’, indicating that the dataset headers
and OPF files are in fact in sync with one another. In
addition, the dataset is also stamped as having ‘valid trace
numbers’. This designation of ‘valid trace numbers’ is
generally transparent, but does serve an important function
in allowing for the most efficient trace processing within the
ProMAX® system.

As a final note, you should be aware that our discussion of

these geometry issues relates specifically to the processing of
prestack data. However, some poststack processes within the
ProMAX® system may require the use of CDP attributes
contained in the OPF Database. If you are only processing
poststack datasets, Create CDP Database for 2D datasets
and 3D Poststack Geometry for 3D datasets can be used to
create the required OPF files.

Other Docs Search Page Known Problems

Geometry Assignment Map942 ProMAX® Reference

Geometry Assignment Map

The following graphic map provides a generalized look at the

main functional components you will encounter when
undertaking the geometry assignment process.

EXTERNAL INPUT
UKOOA
Observer notes
ASCII

Raw Field Data

Field Tape
Promax

Extract Database File

(Optional)

Geometry
Spreadsheet
Inline Geom
Header Load
Ordered Parameter
Files
Output Promax
Dataset

Geometry
matches database
Graphical QC
and Edit Valid trace
numbers
Database Display
XY Graph

Other Docs Search Page Known Problems

Geometry Assignment Map943 ProMAX® Reference

As you can see from this diagram, the OPF Database

functions as the repository for all of the required geometry
information, with interaction to the OPF Database coming
from a number of possible processes and sources. The
Geometry Spreadsheets are the windows used to display and
edit the contents the OPF Database. These processes
function as the primary means of editing attributes which are
contained in the OPFs. The Geometry Spreadsheet processes
also contain the binning and finalization functions, which are
required operations for creating a final set of OPF Database
entries.

Seismic datasets can be used to provide input to the OPF

Database, using Extract Database Files. This process is
used to extract field geometry information which is often
recorded in the headers of the raw data collected in the field
or placed in common data exchange formats.

Inline Geom Header Load is used to update the headers of

the ProMAX® datasets with a standard set of required
information taken from the OPF Database. Therefore, Inline
Geom Header Load ensures that all of the traces are
concurrent with the information in the OPF Database.

Basic Geometry Assignment Components

This section is intended to provide you with a basic

understanding of the OPF Database and its relationship
between field geometry, the various Geometry Spreadsheet
processes, and the trace headers of ProMAX® datasets.

The OPF Database

A complete discussion of the organization and philosophy

behind the use of the OPF Database can be found in the
Ordered Parameter Files chapter. In general terms, the OPF
Database consists of a number of binary files that are used to
store geometry and other processing information in a format
which is tailored for seismic data processing. Each file
consists of information related to a specific processing
domain, or order. The information is stored against a number
of standard parameters; thus the term Ordered Parameter
File. A set of OPFs can be thought of as a matrix of
information. When viewed in the spreadsheet, each column of
values is a separate file under the OPF directory. Each row in
the table serves as the index into that table, whose values
typically range from 1 to N.

Other Docs Search Page Known Problems

Geometry Assignment Map944 ProMAX® Reference

Many of the standard attributes in these tables are the basic

items which describe the field geometry used during data
collection, items such as X and Y locations, elevations,
arbitrary station location values. In addition to these
standard geometry attributes, the OPF Database is used by
many processing tools to store domain specific information,
providing ease of storage, and subsequent retrieval during
processing.

The OPF Database and Field Geometry

When relating the Ordered Parameter Files to field geometry,

the term order is can be thought of as a specific data
collection or processing domain. For example, traces are
collected from unique shots, so it is natural to have a Shot
domain order as part of the OPF structure. Every shot in the
survey will equate to one index or row in this shot domain
order. In another case, traces associated with different shots
can be logically grouped because they were all collected at a
specific receiver location; each receiver location comprises a
single element in a different order, the receiver domain order.
Similarly, geometry domains or database orders can be
constructed for other orders, such as the common depth
point domain or recording channel.

The specific orders which the ProMAX® system recognizes

are as follows:
• LIN is the line or survey
• SIN is the shot or source
• SRF is the receiver
• CDP is the common depth point
• CHN is the channel
• OFB is the offset bin
• PAT is the pattern or relation of shots to receivers
• TRC is the trace
• ILN is the inline (3D only)
• XLN is the crossline (3D only)
• BHC is the borehole position (VSP only)

One of the basic uses of the OPF Database is to avoid the

redundant storage of information. For example, consider a

Other Docs Search Page Known Problems

Geometry Assignment Map945 ProMAX® Reference

shot record which is taken at some specific elevation. That

single source location may have many traces associated with
it, yet each of the traces collected as part of that single shot
record will have a single value for the elevation of the source
point. This single value can be stored once as an attribute of
the SIN database, rather than storing the value against every
trace. In our example, one source elevation is stored against
each shot index in the SIN database. Some database
attributes are stored once for each and every trace in the
survey, in the TRC domain. Those attributes are generally the
cross domain lookup values, which are transparent to you,
and are used by the processing software to locate traces
across each of the other orders.

The LIN database performs a special function as a repository

for global information relative to a specific line or survey. For
example, the processing units of the survey are stored as a
single LIN attribute. In the ProMAX® system, the concept of a
Line is extended to cover a complete 3D survey or a VSP
survey.

The OPF Database and Geometry Spreadsheet Processes

Each of the Geometry Spreadsheet processes essentially

function as a spreadsheet editor, which operates on the
information in the OPF Database. The functions within each
of the geometry spreadsheet processes,
➲ 2D Land Geometry Spreadsheet*
➲ 2D Marine Geometry Spreadsheet*
➲ 3D Land Geometry Spreadsheet*
➲ 3D Marine Geometry Spreadsheet*
➲ VSP Geometry Spreadsheet*
➲ Crooked Line Geometry Spreadsheet*

are described in detail later in this document. While each

process is used to provide access to a specific type of
geometry description, each process does have the same basic
functionality. Again, these spreadsheet editors provide a
means of entering and editing information which is part of
the OPF Database. In addition, full ASCII file import and
export functionality is contained within each spreadsheet
process, and access to graphical quality control tools are also
provided from within each process.

Other Docs Search Page Known Problems

Geometry Assignment Map946 ProMAX® Reference

A geometry spreadsheet process is typically run as a

processing flow in and of itself. Running one of these
processes in a flow creates a primary window, from which
separate spreadsheet editors can be accessed from the main
menu selections. In some cases, accessing one of these
specific menu items opens an edit window which sits directly
on top of one of the database orders. For example, selecting
Receivers from the 2D or 3D Land Geometry Spreadsheet
opens for edit the information in the SRF order of the OPF
database files.

The diagram below shows how this Receiver spreadsheet

looks, and indicates its direct relationship to the SRF OPF
Database.

Ordered Parameter File

Order Infotype Attribute
SRF Geometry Station

Trace Header
SRF_SLOC

In this diagram, the Station is one column in the Receiver

spreadsheet. It actually exists in the OPF database as part of
the Order: SRF; Infotype: Geometry; Attribute: Station.
Editing any single cell under Station edits the value at a
specific index point within the SRF database. While editing a
spreadsheet, the original information is stored in undo files
and if necessary, you can Abort a spreadsheet editing
session, without making any changes to the actual OPF files.

In reference to the above diagram, note that the receiver

Station value will also be used to create a standard ProMAX®

Other Docs Search Page Known Problems

Geometry Assignment Map947 ProMAX® Reference

HEADER entry. Here, the Station value is mapped to the

trace header SRF_SLOC. This final header mapping is a
function of Inline Geom Header Load. Not all OPF values are
mapped into ProMAX® headers. For example, the Pattern
spreadsheet is typically used to tie the traces from any shot
to specific receivers. This Pattern information is only used
internally during the geometry assignment process, and is
not reflected in any of the standard ProMAX® headers.

In some cases, accessing a menu item from the main

geometry spreadsheet window opens up a dialog box rather
than an actual spreadsheet editor. For example, selecting Bin
from the main window opens a window which is used to input
information for CDP binning and to finalize the database.
Although you are not directly editing information in any of
the OPF orders, this dialog information is used to create
required information in the Database.

The OPF Database and Trace Headers

In the final stage of the geometry assignment process, the

actual seismic trace data is linked to the OPF Database, by
passing input traces through a processing flow containing
Inline Geom Header Load. This process creates a set of
standard trace headers, based upon the geometry description
created and stored in the OPF files. This process is
sometimes referred to as ‘loading the geometry’. The
remainder of this discussion focuses on the relationship of
the trace headers to the OPF Database. For a more complete
discussion of trace header components used in the ProMAX®
system, refer to Trace Header File in the Creating ProMAX®
Datasets section of the ProMAX® Seismic Datasets chapter.

One of the primary functions of the OPF Database as it

relates to trace data is to provide the index information used
for both random access and for rapid sorting of datasets
within a processing flow. Inline Geom Header Load is an
integral part of this process. In addition to copying geometry
information from the OPF Database to the trace headers,
Inline Geom Header Load will set global flags in the dataset
indicating that “the geometry in the headers matches the
database” and that “trace numbers are valid, and can be
used to access the database”. With these global header flags
set, a dataset can be accessed within the ProMAX® system in
the most efficient manner possible.

Other Docs Search Page Known Problems

Geometry Assignment Map948 ProMAX® Reference

When these global access flags are set to true, specific traces
can be processed by accessing the cross domain lookup
values which are stored in the TRC database; these dataset
sorting mechanisms are transparent. It is only important to
use Inline Geom Header Load as a final step in the geometry
assignment process. You can ascertain whether or not a
dataset matches the database and has valid trace numbers
by clicking MB2 on the datasets’ listing.

Dataset access within the ProMAX® system does not

absolutely require the assignment of geometry for many
processes. In fact, datasets which are not stamped as having
valid trace numbers can be sorted using any available trace
headers in the raw input data, although this header sort will
be slower than sorting by access to the OPF Database.
However, there are some typical processes which do
absolutely require that the dataset be stamped as matching
the database, such as the basic residual static processes,
where the decomposition of the individual trace values into
their appropriate surface consistent components will be
based upon the use of the index values found in the OPF
database.

You should also be aware that some processes will actually

set the value of the geometry matching/trace number valid
flags on prestack data to be false. A typical example is the
process of creating DMO offset bins and running a DMO
process. In this case, traces can be summed and reorganized
into a new bin space whose output traces do not fit the actual
geometry of the input field data. In those cases, should you
need to run a process on that dataset which requires access
to the OPF database, the geometry will typically need to be
recreated, usually in a separate Line. This can be easily
executed by extracting geometry from the new trace dataset,
finalizing the geometry in a spreadsheet process, and loading
the trace headers of this dataset with Inline Geom Header
Load.

As a final note, be aware that datasets which are created

from the input of a dataset which is stamped as ‘matching
and valid’ will also be created as ‘matching and valid’. Inline
Geom Header Load will generally need to be run one time
within a line. However, this process can be used at any time if
there is a need to input datasets which have not been loaded
with the correct geometry. In fact, it is important to note that
if the basic geometry information created in the OPF
Database is ever altered, any datasets required for further

Other Docs Search Page Known Problems

Geometry Assignment Map949 ProMAX® Reference

processing should be reloaded with the new geometry

description, using Inline Geom Header Load.

Other Docs Search Page Known Problems

Assigning a Geometry950 ProMAX® Reference

Assigning a Geometry

Geometry assignment consists of three main steps:

1. Select and complete a method for building the OPF
Database
2. CDP bin the trace midpoints and finalize the OPF
Database using the spreadsheet
3. Load pertinent OPF Database attributes to the trace
headers

The application of these steps, or the assignment method,

varies depending upon the available information. In order to
illustrate this, the steps and corresponding example flows for
the different assignment methods are described below. The
flowchart in the previous section should help you visualize
the components involved in geometry assignment.

Select and Complete a Method for Building the OPF Database

Before you can build a database, you must decide which

geometry assignment method to use. Your choice is a
function of the field information existing in the trace headers
of the dataset. You have the following choices:
• Full Extraction extracts all geometry information from
field tape headers into the OPF databases using the
Extract Database Files process. This approach
assumes that all required geometry related information
exists in the headers of the incoming dataset.
• Hand Input allows you to hand input geometry informa-
tion from field and survey notes into a spreadsheet using
one of the geometry spreadsheet processes. The data
from arbitrary columnar ASCII files or fixed format
UKOOA files may be imported directly in to the database
using the spreadsheets.
• Partial Extraction imports the geometry information
existing in the input trace headers from field data and
hand input the remaining information using one of the
geometry spreadsheet processes.

To determine which method will work best for you, consider

the questions in the following flowchart:

Other Docs Search Page Known Problems

Assigning a Geometry951 ProMAX® Reference

How to Select a Geometry Assignment Method

Do you want to
use x,y locations No Do you want to No
and source,receiver minimize the Partial
number of times Extraction
stations in the data is read?
the headers?
Yes Yes

Full Hand
Extraction Input

The second question is actually a little more complicated

than it may appear. If the Partial Extraction path is selected,
it will require another read of the data to get the geometry
installed into the headers. However, there may be benefits
obtained by reading the data once in the partial extraction
that outweigh the inconvenience of having to pass over the
data for a second time to install the geometry into the
headers. For example, the partial extraction will retrieve
existing trace header information for the shots, thus saving
considerable time in manual editing of the spreadsheets.
There are also some quality control aspects that can be
realized by reading the trace headers.

Regardless of which method you select, you will use Extract

Database Files and/or one of the Spreadsheet processes to
build your OPF Database.

The following is an explanation of the different methods.

Extract Database Files for Building OPF Database

Extract Database Files is used when assigning geometry for

either the full or partial extraction methods. This process is
used to extract geometry information from the incoming trace
headers and write it to the respective OPF Databases.

For a full extraction, you need the Shot and Receiver Surface
Location numbers, FFID and Recording Channel information.
It is also advisable to have shot and receiver X-Y coordinates
in the input trace headers. For a partial extraction you only

Other Docs Search Page Known Problems

Assigning a Geometry952 ProMAX® Reference

need to have a source identification number (e.g. FFID) and

recording channel number.

In the Full Extraction mode Extract Database Files extracts

the source and receiver information and then creates the
TRC, SIN, and SRF OPFs. These OPFs reflect information for
the individual traces, the shots, and the receivers. In the
Partial Extraction mode, no receiver information exists so the
TRC and SIN are the only OPFs that are created

Geometry Header Preparation is an optional processing

macro, which manipulates header values prior to extracting
geometry information. You may elect to execute Geometry
Header Preparation to fix headers in which channel numbers,
field file IDs, or ensemble boundaries are incorrect. You can
create or fix headers to meet the extraction requirements.

Earlier in this document we defined the geometry assignment

process to consist of three main steps:
1. Select and complete a method for building the OPF
Database
2. CDP bin the trace midpoints and finalize the OPF
Database using the spreadsheet
3. Load the pertinent OPF Database attributes to the trace
headers

The processes involved in the first step are variable

depending on the method selected. These steps can be
outlined as follows:

Other Docs Search Page Known Problems

Assigning a Geometry953 ProMAX® Reference

Step 1) Build the Database, shot and receiver, and pattern information

Full Extraction Partial Extraction Hand Input

1) Extract Database Files 1A) Extract Database Files 1) Spreadsheet

1B) Spreadsheet

Step 2) Assign each trace to a CDP

Step 3) Load the geometry to the trace headers

Example Flow

The following flow example is for Step 1 for Full Extraction or

Step 1A for Partial Extract Method using Geometry Header
Preparation and Extract Database Files:
SEG-Y Input

Geometry Header Preparation (optional)

Extract Database Files

Disk Data Output

In this example, the input data resides on a tape in SEG-Y

format. These data will be converted to internal ProMAX®
format using SEG-Y Input. Geometry Header Preparation
can be used to fix trace header information, if necessary.
Extract Database Files extracts and writes the available
geometry information from the incoming trace headers to the
corresponding OPF Database files, and Disk Data Output
writes a ProMAX® format dataset to disk.

Geometry Spreadsheet for Building OPF Database

The spreadsheets are used to hand input, import, or modify

geometry information in the SIN, SRF and PAT OPFs. Once
the spreadsheets are completed and closed, the information
is written to the proper OPF Database. You have a choice of
the following spreadsheet processes depending on the type of
data you are working on: 2D Land Geometry Spreadsheet,

Other Docs Search Page Known Problems

Assigning a Geometry954 ProMAX® Reference

2D Marine Geometry Spreadsheet, 3D Land Geometry

Spreadsheet, 3D Marine Geometry Spreadsheet, VSP
Geometry Spreadsheet, or Crooked Line Geometry
Spreadsheet.

If you need to hand input all or part of your geometry

information, execute one of the geometry spreadsheet
processes to enter the required information to the Database.

Refer to the Geometry Spreadsheet Processes section for

details.

Example Flow
The following flow example is for Step 1 for Hand Input
method or Step 1B for Partial Extraction. If you have chosen
the Hand Input method for assigning geometry, this would
typically be the first flow to execute. In the case of partial
extraction, you would run this flow after executing Step 1A
described above.

As an example, you may need to complete the geometry

information step for a 2D land line. This flow would look as
follows:
2D Land Geometry Spreadsheet*

A normal geometry assignment consists of the following

steps:
1. Complete the Sources and Receivers spreadsheets.
In these spreadsheets you would enter the coordinates,
elevations, depths, stations, or other appropriate
information related to the sources and receivers. Some, or
all, of this information may have been written to the OPF
Database files using the Extract Database Files process.
You will also find that the spreadsheets are a convenient
tool for importing any pertinent ASCII disk files with
geometry description data.
2. Complete the Patterns Spreadsheet.
This step will not be needed in the Full Extraction Path.
For land data you would be required to enter the pattern
definition mapping sources to the recording receivers in
the Pattern spreadsheet.
For marine data you would be required to enter the
pattern defining the geometry of the streamer and the

Other Docs Search Page Known Problems

Assigning a Geometry955 ProMAX® Reference

positioning of the source relative to the input coordinates.

CDP Bin the Trace Midpoints and Finalize the OPF Database using the
Spreadsheet

Regardless of which assignment method used, you will

always execute one of the geometry spreadsheets to assign
each trace to a Common Depth Point (CDP) and finalize the
OPF Database.

The process of binning completes the geometry assignment to

the OPF Database. During this process, the remaining OPFs
for CDP, channel, and offset bin are created as well as the
lookup pointers required for surface consistent processing
and quick sorting of traces from disk. In the 3D applications,
the ILN (inline) and XLN (cross line) OPFs are also created.

Example Flow

The following flow example will assign each trace to a CDP by

binning and finalization. This example is for 2D straight line:
2D Land Geometry Spreadsheet*

Open a spreadsheet process if you do not alreadyhave one

open. Select Bin from the menu bar.

The CDP assignment and database finalization process

differs for land and marine 2D, crooked line, and the 3D
applications. Generally the following steps will be required:
1. Assignment
This step assigns each trace to its receiver, computes the
shot to receiver offset distance, the midpoint coordinate
and the shot to receiver azimuth.
2. Binning
The actual mechanics involved here differ for the different
geometries, but the goal is to assign each trace to a single
CDP.
3. Finalization
This step creates the final lookup tables for each trace
from the CDP order back to the other orders, such as SIN
and SRF.
Note: For the 3D applications, you will have the
opportunity to bin the data with various binning

Other Docs Search Page Known Problems

Assigning a Geometry956 ProMAX® Reference

parameters and compare the results prior to database

finalization. If entire shots or receivers are deleted from a
spreadsheet and the Finalization step is rerun, any
attributes previously created outside the spreadsheet,
such as first break picks and statics, will not match the
refinalized database and should be recreated.

Load Pertinent OPF Database Attributes to the Trace Headers

After the OPF Database is complete, the geometry

information is copied to the trace headers. Inline Geometry
Header Load automatically loads geometry information from
the OPF Database to trace headers in a processing flow. The
process uses up to three trace headers to match
corresponding OPF Database parameters. When a match is
found, geometry information pertaining to the trace is loaded
into the trace header. Traces may be excluded from the
output file if they do not exist in the OPF Database. Traces
identified in geometry but not found in the data are
considered missing. This matching technique allows
geometry to be loaded on subsets of data as it is acquired.

Use VSP Inline Geometry Load if you are transferring VSP

geometry information from the Database to trace headers.

To determine which Inline Geometry Header Load option to

use, consider the questions in the following flowchart:

How to Select a Geometry Header Load Option

No
Did you use a full or By channel
partial extraction? or other trace
header.

Yes

By valid
trace header.

Other Docs Search Page Known Problems

Assigning a Geometry957 ProMAX® Reference

By Valid Trace Headers

If you used a full or partial extraction to build a database,

you will have valid trace headers that uniquely match a trace
in a data file to a trace in the Database. Run Inline Geom
Header Load and choose the valid trace number option.

By Chan and Other Trace Headers

If you used field notes to build a database, and did not run
the extraction, the recording channel number and up to two
other trace headers, such as Field File ID or shot point
numbers are used to match a trace in a data file to a trace in
the database.

Channel numbers must be unique within the shot and if

need be, they can be re-sequenced using the Renumber and
resequence ensembles option in the Geometry Header
Preparation process.

Note: For marine data, the shift to final datum is performed

by Inline Geom Header Load. The gun and cable depths
from the DEPTH parameter file in the SIN and TRC Orders of
the Database are used to shift the data to sea level. These
parameters must be correctly entered for all shots and
channels during geometry assignment. A nominal or constant
value can be entered in the File/Setup menu.

Example Flow

The following flow will load the pertinent OPF Database

attributes to the trace headers:
Disk Data Input

Inline Geometry Header Load

Disk Data Output

You need to consider several options in this apparently

simple flow. The most important of which is to determine the
mode of trace identification. It is also important to
understand when trace headers can be overwritten instead of
writing a new prestack data file. These issues are covered in
later sections of the Geometry Documentation.

Other Docs Search Page Known Problems

Assigning a Geometry958 ProMAX® Reference

Other Docs Search Page Known Problems