SEG-Y R2.0: SEG-Y Revision 2.0 Data Exchange Format SEG .
SEG-Y r2.0: SEG-Y revision 2.0 Data Exchange format1SEG Technical Standards Committee2January 20171 2017, Society of Exploration Geophysicists. All rights reserved.2Editors Rune Hagelund and Stewart A. Levin
SEG-Y r2.0January 2017Contents1.INTRODUCTION . 12.SUMMARY . 12.1.2.2.2.3.2.4.2.5.2.6.3.UNCHANGED ITEMS . 1CHANGES FROM REV 1 TO REV 2. 1CHANGES FROM REV 0 TO REV 1. 1NOTATION . 2CONTROLLING ORGANIZATION . 2ACKNOWLEDGMENTS . 2SEG-Y FILE STRUCTURE . 23.1.3.2.3.3.3.4.3.5.RECORDING MEDIUM. 2FILE STRUCTURE . 3NUMBER FORMATS . 3VARYING TRACE LENGTHS . 4COORDINATES . 44.TEXTUAL FILE HEADER . 45.BINARY FILE HEADER . 6Byte . 10Description . 106.EXTENDED TEXTUAL FILE HEADER . 116.1.6.2.6.3.7.DATA TRACES . 147.1.7.2.8.STRUCTURE OF EXTENDED TEXTUAL HEADER . 12ENDTEXT STANZA . 13STANZA EXAMPLES . 14TRACE HEADER . 14TRACE DATA. 27USER HEADER STANZA AND DATA TRAILER . 27APPENDIX A. WRITING SEG-Y DATA TO A DISK FILE. 28APPENDIX B. SEG-Y TAPE LABELS. 29APPENDIX C. BLOCKING OF SEG-Y FILES ON TAPE . 32APPENDIX D. EXTENDED TEXTUAL STANZAS. 33D-1. COORDINATE REFERENCE SYSTEM DEFINITION: INTERNATIONAL ASSOCIATION OF OIL ANDGAS PRODUCERS P1/11 . 33D-1.1 FORMAT OVERVIEW . 34D-1.2 LOGICAL FILE STRUCTURE. 35D-1.3 RECORD IDENTIFIERS . 36D-1.4 DATA TYPES USED IN THE FORMAT DEFINITION. 36D-1.5 RECORD DATA TYPES [DATATYPEREF] . 38D-1.6 COMMON HEADER: FILE IDENTIFICATION RECORD . 39D-1.7 COMMON HEADER: REFERENCE SYSTEM DEFINITIONS . 40D-1.8 UNIT REFERENCE SYSTEMS DEFINITION. 41D-1.9 COORDINATE REFERENCE SYSTEMS DEFINITION . 43ii
SEG-Y r2.0January 2017D-1.9.1 Coordinate Reference System Implicit Identification . 45D-1.9.2 Coordinate Reference System Explicit Definition . 46D-1.9.3 Coordinate Transformation Implicit Identification . 54D-1.9.4 Coordinate Transformation Explicit Definition . 55D-1.9.5 Example Point Conversion . 59D-1.10 COMMENT RECORDS . 59D-1.11 EXAMPLE CRS DEFINITION . 60D-1.12 DATA GEOGRAPHIC EXTENT USING OGP P1/11:. 62D-2. SEISMIC BIN GRID DEFINITION: IOGP P6/11. 65D-2.1 P6 HEADER: FILE CONTENT DEFINITIONS . 65D-2.2 BIN NODE POSITION DEFINITION USING OGP P6/11. 67D-2.3 COVERAGE PERIMETER DEFINITION USING OGP P6/11:. 69D-3. COORDINATE REFERENCE SYSTEM DEFINITION (DEPRECATED) . 76D-4. BIN GRID DEFINITION: DEPRECATED . 104D-5. DATA GEOGRAPHIC EXTENT & COVERAGE PERIMETER (DEPRECATED) . 108D-6. DATA SAMPLE MEASUREMENT UNIT. 114D-7. PROCESSING HISTORY . 114D-8. SOURCE TYPE/ORIENTATION . 115D-9. SOURCE MEASUREMENT UNIT . 116D-10. STANZA FOR TRACE HEADER MAPPING . 117D-11. USER DATA STANZA . 128APPENDIX E. DATA WORD FORMAT . 137APPENDIX F. EBCDIC AND ASCII CODES. 143APPENDIX G. REFERENCES . 146FIGURESFIGURE 1 BYTE STREAM STRUCTURE OF A SEG-Y FILE . 2FIGURE 2 STRUCTURE OF A USER HEADER OR DATA TRAILER CONTAINING N DATA BLOCKS. . 27FIGURE 3 BIN GRID DEFINITION (RIGHT-HANDED CASE) . 105FIGURE 4 VARIOUS DATA EXTENTS AND COVERAGE PERIMETERS FOR A SEISMIC SURVEY . 109FIGURE 5 STRUCTURE OF A USER DATA STANZA CONTAINING N DATA BLOCKS . 128TABLESTABLE 1 TEXTUAL FILE HEADER . 5TABLE 2 BINARY FILE HEADER . 6TABLE 3 STANDARD TRACE HEADER. 15TABLE 4 TRACE HEADER EXTENSION 1 . 24TABLE 5 PROPRIETARY TRACE HEADER EXTENSION . 27TABLE 6 SEG-Y TAPE LABEL . 29TABLE 7 STANZA FOR IMPLICIT IDENTIFICATION OF LOCATION DATA . 79TABLE 8 STANZA FOR EXPLICIT DEFINITION OF LOCATION DATA . 80TABLE 9 STANZA FOR IMPLICIT IDENTIFICATION OF LOCATION DATA TRANSFORMATION . 95TABLE 10 STANZA FOR EXPLICIT IDENTIFICATION OF LOCATION DATA TRANSFORMATION . 96TABLE 11 STANZA FOR BIN GRID DEFINITION . 105TABLE 12 STANZA FOR DATA GEOGRAPHIC EXTENT . 110TABLE 13 STANZA FOR COVERAGE PERIMETER. 111TABLE 14 STANZA FOR DATA SAMPLE MEASUREMENT UNIT . 114TABLE 15 STANZA FOR PROCESSING HISTORY . 114iii
SEG-Y r2.0January 2017TABLE 16 STANZA FOR SOURCE TYPE/ORIENTATION . 116TABLE 17 STANZA FOR SOURCE MEASUREMENT UNIT . 116TABLE 18 STANZA FOR TRACE HEADER MAPPING . 117TABLE 19 IBM 3270 CHAR SET REF . 143iv
SEG-Y r2.0January 2017 Allow arbitrarily large and small sampleintervalsSince the original SEG-Y Data ExchangeFormat (revision 0, - see Appendix G.References) was published in 1975 it hasachieved widespread usage within thegeophysical industry. The 2002 revision 1extended the standard to 3-D acquisitionand high capacity media, reducing, thoughfar from eliminating, the use of proprietaryvariations. Since the publication of SEG-Yrev 1, the nature of seismic data acquisition,processing and seismic hardware hascontinued to evolve and the SEG TechnicalStandards Committee undertook furtherrevision. In line with the 2011 SEG D rev 3.0standard, this revision both addressescurrent industry data exchange needs andprovides an explicit mechanism to supportfuture expansion with both proprietary andofficially-adopted extensions. The SEGTechnical Standards Committee stronglyencourages producers and users of SEG-Ydata sets to move to the revised standard inan expeditious fashion. Permit up to 264–1 traces per line and232–1 traces per ensemble Support additional data sample formats,including IEEE double precision (64 bit) Support little-endian and pair-wise byteswapping to improve I/O performance. Support microsecond accuracy in timeand date stamps Support additional precision oncoordinates, depths and elevations(especially useful for lat/long and UTMcoordinates) and more options forcoordinate reference systemspecification Require Extended Textual File Headerstanzas to begin at 3200-byteboundaries and removed 40 80-byte linerestriction Allow stanzas to appear after the lastdata traceUsers of this standard are cautioned thatSEG-Y was not explicitly designed for useas a field recording format. The SEG D orSEG 2 formats are recommended for thispurpose. Provide flexible trace header mappingoptions via Extended Textual FileHeaders. Because of this ability, weremove almost all “mandatory” and“highly recommended” header entrydesignations2. Summary Allow XML-based Extended Textual FileHeader and Trailer stanzas for ease ofmachine encoding and decoding Include depth, velocity, EM, gravity androtational sensor data1. Introduction2.1. Unchanged Items EBCDIC encoding allowed for text The size of the original 3200-byteTextual File Header, 400-byte BinaryFile Header and initial 240-byte TraceHeader2.3. Changes from rev 0 to rev 1 A SEG-Y file may be written to anymedium that is resolvable to a stream ofvariable length records The data word formats are expanded toinclude four-byte, IEEE floating-pointand one-byte integer data words A small number of additional fields in the400-byte Binary File Header and the2.2. Changes from rev 1 to rev 2 Provide for up to 65535 additional 240byte trace headers with bytes 233-240of each trace header reserved for traceheader names Allow up to 232 –1 samples per trace1
SEG-Y r2.0Optional128 BinaryFileHeaderJanuary 2017st1 3200byteExtendedTextualFileHeader(Optional)thN 3200byteExtendedTextualFileHeader(Optional)st1 or more 1240 byte DataTrace 1TraceHeaders1 or more240 byteTrace MHeadersthMDataData TrailerTrace 1 or more3200 byterecords(Optional)Figure 1 Byte stream structure of a SEG-Y file with N Extended Textual File Header records and M tracesrecords240-byte Trace Header are defined andthe use of some existing entries isclarified Phone: (918) 497-5500Fax: (918) 497-5557Internet site: www.seg.orgAn Extended Textual File Headerconsisting of additional 3200-byteTextual File Header blocks is introduced The data in the Extended Textual FileHeader uses a stanza layout andstandard stanzas are defined Trace identification is expanded Engineering conversions are introduced The Textual File Header and theExtended Textual File Header can beencoded as EBCDIC or ASCIIcharacters2.6. AcknowledgmentsThe SEG Technical Standards Committeewould like to acknowledge the time andeffort put forth by a great many individualsand organizations.3. SEG-Y File StructureThe SEG-Y format is intended to beindependent of the actual medium on whichit is recorded. For this standard, the termsfile and data set are synonymous. Bothterms are a collection of logically relateddata traces or ensembles of traces and theassociated ancillary data.2.4. NotationThe term CDP (common depth point) asused in this document is used as a synonymfor the term CMP (common midpoint).3.1. Recording MediumA SEG-Y file may be written to anysequential medium. Whatever medium isused, the data must be resolvable to astream of variable length logical records.This includes high capacity tape devices,although with these it is desirable to usesome kind of blocking and/or logicalencapsulation such as SEG RODE (Boothet al., 1997), to use the tape more efficientlyand possibly to allow the recording ofassociated metadata. Obviously, whenseismic data are being exchanged in SEG-Yformat, the medium and any blocking and/orencapsulation scheme used must beacceptable to both the provider andrecipient of the data.2.5. Controlling OrganizationSEG-Y is administered by the SEGTechnical Standards Committee. Anyquestions, corrections or problemsencountered in the format should beaddressed to:Society of Exploration GeophysicistP.O. Box 702740Tulsa, Ok 74170-2740Attention: SEG Technical StandardsCommittee2
SEG-Y r2.0January 2017One important class of media on whichSEG-Y data are exchanged is the bytestream without any record structure. It iscommon practice to write SEG-Y data todisk, including USB sticks, CD and DVDROM, or streamed through a network fordata distribution. Certain rules have to befollowed for this to work correctly. AppendixA defines how SEG-Y data should bewritten as a byte stream.Trace Header Extensions. The format ofTrace Header Extensions is described fullyin section 7.3.3. Number FormatsIn earlier SEG-Y standards, all binaryvalues were defined as using “big-endian”byte ordering. This means that, within thebytes that make up a number, the mostsignificant byte (containing the sign bit) iswritten closest to the beginning of the fileand the least significant byte is writtenclosest to the end of the file. With SEG-Yrev 2, “little-endian” and “pairwise byteswapped” byte ordering are allowed,primarily for I/O performance. This isindependent of the medium to which aparticular SEG-Y file is written (i.e. the byteordering is no different if the file is written totape on a mainframe or to disk on a PC).These alternate byte orders are identified byexamining bytes 3297-3300 in the BinaryFile Header and apply only to the BinaryFile Header, Trace Headers, and Trace3Samples .In order to make SEG-Y consistent with theSEG D Rev 3.0 standard, Appendix Bdefines a tape label for SEG-Y tapes, usinga format based on the RP66 Storage UnitLabel. Labels are not mandatory for SEGY, but their use is highly desirable inenvironments such as robotic tape librariesand large scale processing centers.Appendix C defines a simple blockingscheme for SEG-Y data to allow moreefficient use of high-capacity tape media.This is based on the scheme defined in theSEG D Rev 3.0 standard.3.2. File StructureAll values in the Binary File Header and theSEG defined Trace Headers are to betreated as two's complement integers,whether two, four or eight bytes long, withthe exception of the new 8-character TraceHeader Extension name, an optional IEEEdouble precision sample rate, and fields thatcannot be negative such as the number ofsamples per trace. To aid in data recognition and recovery, a value of zero in anySEG or user assigned fields of theseheaders should indicate an unknown orunspecified value unless explicitly statedotherwise.Figure 1 illustrates the structure of a SEG-Yfile. Following the optional SEG-Y TapeLabel, the next 3600 bytes of the file are theTextual File Header and the Binary FileHeader written as a concatenation of a3200-byte record and a 400-byte record.This is optionally followed by ExtendedTextual File Header(s), which consists ofzero or more 3200-byte Extended TextualFile Header records. The remainder of theSEG-Y file contains a variable number ofData Trace records that are each precededby a 240-byte Standard Trace Header andzero or more 240-byte Trace HeaderExtensions. The Trace Header Extensionmechanism is the only structural changeintroduced in this revision and while notstrictly backward compatible with prior SEGY formats, it has been carefully designed tohave minimal impact on existing SEG-Yreader software. It should be simple forexisting software to be modified to detectthe presence of the optional trace headersand either process or ignore any ProprietaryTrace Data sample values are eitherintegers or floating-point numbers. Signedintegers are in two’s complement format.SEG-Y revision 2 adds unsigned integers,3Textual Headers and Data Trailer recordsare always assumed to be text and so byteordering is left untouched.3
SEG-Y r2.0January 201724 and 64 bit integ
In order to make SEG-Y consistent with the SEG D Rev 3.0 standard, Appendix B defines a tape label for SEG-Y tapes, using a format based on the RP66 Storage Unit Label. Labels are not mandatory for SEG-Y, but their use is highly desirable in environments such as ro
OF GROUPE RENAULT SALES BY 2022 Width Price CMF-A CMF-B LS CMF-B HS A SEG. B SEG. C SEG. D SEG. CMF-CD CMF-EV CMF: Common Module Family LS: Low specifications HS: High specifications 2016 2022 New EV 0% 25% 50% 75% 100% 2019 2021 Sales on CMF platforms New B
2 Trimark Seg Funds Annual Report December 31, 2018 Trimark Interest Seg Fund Selected Seg Fund information Fund information as at: December 31, 2018 First offered for sale: June 23, 1998 Size: 567,441 Net asset value: 10.27 per unit Issued by: BMO Life Assurance Company Managed by: Invesco Canada Ltd. Performance: 1-year 3-year 5-year 10-year 0.45% 0.17% 0.12% 0.08%
Refer to the image below for loading 3D SEG-Y files into GVERSE Geophysics. The source of the XY coordinates for the data is of primary concern. Follow the workflow on the left side of the image if the XY coordinates are in the SEG-Y file. Follow the workflow on the right side of the image if the XY coordinates are manually entered.
Access Gateway topic in the Deploying and Configuring VMware Unified Access Gateway guide. Configuring for High Availability and Disaster Recovery SEG can be configured in high availability and disaster recovery environments with both clustering and non-clustering server configurations. The high availability and disaster recovery
VMware AirWatch SEG Administration Guide, available on docs.vmware.com. Beginning with the 1907 release, SEG Classic is no longer available on new deployments. Beginning with Unified Access Gateway 3.6 the SEGv2 image is included in the UAG appliance.
building has a basement, the basement floor is the lowest floor. Whether there is a basement or not, the cost of foundations should be included in all buildings. These costs, converted to a Segregated Cost basis, are in Sections SEG 1 through SEG 6 for the various types of construction and building occupancy and they include an
SERIE TSP650 Impresoras de recibos de gama básica, bajo coste y alta velocidad 150 mm/seg con corte manual o automático 16-17 SERIE TSP700II Impresora de recibos multifunción, 250 mm/seg, apta para la impresión de etiquetas, códigos de barras y tiquetes
Keywords with the- Agile software development, Scrum I. INTRODUCTION Scrum [16, 29] is the most often used [6, 30, 31] agile [10] software development methodology among teams that utilize an agile methodology. A large-scale survey [31] deployed in the software engineering industry from June/July 2008 received 3061 respondents from 80 different countries. For the question “Which Agile .
