New versions of SEG-D

SEG Annual Meeting – Denver Tuesday Oct 28, 2014 Rune Hagelund, DAECO

SEG-D Rev 3.0 September 2014

  Final version of 3.0 Further development will be 3.1

SEG-D Rev 3.0 September 2014 - Changes

 New channel types (ChannelSet byte 4) – 0x9A Source excitation – 0x9B Source valve – 0x9C Source overload  New physical units supported for samples (ChannelSet byte 62) – 0x14 Millimeter – 0x15 Meter

SEG-D Rev 3.0 September 2014 - Changes

 Updated measurements to support Energistics Unit of Measure v1.0

– Some units removed and added – Note: % removed, use EUC – Several new measurement types added to http://www.seg.org/web/technical standards-committee/wiki/ /wiki/Main/SegMeasurements

SEG-D Rev 3.0 September 2014 - Changes

 New producers – Seismic Instruments, Inc (code 54) – TGS (code 55) – Hewlett Packard (code 56) – Modern Seismic Technology, LLC (code 57)

SEG-D Rev 3.0 September 2014 - Changes

+ some clarifications of usage  For more details please refer to release letter

SEG-D Rev 3.1

   New version of SEG-D New functionality: Little endian samples and new CRS definition format Not binary compatible with Rev 3.0

– Most headers are identical  NOTE: Only samples can be little-endian, all headers are still big-endian

SEG-D Rev 3.1 - Changes

 Little endian samples – 9036 - Little endian 24 bit 2's complement integer – 9038 - Little endian 32 bit 2's complement integer – 9058 - Little endian 32 bit IEEE – 9080 - Little endian 64 bit IEEE  Other formats not supported as they do not match internal computer data formats – Would cause additional implementation and test cost for no benefit

SEG-D Rev 3.1 - Changes

 Added support for new P1/11 Coordinate Reference System definition format – Old 3.0 CRS format deprecated but still supported  Shared CRS format with all OGP P-formats (and the coming updated SPS and SEG-Y)  OGP is working on a format update so Appendix D1 will be changed accordingly prior to 3.1 publication

SEG-D Rev 3.1 Questions

 Should more be added?

 Can we go ahead and publish this version?