head	1.2;
access;
symbols;
locks; strict;
comment	@# @;


1.2
date	2002.12.02.06.53.17;	author simon;	state Exp;
branches;
next	1.1;

1.1
date	2002.09.25.08.52.55;	author simon;	state Exp;
branches;
next	;


desc
@@


1.2
log
@*** empty log message ***
@
text
@Synoposis
---------

A raw AWS data file consists of a 6144 byte header and
variable lengthed data.


Header
------

0x0000: 254 (char[4]) station names, the fourth byte useless
0x03f8: (int)         modif: what it actually means no one knows
0x03fc: (int)         number of stations
0x0400: 255 (short)   number of elements per station
0x05fe: (short)       total number of elements
0x0600: 254 (short)   offset positions of elements (godamit 1-indexed)
0x07fc: (short)       mystery
0x07fe: (short)       mystery
0x0800: 2048 (char)   element codes
0x1000: 2048 (char)   dummy: what it actually does no one knows
0x1800: data


Data
----

The Data part is stacked with 1440 records representing data
for each minute, from 0001H to 2400H.  (Note the first record
represents 0001H but _NOT_ 0000H, which is equivalent to 2400H
of the previous day.)

Each record has length 

   record_length = ((total_number_of_elements + 255) / 256) * 512

It is not understood why this is so.  (A more intuitive approach would
be (total_number_of_elements * 2)

Each record consists of (total_number_of_elements) number of short's,
the order arranged as in the section "element codes" (0x0800) in the
header.


@


1.1
log
@*** empty log message ***
@
text
@d16 1
a16 1
0x0600: (short)       offset positions of elements (godamit 1-indexed)
d21 1
a21 1
0x1200: data
@

