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:
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, F; Bowes, A.W.; LaFon, S.K.; Musser, J.A. (Saudi Aramco) September, 2011
Current SPS v2.1 Point Record (R & S) Specifications ItemDefinition of fieldColsFormatMin. to maxDefaultJust.units 1Record identification1-1A1“S” or “R”Nonen/a 2Line name2-11F to NoneRight 3Point number12-21F to NoneRight Blank 4Point index24-24I11 to 91Right 5Point code25-26A2A#NoneLeft 6Static correction27-30I4-999 to 9999BlankRightms 7Point depth31-34F4.10 to 99.90RightHeader defined 8Seismic datum35-38I4-999 to 99990RightHeader defined 9Uphole time39-40I20 to 99BlankRightms 10Water depth41-46F6.10 to BlankRightHeader defined 11Map grid easting47-55F9.1None Right 12Map grid northing56-65F10.1None Right 13Surface elevation66-71F to NoneRightHeader defined 14Day of year72-74I31 to 999NoneRight 15Time “hhmmss”75-803I to Nonen/a
Proposed SPS v3.0 Point Record (R & S) Specifications ItemDefinition of fieldColsFormatMin. to maxDefaultJust.units 1record identification1-1A1“S” or “R”Nonen/a 2line name2-17F to NoneRight 3point number18-33F to NoneRight Blank 4point index36-38I31 to 9991Right 5point code39-41A3A##NoneLeft 6point depth42-49F8.20 to RightHeader defined 7tide height50-54F to RightHeader defined 8water depth55-62F8.20 to BlankRightHeader defined 9map grid easting63-72F10.2None Right 10map grid northing73-83F11.2None Right 11surface elevation84-91F to NoneRightHeader defined 12day of year (Julian day)92-94I31 to 999NoneRight 13time “hhmmss” I to Nonen/a 14GPS time* (SEGD Timestamp) F to NoneRightSeconds * 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.
Current SPS v2.1 Relation Record (X) Specifications ItemDefinition of fieldColsFormatMin. to maxDefaultJust. 1Record identification1-1A1“X”Nonen/a 2Field tape number2-73A2freeNoneright 3Field record number8-15I80 to None right 4Field record increment16-16I11 to 91 right 5Instrument code17-17A11 to 91 right 6Line name18-27F to None right 7Point number28-37F to None right 8Point index38-38F4.1I11 to 91 right 9From channel39-43I51 to 99999None right 10To channel44-48I51 to 99999None right 11Channel increment49-49I11 to 9Blank1 right 12Line name50-59F to None right 13From receiver60-69F to None right 14To receiver70-79F to None right 15Receiver index80-80I11 to 91 right
Proposed SPS v3.0 Relation Record (X) Specifications ItemDefinition of fieldColsFormatMin. to maxDefaultJust. 1record identification1-1A1“X”Nonen/a 2field tape number2-136A2freeNoneright 3field record number14-21I80 to None right 4field record increment22-23I21 to 991 right 5instrument code24-24A11 to 91 right 6source line name25-40F to None right 7source point number41-56F to None right 8source point index57-59I31 to 9991 right 9from channel number60-66I71 to None right 10to channel number67-73I71 to None right 11channel number increment74-76I31 to 9991 right 12receiver line name77-92F to None right 13from receiver point number93-108F to None right 14to receiver point number F to None right 15receiver point index I31 to 9991 right
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) or – It may be a modification of the existing Relational (X) file with added records defining the daughter data Additional 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).
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.