Cold In The Beaufort Sea

Good Lord the problems I have with this one!  This data is from Westerngeco (my old employer) thanks to the USGS that was shot back in 1978.  Why can't I find data that is somewhat recent and that has data that's accurate.  Anyhow, here's what the data looks like. Now based on the "MetaData" file, here are the details of the survey:

ID	W-19-78-AR
Also Known As	00019
Abstract	WesternGeco. Geophysical data (navigation, seismic) of field activity W-19-78-AR in Beaufort Sea Streamer from 01/01/1978 to 02/13/1978
Organization	WesternGeco
Activity Type	Geophysical
Area of Operation	Beaufort Sea Streamer, Arctic Ocean
Bounding Coordinates	70.65183 -149.68971 -145.53813 70.17886
Dates	01/01/1978 (JD 001) to 02/13/1978 (JD 044)
Analog Materials	No analog holdings.
Information Specialist	Jon Childs
Equipment Used	navigation seismic
Notes	Description of Survey Area 00019: Beaufort Sea Streamer 1978 Date of Survey Sept 1978 Tape Version Identifier SEG-P1 Client Name WesternGeco Multiclient Coordinate Location Vessel Locations Spheroid Definition-Survey Clarke 1866 6378206.400 294.978698 Spheroid Def. - Post Plot Clarke 1866 6378206.400 294.978698 Geodetic Datum - Survey NAD 27 Geodetic Datum - Post Plot NAD 27 Datum Shifts Projection Type Transverse Mercator Grid System UTM Zone 6 Grid Units Meters Central Meridian 147 0 0.000W Grid Origin 0 0 0.000N147 0 0.000W Grid Coordinates at Origin 500000.00E 0.00N Scale Factor 0.9996000000 Scale Factor Defined at 0 0 0.000N147 0 0.000W

Now here are the datatypes available:

Navigation

• ArcInfo E00 files (thankfully)
• Edited shotpoint data (looks like reliable lat,long,x,y info every 10 shotpoints but you never know.  The data look funny though)
• A kmz file for you GoogleEarth people

Seismic

• 2D Stack Lines
• 2D Migration Lines

Alrighty now let's look at things....

Let's look at a migration EBCDIC header:

C01 CLIENT WESTERNGEC COMPANY CREW NO C02 LINE WB-737 AREA 19 C03 REEL NO 782124 PROSPECT BEAUFORT SEA 1978 OBSERVER C04 INSTRUMENT: MFG MODEL SERIAL NO C05 DATA TRACES/RECORD 1 AUXILIARY TRACES/RECORD 0 CDP FOLD C06 SAMPLE INTERVAL 4 SAMPLES/TRACE 1500 BITS/IN BYTES/SAMPLE 4 C07 RECORDING FORMAT FORMAT THIS REEL MEASUREMENT SYSTEM C08 SAMPLE CODE: FLOATING PT FIXED PT FIXED PT-GAIN CORRELATED C09 C10 C11 C12 C13 C14 C15 C16 C17 C18 C19 FIELD FILE SEQUENCE IN BYTES 21-24 C20 C CLIENT WGC C LINE WB-737 S.P. 1400 - 100 C AREA O-ALK C MAX REF TIME(MS) 6000 SAMPLING INTERVAL 4 REEL SEQUENCE NUMBER 1 TYPE FL C DATA TRACE NO.(MAX) 24 UNITS OF DISTANCE FEET STACK RMS 2000 C TIME VALUE MULTIPLIER 1 REPLACEMENT VELOCITY DATUM ELEVATION C TRACE HEADER LENGTH 100 CODE RELEASE DATE/VERSION / C IDENT TYPE WGC TRACE HEADER START TIME C EARLIEST TIME OF FIRST SAMPLE -200 C CDF ACCEPTANCE RADIUS C STATION RANGE FIRST 1 LAST 99999 INCREMENT 1 C GS VELOCITY 5000 100 5000 600 6000 1600 7500 2200 9000 3000 9700 C GS VELOCITY 5000 12000 C USER PROCESSING COMMENTS C Z5419VE8V 14- 6-89 15.13.49 HA91 C RESIDUAL AMPLITUDE COMPENSATION C Z575AVA2S 14- 6-89 15.46.08 HA91 C CASCADED FINITE DIFFERENCE MIGRATION C END OF USER PROCESSING COMMENTS C MAP PROJECTION PARAMETERS

I get red in the face asking my self who put this together. If you have enough brains to process seismic data why don't you have enough brains to put together a 1/2 decent EBCDIC header. I mean . . . I'll go on to other things.  I mean, why do they repeat everything?  Hardly any byte locations, no loading info, no projection information, no grid.  I guess how WGC gets you on phone paying for more gobbledygook.  I mean - cell size?  lat/longs or X/Ys?  Sorry.

When we take a look at the trace headers next which have their troubles.  Instead of putting lat/long some sort of XY in 73-76/77-80 or 81-84/85-88 they put "something" in 81-84/85-88 as an X/Y.  Here's what I have for line WB-737 sp 1400:

Sesimic File:
77 1705911 25580523

Navigation File:
70.27954 -146.46993 519965  7796959

Then there's a number in there 2949120 (181-185) and 3473408 (189-192).  Of source there's no description of what those number are is.

Maybe I might be able to figure out how to create a proper coordinate file to match things up.  Let me work on it.