Error handling, warnings, flagging, etc.

[EvanBianco]

Have ways of smart handling of inconsistent information:

potential things to watch for / flag:

• Header information missing
• Header information in wrong locations
• coordinate conversion scale factor does not match integer in x and y coordinates...
• reported sample rate or record length does not match actual, etc.

[EvanBianco]

Write tests to check for equivalency and consistency between meta-data in the trace header fields and (where appropriate) for other meta data in the file.

• For instance, source and geophone coordinates should be the same for stacked 3D data.
• Tests for geographical sensibility (off by a factor of 10 in coordinate scale conversion)
• Test that number of samples matches the value stated in the header.
• Throw warnings if CDP number, trace seq number, shotpoint number, etc., are not in their standard byte locations.