User Tools

Site Tools


sudoc:su_data_format

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
sudoc:su_data_format [2020/08/06 20:43] johnsudoc:su_data_format [2021/03/30 21:32] (current) seisunix
Line 4: Line 4:
 Here will have an explanation of how SU data is, it's headers and how they are organized in a big SU file with more than one gather: Here will have an explanation of how SU data is, it's headers and how they are organized in a big SU file with more than one gather:
  
-=== SEG-Y Data Exchange Format, Rev. 0 and Rev. 1, with Seismic Un*x keys ===+=== SEG-Y Data Exchange Format, Rev. 0 and Rev. 1 and Rev. 2, with Seismic Un*x keys ===
  
 ^ SU key ^ Length ^ Bytes ^ Description ^ ^ SU key ^ Length ^ Bytes ^ Description ^
Line 113: Line 113:
 | - | 2 | 231-232 | "Source measurement unit: -1=other, 0=unknown, 1=Joule (J), 2=kilowatt (kW), 3=Pascal (Pa), 4=Bar (Bar), 4=Bar-meter (Bar-m), 5=Newton (N), 6=kilogram (kg)."| | - | 2 | 231-232 | "Source measurement unit: -1=other, 0=unknown, 1=Joule (J), 2=kilowatt (kW), 3=Pascal (Pa), 4=Bar (Bar), 4=Bar-meter (Bar-m), 5=Newton (N), 6=kilogram (kg)."|
 | - | 8 | 233-240 | Unassigned -- for optional information.| | - | 8 | 233-240 | Unassigned -- for optional information.|
 +
 +
 +=== SEG-Y Binary Headerb, Revision 2 (2017) ===
 +
 +The 400-byte Binary File Header record contains binary values relevant to the whole SEG-Y file. The values in the Binary File Header are defined as two-byte or four-byte, two's complement or unsigned integers, with the exception of IEEE double precision sample intervals in the optional SEG00001 trace header. Certain values in this header are crucial for the processing of the data in the file, particularly the sample interval, trace length, and format code. Revision 2.0 defines a few additional fields in the optional portion, as well as providing some clarification on the use of some existing entries.
 +
 +The SEG-Y binary header table starts counting byte locations at 3201 because SEG-Y documents consider the binary header an extension of the first 3200 byte textual file header. Therefore, that is the numbering in the first column. The second column is byte length. The third column starts counting byte locations in the binary header at 1 (one) for convenience when counting these bytes as a separate file. When byte locations are stated in the Description, column 3 references are in square brackets ([ ]).
 +
 +https://seg.org/Portals/0/SEG/News%20and%20Resources/Technical%20Standards/seg_y_rev2_0-mar2017.pdf SEG-Y revision 2.0 Data Exchange Format, SEG Technical Standards Committee, January 2017 
 +
 +Where not otherwise indicated, a value of zero indicates an unknown or unspecified value.
 +
 +^ Bytes ^ Length ^ Bytes ^ Description ^
 +|3201-3204 | 4 | 1-4  |  Job identification number.|
 +|3205-3208 | 4 | 5-8  | Line number. For 3-D poststack data, this will typically contain the in-line number.|
 +|3209-3212 | 4 | 9-12 | Reel number. |
 +|3213-3214 | 2 | 13-14| Number of data traces per ensemble. Mandatory for prestack data.|
 +|3215-3216 | 2 | 15-16| Number of auxiliary traces per ensemble. Mandatory for prestack data. |
 +|3217-3218 | 2 | 17-18 | Sample interval. Microseconds (µs) for time data, Hertz (Hz) for frequency data, meters (m) or feet (ft) for depth data. |
 +|3219-3220 | 2 | 19-20 | Sample interval of original field recording. Microseconds (µs) for time data, Hertz (Hz) for frequency data, meters (m) or feet (ft) for depth data.|
 +|3221-3222 | 2 | 21-22 | Number of samples per data trace. Note: The sample interval and number of samples in the Binary File Header should be for the primary set of seismic data traces in the file.|
 +|3223-3224 | 2  | 23-24 | Number of samples per data trace for original field recording.
 +|3225-3226 | 2. |25-26  | Data sample format code. Mandatory for all data. These formats are described in Appendix E.  1 = 4-byte IBM floating-point 2 = 4-byte, two's complement integer 3 = 2-byte, two's complement integer 4 = 4-byte fixed-point with gain (obsolete) 5 = 4-byte IEEE floating-point 6 = 8-byte IEEE floating-point 7 = 3-byte two’s complement integer 8 = 1-byte, two's complement integer 9 = 8-byte, two's complement integer 10 = 4-byte, unsigned integer 11 = 2-byte, unsigned integer 12 = 8-byte, unsigned integer 15 = 3-byte, unsigned integer 16 = 1-byte, unsigned integer |
 +|3227-3228 | 2 | 27-28 |Ensemble fold — The expected number of data traces per trace ensemble (e.g., the CMP fold).|
 +|3229-3230 | 2 | 29-30 |Trace sorting code (i.e., type of ensemble):–1 = Other (should be explained in a user Extended Textual File Header stanza)  0 = Unknown 1 = As recorded (no sorting) 2 = CDP ensemble 3 = Single fold continuous profile 4 = Horizontally stacked 5 = Common source point 6 = Common receiver point 7 = Common offset point 8 = Common mid-point 9 = Common conversion point |
 +|3231-3232 | 2 |31-32 | Vertical sum code: 1 = no sum,2 = two sum,…, N = M–1 sum (M = 2 to 32,767) |
 +|3233-3234 | 2 | 33-34 | Sweep frequency at start (Hz). |
 +|3235-3236 | 2  | 35-36 | Sweep frequency at end (Hz). |
 +|3237-3238  | 2 | 37-38 | Sweep length (ms). |
 +|3239-3240 | 2| 39-40 | Sweep type code: 1 = linear 2 = parabolic 3 = exponential 4 = other |
 +|3241-3242  | 2 | 41-42 | Trace number of sweep channel. |
 +|3243-3244 | 2 | 43-44 | Sweep trace taper length in milliseconds at start if tapered (the taper starts at zero time and is effective for this length). |
 +|3245-3246 | 2 | 45-46 | Sweep trace taper length in milliseconds at end (the ending taper starts at sweep length minus the taper length at end). |
 +|3247-3248 | 2 | 47-48 | Taper type: 1 = linear 2 = cosine squared 3 = other |
 +|3249-3250 | 2 | 49-50  |Correlated data traces: 1 = no 2 = yes |
 +|3251-3252 | 2 | 51-52 | Binary gain recovered: 1 = yes 2 = no |
 +|3253-3254 | 2 | 53-54 | Amplitude recovery method: 1 = none 2 = spherical divergence 3 = AGC 4 = other |
 +|3255-3256 | 2 | 55-56| Measurement system: If Location Data stanzas are included in the file, this entry would normally agree with the Location Data stanza. If there is a disagreement, the last Location Data stanza is the controlling authority. If units are mixed, e.g., meters on surface, feet in depth, then a Location Data stanza is mandatory. 1 = Meters 2 = Feet |
 +|3257-3258 | 2 | 57-58 | Impulse signal polarity 1 = Increase in pressure or upward geophone case movement gives negative number on trace. 2 = Increase in pressure or upward geophone case movement gives positive number on trace. |
 +|3259-3260 | 2 | 59-60 | Vibratory polarity code: Seismic signal lags pilot signal by:1 = 337.5° to 22.5° 2 = 22.5° to 67.5° 3 = 67.5° to 112.5° 4 = 112.5° to 157.5° 5 = 157.5° to 202.5° 6 = 202.5° to 247.5° 7 = 247.5° to 292.5° 8 = 292.5° to 337.5° |
 +|3261-3264 | 4 | 61-64 | Extended number of data traces per ensemble. If nonzero, this overrides the number of data traces per ensemble in bytes 3213–3214 [13-14]. |
 +|3265-3268 | 4 | 65-68  | Extended number of auxiliary traces per ensemble. If nonzero, this overrides the number of auxiliary traces per ensemble in bytes 3215–3216 [15-16]. |
 +|3269-3272 | 4 | 69-72  | Extended number of samples per data trace. If nonzero, this overrides the number of samples per data trace in bytes 3221–3222 [21-22]. |
 +|3273-3280 | 8 | 73-80| Extended sample interval, IEEE double precision (64-bit). If nonzero, this overrides the sample interval in bytes 3217–3218 [17-18] with the same units. |
 +|3281-3288 | 8 | 81-88 | Extended sample interval of original field recording, IEEE double precision (64-bit). If nonzero, this overrides the sample interval of original field recording in bytes 3219–3220 [19-20] with the same units. |
 +|3289-3292 | 4 | 89-92| Extended number of samples per data trace in original recording. If nonzero, this overrides the number of samples per data trace in original recording in bytes 3223–3224 [23-24]. |
 +|3293-3296 | 4 | 93-96 | Extended ensemble fold. If nonzero, this overrides ensemble fold in bytes ||3227–3228 [27-28]. |
 +|3297-3300 | 4| 97-100 | The integer constant 1690906010 (0102030416). This is used to allow unambiguous detection of the byte ordering to expect for this SEG-Y file. For example, if this field reads as 6730598510 (0403020116) then the bytes in every Binary File Header, Trace Header and Trace Data field must be reversed as they are read, i.e., converting the endian-ness of the fields. If it reads 3362099510 (0201040316) then consecutive pairs of bytes need to be swapped in every Binary File Header, Trace Header and Trace Data field. The byte ordering of all other portions (the Extended Textual Header and Data Trailer) of the SEG-Y file is not affected by this field. |
 +|3301-3500 | 200 | 101-300 | Unassigned |
 +|3501-3501 | 1 | 301-301 | Major SEG-Y Format Revision Number. This is an 8-bit unsigned value. Thus for SEG-Y Revision 2.0, as defined in this document, this will be recorded as 0216. This field is mandatory for all versions of SEG-Y, although a value of zero indicates “traditional” SEG-Y conforming to the 1975 standard.|
 +|3502-3502 | 1 | 302-302 | Minor SEG-Y Format Revision Number. This is an 8-bit unsigned value with a radix point between the first and second bytes. Thus for SEG-Y Revision 2.0, as defined in this document, this will be recorded as 0016. This field is mandatory for all versions of SEG-Y.|
 +|3503-3504 | 2 | 303-304 | Fixed length trace flag. A value of one indicates that all traces in this SEG-Y file are guaranteed to have the same sample interval, number of trace header blocks and trace samples, as specified in Binary File Header bytes 3217–3218 [17-18] or 3281–3288 [81-88], 3517–3518 [317-318], and 3221–3222 [21-22] or 3289–3292 [89-92]. A value of zero indicates that the length of the traces in the file may vary and the number of samples in bytes 115–116 of the Standard SEG-Y Trace Header and, if present, bytes 137–140 of SEG-Y Trace Header Extension 1 must be examined to determine the actual length of each trace. This field is mandatory for all versions of SEG-Y, although a value of zero indicates “traditional” SEGY conforming to the 1975 standard. Irrespective of this flag, it is strongly recommended that corect values for the number of samples per trace and sample interval appear in the appropriate trace Trace Header locations. |
 +|3505-3506 | 2 | 305-306 | Number of 3200-byte, Extended Textual File Header records following the Binary Header. If bytes 3521–3528 [321-328] are nonzero, that field overrides this one. A value of zero indicates there are no Extended Textual File Header records (i.e., this file has no Extended Textual File Header(s)). A value of -1 indicates that there are a variable number of Extended Textual File Header records and the end of the Extended Textual File Header is denoted by an ((SEG: EndText)) stanza in the final record (Section 6.2). A positive value indicates that there are exactly that many Extended Textual File Header records.Note that, although the exact number of Extended Textual File Header records may be a useful piece of information, it will not always be known at the time the Binary Header is written and it is not mandatory that a positive value be recorded here or in bytes 3521–3528 [321-328]. It is however recommended to record the number of records if possible as this makes reading more effective and supports direct access to traces on disk files. In the event that this number exceeds 32767, set this field to –1 and bytes 3521–3528 [321-328] to 3600+3200*(number of Extended Textual File Header records). Add a further 128 if a SEG-Y Tape Label is present.|
 +|3507-3510 | 4 | 307-310 | Maximum number of additional 240 byte trace headers. A value of zero indicates there are no additional 240 byte trace headers. The actual number for a given trace may be supplied in bytes 157–158 of SEG-Y Trace Header Extension 1. |
 +|3511-3512 | 2 | 311-312 | Time basis code: 1 = Local 2 = GMT (Greenwich Mean Time) 3 = Other, should be explained in a user defined stanza in the Extended Textual File Header 4 = UTC (Coordinated Universal Time) 5 = GPS (Global Positioning System Time) |
 +|3513-3520 | 8 | 313-320 | Number of traces in this file or stream. (64-bit unsigned integer value) If zero, all bytes in the file or stream are part of this SEG-Y dataset. |
 +|3521-3528 | 8 | 321-328 | Byte offset of first trace relative to start of file or stream if known, otherwise zero. (64-bit unsigned integer value) This byte count will include the initial 3600 bytes of the Textual and this Binary File Header plus the Extended Textual Header if present. When nonzero, this field overrides the byte offset implied by any nonnegative number of Extended Textual Header records present in bytes 3505–3506 [305-306]. |
 +|3529-3532| 4| 329-332 | Number of 3200-byte data trailer stanza records following the last trace (4 byte signed integer). A value of 0 indicates there are no trailer records. A value of -1 indicates an undefined number of trailer records (0 or more) following the data. It is, however, recommended to record |
 +|3533-3600| 68| 333-400 | Unassigned |
 +
 +
 +
sudoc/su_data_format.txt · Last modified: 2021/03/30 21:32 by seisunix