sps 3 0 n.
Skip this Video
Loading SlideShow in 5 Seconds..
SPS 3.0 PowerPoint Presentation

SPS 3.0

204 Views Download Presentation
Download Presentation

SPS 3.0

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. 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

  2. Current SPS v2.1 Point Record (R & S) Specifications

  3. Proposed SPS v3.0 Point Record (R & S) Specifications * The GPS Time / SEGD Timestamp is the time in seconds with microsecond precision since 06 January 1980 00: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

  5. Proposed SPS v3.0 Relation Record (X) Specifications

  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) 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).

  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.