BUFR data

[Tennessee Leeuwenburg]

Hi all,

I am trying to get BUFR working in GRADS, with a view to serving it out
with GDS. I have a file with QUIKSCAT data in it that I am using to
test, but will also want to try other kinds, and also most likely use
custom BUFR tables a little down the track.

The GRADS1.9 documentation hints at being able to do this, but does not
really explain it sufficiently for a Bear of Little Brain such as I.

I took my file and stuck it in /data
I asked our BUFR guru about BUFR tables. It needs Master table 0, centre
ID 160, subcentre ID 0, global version 6, local version 1. We guessed
that this table was the one in
/usr/loca/lib/grads/tables/B3L-160000-006001-D and as such we should be
able to serve it just fine.

I tried running

'bufrscan /usr/loca/lib/grads/tables/ /data/quickscat.bf, and saw some
header information that looked like this :
 >>> processing message 0



 >>> start of message
3 12 028  (sequence)

<<< end of message


 >>> processing message 0



 >>> start of message
3 12 028  (sequence)

<<< end of message


 >>> processing message 0



 >>> start of message
3 12 028  (sequence)

<<< end of message


 >>> processing message 0



 >>> start of message
3 12 028  (sequence)

<<< end of message


 >>> processing message 0


Running it to look at the binary data gave :
'bufrscan -d /usr/loca/lib/grads/tables/ /data/quickscat.bf'

Corrupt message: 334 extra bytes in data section
Corrupt message: 534 extra bytes in data section
Corrupt message: 670 extra bytes in data section
Corrupt message: 744 extra bytes in data section
Corrupt message: 930 extra bytes in data section
Corrupt message: 984 extra bytes in data section
Corrupt message: 1776 extra bytes in data section
Corrupt message: 2036 extra bytes in data section
Corrupt message: 2102 extra bytes in data section
Corrupt message: 2168 extra bytes in data section
Corrupt message: 2362 extra bytes in data section
Corrupt message: 2466 extra bytes in data section
Corrupt message: 2720 extra bytes in data section
Corrupt message: 2864 extra bytes in data section
Corrupt message: 2916 extra bytes in data section
Corrupt message: 2938 extra bytes in data section
Corrupt message: 2984 extra bytes in data section
Corrupt message: 3058 extra bytes in data section
Corrupt message: 3106 extra bytes in data section
Corrupt message: 4552 extra bytes in data section
Corrupt message: 2844 extra bytes in data section
Corrupt message: 2936 extra bytes in data section
Corrupt message: 2908 extra bytes in data section
Corrupt message: 2890 extra bytes in data section
Corrupt message: 3750 extra bytes in data section

This piece of documentation
(http://www.ncdc.noaa.gov/oa/model/publications/gds-and-grads-2004.pdf)
sketches over needing to write up a config file for the gds/dods
integration where BUFR is required, but I don't think it's necessary
when running bufrscan from the command prompt as I was doing.

Could some perhaps enlighten me as to what might be going on?

Cheers,
-Tennessee