[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20051124: EUMETSAT "GRIB" messages (cont.)



>From:  "Valentijn Venus" <address@hidden>
>Organization:  ITC
>Keywords: 200511171722.jAHHMk7s019022 McIDAS MAKNAV

Hi Valentijn,

>Temperatures are finally dropping here in Holland below 5 celsius. The
>first time this winter season. 

It has been exceedingly warm here in Colorado also.  Today (our
Thanksgiving holiday) we are expecting temperatures in the low 60s
[F].  I can sit out on the deck of my house at 8150 feet in a Tshirt!
It is days like this (it has been this way all week) that reinforce the
belief that global warming is real!!

>let me know what the status is of this Total Ozone/GRIB to AREA issue.
>Do you have enough info on the GRIB definition tables? Raul only needs
>it for his MSc research by the end of next week. But I can reorganise
>some of his work so you have some more air....

I just took a look at the files you sent me:

L-000-MSG1__-MPEF________-TOZ______-000001___-200511010845-__
L-000-MSG1__-MPEF________-TOZ______-PRO______-200511010845-__

They do _not_ look like GRIB files to me.  One very clear indication
that a contains a GRIB messate is the telltale beginning with GRIB and
ending with 7777.  Here is an example that illustrates this for a GRIB
message from model output:

od -c 2003061300_d1_f06.grb | less

0000000   G   R   I   B  \0   e 222 001  \0  \0 034 002   < 377 377 200
0000020   !   i  \0  \n 003 006  \r 006  \0 001  \0  \0  \0  \0  \0  \0
0000040 025 377  \0 002  \0  \0      \0 377 005  \0   n  \0 221 200   a
...
12542160 267   p 345   q 262   r 303   t 003   u 001   u 342   u 213   v
12542200   m  \0   7   7   7   7

Here is the same output from the first of the two files above:

od -c L-000-MSG1__-MPEF________-TOZ______-000001___-200511010845-__ | less

0000000  \0  \0 020 001  \0  \0  \0   g  \0  \0  \0  \0  \0   0 301   @
0000020 004  \0   @   L   -   0   0   0   -   M   S   G   1   _   _   -
0000040   M   P   E   F   _   _   _   _   _   _   _   _   -   T   O   Z
0000060   _   _   _   _   _   _   -   0   0   0   0   0   1   _   _   _
0000100   -   2   0   0   5   1   1   0   1   0   8   4   5   -   _   _
0000120 005  \0  \n   @   D   ? 001 357   A 314 200  \0  \r  \0  \0  \0
0000140  \0 001  \0 001  \0 001  \0  \0 034   :   / 001  \r  \r  \n   0
0000160   2   8  \r  \r  \n   I   U   L   A   0   1       E   U   M   G
0000200       0   1   0   8   3   0  \r  \r  \n   B   U   F   R  \0   :
0000220  \f 003  \0  \0 022  \0  \0 376  \0  \0 005   < 013  \0 005 013
...
1414160   &   L 231   2   d 311 223   &   L 231   2   d 311 223   &   L
1414200 231   2   d 311 223      \0   7   7   7   7  \r  \r  \n 003

If you look at the 9th line of the 'od' output, you will see that this
is a BUFR file.  I see nothing to indicate that there is a GRIB message
in the file.

Are you sure that this file is supposed to be in GRIB format?  Perhaps
you mistakely sent me a BUFR file instead?

Just so you know, McIDAS does not contain a BUFR decoder.  The original
thing you asked about, how to use GRIBFILER.CFG, was a McIDAS-XCD
configuration option to file (not decode) GRIB/BUFR files.  Decoding
the data inside a BUFR message is not something that McIDAS currently
does.

I will send an email to the McIDAS users email list to see if anyone
has a BUFR decoder that can be used to convert the data.

Cheers,

Tom
--
+-----------------------------------------------------------------------------+
* Tom Yoksas                                             UCAR Unidata Program *
* (303) 497-8642 (last resort)                                  P.O. Box 3000 *
* address@hidden                                   Boulder, CO 80307 *
* Unidata WWW Service                             http://www.unidata.ucar.edu/*
+-----------------------------------------------------------------------------+


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.