[Met_help] [rt.rap.ucar.edu #72735] History for Does the MET support for ECMWF grib data?

Mon Jul 27 09:37:19 MDT 2015

----------------------------------------------------------------
  Initial Request
----------------------------------------------------------------

Dear Sir:

        Does the MET support for ECMWF grib data?  The grib table of ECMWF are different with NCEP grib data. When i use pcp_combine to convert EC grib file to netcdf format, it could not found the APCP variable. The grib code is 228 for EC grib data. How can i solve this problem? 
DO i need to modified the code?

        Thanks!

Kefeng

*******************************************
kefeng at nju.edu.cn
朱科锋
南京大学大气科学学院
邮编:210093
南京市汉口路22号
中国江苏
*******************************************

----------------------------------------------------------------
  Complete Ticket History
----------------------------------------------------------------

Subject: Does the MET support for ECMWF grib data?
From: Julie Prestopnik
Time: Fri Jul 24 10:16:36 2015

met-5.0 and earlier versions do not include support for the ECMWF
usage of
GRIB.  In previous versions of MET, the GRIB tables were harded-coded,
but
the code is now reading them from a flat-file at runtime.

In met-5.0, it's reading it from the installed met-5.0 directory
"share/met/table_files/nceptab_flat.txt".

And in METv4.1, the flat file can be found here:
   METv4.1/data/table_files/nceptab_flat.txt

The difference really is just in the GRIB code abbreviations and
units.  I
would expect that MET can read ECMWF GRIB1 files, but that
it just uses the wrong names for the variables.

If you'd like to change MET's behavior, you could edit that flat file
to
use whichever abbreviations and units you'd like.  The next time
you run the MET tools, it'll just read in the updated strings and use
them.

It would be preferable to support ECMWF GRIB data without putting this
onus
on the user, but we don't currently get any ECMWF data.  So it's
difficult
to support.

I hope this helps.

Julie

On Fri, Jul 24, 2015 at 4:15 AM, kefeng at nju.edu.cn via RT
<met_help at ucar.edu
> wrote:

>
> Fri Jul 24 04:15:52 2015: Request 72735 was acted upon.
> Transaction: Ticket created by kefeng at nju.edu.cn
>        Queue: met_help
>      Subject: Does the MET support for ECMWF grib data?
>        Owner: Nobody
>   Requestors: kefeng at nju.edu.cn
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=72735 >
>
>
> Dear Sir:
>
>         Does the MET support for ECMWF grib data?  The grib table of
ECMWF
> are different with NCEP grib data. When i use pcp_combine to convert
EC
> grib file to netcdf format, it could not found the APCP variable.
The grib
> code is 228 for EC grib data. How can i solve this problem?
> DO i need to modified the code?
>
>         Thanks!
>
>
> Kefeng
>
>
>
>
> *******************************************
> kefeng at nju.edu.cn
> 朱科锋
> 南京大学大气科学学院
> 邮编:210093
> 南京市汉口路22号
> 中国江苏
> *******************************************
>

--
Julie Prestopnik
National Center for Atmospheric Research
Research Applications Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu

------------------------------------------------
Subject: Does the MET support for ECMWF grib data?
From: kefeng at nju.edu.cn
Time: Fri Jul 24 19:01:41 2015

      Problems solved.

      Many thanks!  Julie

 Kefeng

kefeng at nju.edu.cn

From: Julie Prestopnik via RT
Date: 2015-07-25 00:16
To: kefeng
Subject: Re: [rt.rap.ucar.edu #72735] Does the MET support for ECMWF
grib data?
met-5.0 and earlier versions do not include support for the ECMWF
usage of
GRIB.  In previous versions of MET, the GRIB tables were harded-coded,
but
the code is now reading them from a flat-file at runtime.

In met-5.0, it's reading it from the installed met-5.0 directory
"share/met/table_files/nceptab_flat.txt".

And in METv4.1, the flat file can be found here:
   METv4.1/data/table_files/nceptab_flat.txt

The difference really is just in the GRIB code abbreviations and
units.  I
would expect that MET can read ECMWF GRIB1 files, but that
it just uses the wrong names for the variables.

If you'd like to change MET's behavior, you could edit that flat file
to
use whichever abbreviations and units you'd like.  The next time
you run the MET tools, it'll just read in the updated strings and use
them.

It would be preferable to support ECMWF GRIB data without putting this
onus
on the user, but we don't currently get any ECMWF data.  So it's
difficult
to support.

I hope this helps.

Julie

On Fri, Jul 24, 2015 at 4:15 AM, kefeng at nju.edu.cn via RT
<met_help at ucar.edu
> wrote:

>
> Fri Jul 24 04:15:52 2015: Request 72735 was acted upon.
> Transaction: Ticket created by kefeng at nju.edu.cn
>        Queue: met_help
>      Subject: Does the MET support for ECMWF grib data?
>        Owner: Nobody
>   Requestors: kefeng at nju.edu.cn
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=72735 >
>
>
> Dear Sir:
>
>         Does the MET support for ECMWF grib data?  The grib table of
ECMWF
> are different with NCEP grib data. When i use pcp_combine to convert
EC
> grib file to netcdf format, it could not found the APCP variable.
The grib
> code is 228 for EC grib data. How can i solve this problem?
> DO i need to modified the code?
>
>         Thanks!
>
>
> Kefeng
>
>
>
>
> *******************************************
> kefeng at nju.edu.cn
> 朱科锋
> 南京大学大气科学学院
> 邮编:210093
> 南京市汉口路22号
> 中国江苏
> *******************************************
>

--
Julie Prestopnik
National Center for Atmospheric Research
Research Applications Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu

------------------------------------------------