Specifications

80 Appendix 2: Displaying Data Formats
// you have defined three channels, they will be numbered 0, 1
and
// 2. Channel data records can be in any order(i.e. 0,1,2 or
1,0,2)
// and you do not need to specify all channels on every line.
//
// If the channels already exist in the database, the channel
// parameters are ignored.
//
//--------------------------------------------------------------
//
// Example:
//
// Hex values are in <hex>, other binary values are in (value,
// value,...).
//
// The binary type of each value can be determined from the
record
// structures. For example, a channel data record
(1,5,4610.0,0.1,
// 42150) in binary would be:
//
// lChanNumber = 1; // long, 4 bytes
// lBinaryType = 5; // long, 4 bytes
// dFidStart = 4610.0; // double, 8 bytes
// dFidIncrement = 0.1; // double, 8 bytes
// lLength = 42150; // long, 4 bytes
//
// In this example, 42150 double (8-byte) values must
immediately
// follow the channel data record.
//
// A carriage-return line-feed <0D0A> is assumed at the end of
each
// comment header line for the purpose of calculating offsets.
//
// Channel names are null terminated in a 64 character field.
//
// byte
// offset data
comments
// ------ [---------------------------------------]-------------
// 0 [Oasis BINARY DATA ]
required
// 19 [ ]
// 21 [ This is a sample Oasis montaj binary data file which
]
// 69 [ contains two lines, 100 and 110, from flight 10 flown]
// 119 [ on January 19, 1995. The data includes X, Y, GPS ]
comments
// 170 [ time and 256-channel spectrometer sampled once a ]
// 222 [ second and in-phase (EM-I) and quadrature (EM-Q) ]
// 272 [ data sampled 10 times per second. ]
// 315 [ ]
// 317 [<1A> ]
end comments
// 318 [<01> ("Time",4,2,10,1) ]
Time channel
// 399 [<01> ("X",5,0,12,1) ]
X channel
// 480 [<01> ("Y",5,0,12,1) ]
Y channel
// 561 [<01> ("Mag",4,0,10,1) ]
Mag channel