obspy/obspy — pull request #610 by megies (2013-08-27 16:40:29+00:00)
Title: readSEGY and handling ambiguous SEG Y files

I've recently encountered a SEGY that had its data in IEEE floating point format, but still adhered to the Rev 0 binary header table codes.

Rev 0 is apparently agnostic to floating point format. When `readSEGY` is called, all files are assumed to be of SEG Y rev 1.0. This causes files marked 'floating point' in rev 0.0 to be read in as IBM format, when the true format is ambiguous.

This is perhaps a sensible default (and has served me correctly in the past), but for these edge cases, it would be very useful if there was a way to force the floating point format ("data sample format code") at the call to `segy.read(...)` in the same way it can be specified during a call to `segy.write(...)`.