Presentation on theme: "SPS 3.0 Update of the Progress of the SPS Subgroup of the SEG Technical Standards Committee Cignoli, J.E.; Green, P.C.; Hubbell, S.E.; Moffitt, R.G.; Siddiquee,"— Presentation transcript:
1 SPS 3.0Update of the Progress of the SPS Subgroup of the SEG Technical Standards CommitteeCignoli, J.E.; Green, P.C.; Hubbell, S.E.; Moffitt, R.G.; Siddiquee, F; Bowes, A.W.; LaFon, S.K.; Musser, J.A. (Saudi Aramco)September, 2011
2 Current SPS v2.1 Point Record (R & S) Specifications ItemDefinition of fieldColsFormatMin. to maxDefaultJust.units1Record identification1-1A1“S” or “R”Nonen/a2Line name2-11F10.2toRight3Point number12-21+22-23Blank4Point index24-24I11 to 95Point code25-26A2A#Left6Static correction27-30I4-999 to 9999ms7Point depth31-34F4.10 to 99.9Header defined8Seismic datum35-389Uphole time39-40I20 to 9910Water depth41-46F6.10 to11Map grid easting47-55F9.112Map grid northing56-65F10.113Surface elevation66-71to14Day of year72-74I31 to 99915Time “hhmmss”75-803I2to
3 Proposed SPS v3.0 Point Record (R & S) Specifications ItemDefinition of fieldColsFormatMin. to maxDefaultJust.units1record identification1-1A1“S” or “R”Nonen/a2line name2-17F16.5toRight3point number18-33+34-35Blank4point index36-38I31 to 9995point code39-41A3A##Left6point depth42-49F8.20 toHeader defined7tide height50-54F5.2-9.99 to 99.998water depth55-629map grid easting63-72F10.210map grid northing73-83F11.211surface elevation84-91to12day of year (Julian day)92-9413time “hhmmss”95-1003I2to14GPS time* (SEGD Timestamp)F21.6toSeconds* The GPS Time / SEGD Timestamp is the time in seconds with microsecond precision since 06 January :00:00 (GPS epoch). Dates and times before 06 January 1980 will have a negative GPS Time value.
4 Current SPS v2.1 Relation Record (X) Specifications ItemDefinition of fieldColsFormatMin. to maxDefaultJust.1Record identification1-1A1“X”Nonen/a2Field tape number2-73A2freeright3Field record number8-15I80 to4Field record increment16-16I11 to 95Instrument code17-176Line name18-27F10.2to7Point number28-37to8Point index38-38F4.1I19From channel39-43I51 to 9999910To channel44-4811Channel increment49-49Blank11250-5913From receiver60-6914To receiver70-7915Receiver index80-80
5 Proposed SPS v3.0 Relation Record (X) Specifications ItemDefinition of fieldColsFormatMin. to maxDefaultJust.1record identification1-1A1“X”Nonen/a2field tape number2-136A2freeright3field record number14-21I80 to4field record increment22-23I21 to 995instrument code24-241 to 96source line name25-40F16.5to7source point number41-568source point index57-59I31 to 9999from channel number60-66I71 to10to channel number67-7311channel number increment74-7612receiver line name77-9213from receiver point number93-10814to receiver point number15receiver point index
6 SPS 3.0 Considerations and Features SPS v3.0 should be fully compatible with SEGD v3.0.Proposed SPS v3.0 records all require less than 150 columns (as recommended by OGP) and still have room for expansion before that limit is reached.SEGD supports Short Mother Records (SMR), in which multiple source events are recorded in a single record, resulting in a many-to-one relation of source point records to an ffid on tape.This will require further generalization of the relational (X) records to allow generation of daughter records with unique ffids from the mother record.This may be a new record or file type (similar to X) orIt may be a modification of the existing Relational (X) file with added records defining the daughter dataAdditional input relating to handling SMRs and subsequent separated daughter records is solicited from industry participants. The current recommendations are Aramco-centric mainly because we have received little feedback from seismic industry service providers when solicited.GPS time with microsecond fidelity is added to allow accurate source separation in high-productivity acquisition (such as ISS).
7 SPS 3.0 Considerations and Features (cont.) Comma delimiting of record entries is being considered to improve robustness of the formats. [Comma-Space] delimiting is also being considered to help keep the records relatively easy to scan by eye.OBC data acquisition easily fits within the proposed SPS 3.0 definitions.Current and Future High-Channel Count crews require the SEGY format to increase the current channel limitation (32,767) to be compatible with SEGD (16,777,215).Consideration should be given in future versions of all formats (SPS, SEGD, SEGY, etc.) for robust handling of Common Receiver Gather data, such as acquired by nodes and other wireless systems.For SPS files, this can be achieved by a reversal of the roles of S and R stations within the X files.Further development of SPS Header Blocks and Templates for specific acquisition technologies and schemes (such as, surface sources, explosives, airgun arrays, buried receivers, seabed receivers, etc.) are under development.Documentation will proceed upon approval of proposed formats.