Professional Documents
Culture Documents
and
System Four ®
SEG Y Format
November 2006
1018-010007B
Copyright
i
ii
Chapter 1. History and Current Requirements
History The SEG Y format was published in 1975 and reflects the state of seismic
data recording at that time. The original format specified bit positions and
signal patterns for 800 bpi NRZI (Non-Return to Zero Inverted) and 1600 bpi
PE (Phase Encoded) recording formats. The original format also mentions
IBM's proposed 6250 bpi GCR (Group Coded Recording) format. Currently,
the type of media and recording technology used is not relevant to discussion
of the application specific format of data written to sequential media.
Current The SEG Y format allows for a collection of trace data of similar sample rate
Requirements and trace length on one tape. It specifies that all the data on one reel be from
one line. With 3D recording, it is not practical to have the restriction of all the
data on a given tape being from one receiver line. Therefore, Input/Output
Land Recording Systems do not restrict data to be from only one receiver line.
The restrictions on sample rate and trace length are also unnecessary.
However, I/O’s RSR system (Transcriber 2) system currently pads or trun-
cates traces to the same length.
I/O’s Scorpion and System Four systems set the Binary Header values for
Sample Interval and Number of Samples to zero (0), where zero means vari-
able Sample Interval and variable Number of Samples. Each Trace Header
contains the Sample Interval and the Number of Samples for that trace. This
was done to allow different record lengths and different sample intervals per
reel.
This document describes the differences between the I/O SEG Y specifica-
tion and the original SEG Y specification, now referred to as “SEG Y 1975”
or “Rev 0”.
NOTE
This document does not make reference to the second SEG Y publication
by the Society of Exploration Geophysicists: “SEG Y rev 1 Data Exchange
Format, SEG Technical Standards Committee, Release 1.0, May 2002.”
NOTE
I/O systems write two EOF marks at the end of data instead of one.
Text Block The first part of the Reel Identification Header consists of 3200 bytes of
EBCDIC data, which is the equivalent of 40 data cards. The original SEG Y
specified format for this block is illustrated in Table 2-4:
Each card image contains the character C in the first column. By definition,
card image numbers 23 through 39 are unassigned for optional use, so the text
shown in Table 2-4 is in the specified format. Unused characters are EBCDIC
Blank.
Proper system setup by the operator is required to ensure that all fields are
populated. It is also possible to treat the entire 3200 bytes as a free form
EBCDIC text block.
Starting with the RSR Transcriber 2 version 1.3.2, the EBCDIC block will be
populated in one of three ways. If there is a segyhdr.txt file in the project
directory, then the EBCDIC block will be filled with information from the
segyhdr.txt file. If there is no segyhdr.txt file but there is XTM information,
the first 6 lines of the EBCDIC block will be populated with the following
information, which comes from the XTM’s Job Text packet:
• Client
• Prospect
• Contractor
• Crew ID
• Location
• Observer
If there is no segyhdr.txt file and there is no XTM information available for
the output data range, the EBCDIC block will be blank, except for a C in
column 1 of all 40 lines. The data will be in EBCDIC format if the data
sample format is IBM floating point or IEEE with EBCDIC option. The data
will be in ASCII format if the IEEE ASCII option is selected. Column one in
each line is uppercase “C”. Blank characters are used to fill the 80 character
lines.
The Scorpion and System Four EBCDIC block will be populated by informa-
tion from their respective databases.
Binary Block The binary coded section of the Reel Identification header consists of 400
bytes, of which the first 60 bytes have assigned definitions and the remaining
340 bytes are unassigned for optional use. I/O systems use 14 of the
unassigned bytes as shown in Table 2-5.
It is strongly recommended that information on the following nine entries
always be recorded:
• Line number
• Reel number
• Number of data traces per record
• Number of auxiliary traces per record
• Sample interval this reel
• Number of samples per trace
• Data sample format
• CDP fold
• Measurement system
These are denoted with an asterisk in column 2 of Table 2-5. I/O systems set
many of these fields to 0 because the information is either unknown or more
appropriately documented in the Trace Identification header.
Trace Data Block Each Trace Data block consists of a 240-byte Trace Identification header
followed by the number of data samples specified in the Reel Identification
header binary block, bytes 3221-3222. The original format allows four data
sample formats. Of these four original data sample formats defined, only IBM
4-byte floating point is supported. I/O systems allow the use of a fifth data
sample format, the IEEE floating point format. This IEEE format is also the
recommended data sample format for the RSR Transcriber 2 and the only for-
mat for Scorpion and System Four.
Data from RSR/VRSR and MRX (Miniaturized Remote Extender) boxes are
normalized to their equivalent input voltage, expressed in millivolts (mV).
The maximum millivolt value depends on the preamp K-gain used in the box.
See Table 2-6 to relate the largest and smallest possible values on tape to a
given K-gain. The preamp K-gain is stored in trace header bytes 121-122.
RSR or MRX K-gain vs. Largest and Smallest values written to SEG Y tape
RSR or MRX K-gain (dB), Bytes 121- Largest absolute value written to tape Smallest absolute value written to tape,
122 (mV) other than zero (only LSB on)
Table 2-6. RSR or MRX K-gain vs. Largest and Smallest Values Written
to SEG Y Tape
RSR VectorSeis LSB Setting vs. Largest and Smallest values written
to SEG Y tape and multiplier to apply to return values to G’s
Least Significant Largest absolute Smallest absolute value written to tape, Multiplier to apply to data
Bit (LSB) Setting - value written to other than zero (only LSB on) to get LSB setting
value in nanoG’s tape
20 1.0 0.000 000 119 209 289 550 781 250 0.167 772 160
40 1.0 0.000 000 119 209 289 550 781 250 0.335 544 320
160 1.0 0.000 000 119 209 289 550 781 250 1.342 177 280
RSR using the current version of VectorSeis receivers, and Scorpion and Sys-
tem Four preserve the 20, 40, or 160 nG LSB values for VectorSeis data. No
scaling is necessary to read the data. Largest and smallest values are shown in
Table 2-8. See Trace Header byte 202 for the VectorSeis receiver scaling
code.
RSR VectorSeis (current version) Scorpion and System Four LSB Setting vs.
Largest and Smallest values written to SEG Y tape
Least Significant Bit (LSB) Setting - Largest absolute value written to Smallest absolute value written to
value in nanoG’s tape (G’s) tape, other than zero (only LSB on)
Analog data from Scorpion and System Four is normalized to their equivalent
input voltage, expressed in millivolts (mV). The maximum millivolt value
depends on the preamp scale factor used in the box. See Table 2-9 to relate
the largest and smallest possible values on tape to a given gain factor. The
preamp gain factor is stored in trace header byte 202.
Table 2-9. Scorpion and System Four Analog Largest and Smallest
Values Written to SEG Y Tape
Trace The original SEG Y binary coded trace header consists of 240 bytes, of which
Identification the first 180 bytes have assigned definitions and the remaining 60 bytes are
Header unassigned. I/O systems use all of the remaining 60 bytes and redefine some
obsolete bytes when recording VectorSeis data.
It is strongly recommended that information on the following six entries
always be recorded:
• Trace sequence number within line
• Original field record number
• Trace number within field record
• Trace identification code
• Number of samples this trace
• Sample interval in microseconds
These fields are denoted with an asterisk in column two of Table 2-10 and are
described in detail in the following paragraphs.
The trace sequence number within line entry (bytes 1-4) is used to count
traces through an entire write process. A write process may span more than
one tape. In this case, the first value of trace sequence number within line
entry on Tape 2 would not start with 1 but rather with a number one greater
than the last trace sequence number within line entry from Tape 1.
The original field record number entry (bytes 9-12) equals the file number
set by the RSR Transcriber 2, Scorpion and System Four operator. The file
number can also be taken from an IMAGE SEG-D tape when merged into a
RSR Transcriber 2 project. The original field record number entry can also
equal the Shot Id for unordered data that is made directly by reading an RSR
Data Collector Unit (DCU).
The trace number within field record entry (bytes 13-16) equals the trace
number within a record (an I/O Energy Point (EP)) starting with 1.
The trace identification code entry (bytes 29-30) is the same as the original
SEG Y specification with the addition of code 9 as unknown Aux type and
code 62 as GPS Aux/External data.
The number of samples this trace and the sample interval in microseconds
entries (bytes 115-116 and 117-118, respectively) are the same as in the reel
binary header block for RSR Transcriber 2. For Scorpion and System Four,
only the trace header contains the correct values for each trace. The reel
header values are set to zero (0) meaning that the trace length and interval can
vary throughout the reel.
Table 2-10 shows the I/O 240 Byte Trace Header in comparison with the
original SEG Y specification.
Table 2-10. 240 Byte Trace Header Original SEG Y Spec. vs. I/O Spec.
A
Analog-1C Gain Factor 2-8
B
bit positions 1-1
D
Data Collector Unit (DCU) 2-8
E
EBCDIC
Blank 2-2
block 2-3
data 2-2
format 2-3
text block 2-2
Energy Point (EP) 2-8
G
GCR (Group Coded Recording) format 1-1
GPS Aux/External data 2-9
I
IBM
4-byte floating point 2-6
floating point 2-3
IEEE
ASCII 2-3
floating point 2-6
with EBCDIC 2-3
J
Job Text packet 2-3
K
K-gain 2-6
L
Least Significant Bit (LSB) 2-6
M
MRX (Miniaturized Remote Extender) boxes 2-6
MRX K-gain 2-6
N
NRZI (Non-Return to Zero Inverted) recording format 1-1
number of samples
this trace 2-9
P
PE (Phase Encoded) recording format 1-1
R
Reel Header
400 byte Binary 2-4
Reel Identification header 2-1, 2-6
Rev 0 1-1
RSR 1-1, 2-6
RSR (Remote Seismic Recorder) boxes 2-6
S
sample interval
in microseconds 2-9
SEG Y
1975 1-1
Current Requirements 1-1
current requirements 1-1
differences with original 1-1
History 1-1
published 1-1
specification 1-1
SEG Y format 1-1
SEG Y Specification vs. I/O Specification 2-9
segyhdr.txt file 2-3
sensor scaling code 2-6
signal patterns 1-1
Society of Exploration Geophysicists 1-1
T
Text Block 2-2
Trace
Data Block 2-6
Identification code 2-8
Identification header 2-1, 2-3, 2-6
number within field record 2-8
sequence number within line 2-8
Trace Header
240 byte 2-9
Transcriber 2 1-1, 2-3, 2-6
V
VectorSeis 2-6, 2-7, 2-8, 2-11, 2-12
VRSR 2-7
VRSR LSB Setting 2-7
X
XTM information 2-3
Tel +1.281.552.3002
Fax +1.281.879.3626
www.i-o.com