[Met_help] [rt.rap.ucar.edu #82501] History for how to define message_type_map of Ascii2nc

John Halley Gotway via RT met_help at ucar.edu
Tue Jul 9 12:04:13 MDT 2019


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

Hi John,

      I try to use Asciitonc to convert ascii data to netcdf format. when I read the guide, there's message_type_map to define the variables. I find your previous answer about this question:

And we do matching in the vertical for the
"surface" based only on the message type.  Message types of "ADPSFC" and
"SFCSHP" are considered to be at the surface.  So if you're verifying
2-meter temperature or 10-meter winds (which are "surface" variables), you
should verify against the "ADPSFC" or "SFCSHP" message type.  If you use
any other message type, Point-Stat shouldn't find any matched pairs.


http://mailman.ucar.edu/pipermail/met_help/2009-June/000750.html

*******************************************************************
message_type_map = [
{ key = "FM-12 SYNOP"; val = "ADPSFC"; },
{ key = "FM-13 SHIP"; val = "SFCSHP"; },
{ key = "FM-15 METAR"; val = "ADPSFC"; },
{ key = "FM-18 BUOY"; val = "SFCSHP"; },
{ key = "FM-281 QSCAT"; val = "ASCATW"; },
{ key = "FM-32 PILOT"; val = "ADPUPA"; },
{ key = "FM-35 TEMP"; val = "ADPUPA"; },
{ key = "FM-88 SATOB"; val = "SATWND"; },
{ key = "FM-97 ACARS"; val = "AIRCFT"; }
];

So where to find such definitions of 2-meter temperature as ADFSFC or surface precipitation, 10-meter temperature?

Thank you!

Mandy


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

Subject: how to define message_type_map of  Ascii2nc
From: John Halley Gotway
Time: Fri Oct 27 16:37:40 2017

Mandy,

I read through your email but am not sure how to answer your question.

First, you're correct, the message_type_map is an option in the
ascii2nc
configuration file.  But it's only used when processing ascii
observations
of type little_r.  These "key" strings from the little_r format and
converted to the corresponding "val" strings in the output.  If you're
not
processing little_r observation data, you don't need to worry about
the
this config file entry.

What is the ascii data that you currently have?  Typically, users
convert
custom ascii formats into the 11-column format supported by ascii2nc
that's
described in the user's guide.  If you'd like, you could send me a
sample
of your ascii format and I could see if I have any suggestions.

Hope that helps.

Thanks,
John

On Wed, Oct 25, 2017 at 10:32 AM, Zhang, Mandy via RT
<met_help at ucar.edu>
wrote:

>
> Wed Oct 25 10:32:20 2017: Request 82501 was acted upon.
> Transaction: Ticket created by Man.Zhang-1 at ou.edu
>        Queue: met_help
>      Subject: how to define message_type_map of  Ascii2nc
>        Owner: Nobody
>   Requestors: Man.Zhang-1 at ou.edu
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82501 >
>
>
> Hi John,
>
>       I try to use Asciitonc to convert ascii data to netcdf format.
when
> I read the guide, there's message_type_map to define the variables.
I find
> your previous answer about this question:
>
> And we do matching in the vertical for the
> "surface" based only on the message type.  Message types of "ADPSFC"
and
> "SFCSHP" are considered to be at the surface.  So if you're
verifying
> 2-meter temperature or 10-meter winds (which are "surface"
variables), you
> should verify against the "ADPSFC" or "SFCSHP" message type.  If you
use
> any other message type, Point-Stat shouldn't find any matched pairs.
>
>
> http://mailman.ucar.edu/pipermail/met_help/2009-June/000750.html
>
> *******************************************************************
> message_type_map = [
> { key = "FM-12 SYNOP"; val = "ADPSFC"; },
> { key = "FM-13 SHIP"; val = "SFCSHP"; },
> { key = "FM-15 METAR"; val = "ADPSFC"; },
> { key = "FM-18 BUOY"; val = "SFCSHP"; },
> { key = "FM-281 QSCAT"; val = "ASCATW"; },
> { key = "FM-32 PILOT"; val = "ADPUPA"; },
> { key = "FM-35 TEMP"; val = "ADPUPA"; },
> { key = "FM-88 SATOB"; val = "SATWND"; },
> { key = "FM-97 ACARS"; val = "AIRCFT"; }
> ];
>
> So where to find such definitions of 2-meter temperature as ADFSFC
or
> surface precipitation, 10-meter temperature?
>
> Thank you!
>
> Mandy
>
>

------------------------------------------------
Subject: how to define message_type_map of  Ascii2nc
From: Zhang, Mandy
Time: Mon Oct 30 15:51:20 2017

Zhang, Mandy has shared OneDrive for Business files with you. To view
them, click the links below.


<https://sooners-my.sharepoint.com/personal/man_zhang-
1_ou_edu/_layouts/15/guestaccess.aspx?docid=18e12fcd612e84e07a72fa00a516d3aec&authkey=AUHrLJiaqfWm-
njwA54O8v0&expiration=2017-11-29T21%3a50%3a18.000Z>
[https://r1.res.office365.com/owa/prem/images/dc-
txt_20.png]<https://sooners-my.sharepoint.com/personal/man_zhang-
1_ou_edu/_layouts/15/guestaccess.aspx?docid=18e12fcd612e84e07a72fa00a516d3aec&authkey=AUHrLJiaqfWm-
njwA54O8v0&expiration=2017-11-29T21%3a50%3a18.000Z>

201710200800_LocalAWS.txt<https://sooners-
my.sharepoint.com/personal/man_zhang-
1_ou_edu/_layouts/15/guestaccess.aspx?docid=18e12fcd612e84e07a72fa00a516d3aec&authkey=AUHrLJiaqfWm-
njwA54O8v0&expiration=2017-11-29T21%3a50%3a18.000Z>

<https://sooners-my.sharepoint.com/personal/man_zhang-
1_ou_edu/_layouts/15/guestaccess.aspx?docid=1c707c5b9f66c485ba78d56afc54320e5&authkey=AcuoPXuhg1qdfm3sXATWyfE&expiration=2017-
11-29T21%3a50%3a21.000Z>
[https://r1.res.office365.com/owa/prem/images/dc-
generic_20.png]<https://sooners-my.sharepoint.com/personal/man_zhang-
1_ou_edu/_layouts/15/guestaccess.aspx?docid=1c707c5b9f66c485ba78d56afc54320e5&authkey=AcuoPXuhg1qdfm3sXATWyfE&expiration=2017-
11-29T21%3a50%3a21.000Z>

prepbufr_encode_surface.f90<https://sooners-
my.sharepoint.com/personal/man_zhang-
1_ou_edu/_layouts/15/guestaccess.aspx?docid=1c707c5b9f66c485ba78d56afc54320e5&authkey=AcuoPXuhg1qdfm3sXATWyfE&expiration=2017-
11-29T21%3a50%3a21.000Z>




Hi John,

     I decided to convert ascii observation data to bufr type, Maybe
it is the easiest way.

 But I'm not familiar with Bufr data, for purpose with MET use, what's
the table of bufr it prefers?

 Do you have the fortran code of encode bufr data for MET use?  I
download the sample code from GSI bufr, I don't know whether it works
if I add the variables like rainfall, dewpoint?

the attaches are my ascii data and gsi_bufr_encode fortran code.

Thank you very much!



Mandy



________________________________
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Friday, October 27, 2017 5:37:41 PM
To: Zhang, Mandy
Subject: Re: [rt.rap.ucar.edu #82501] how to define message_type_map
of Ascii2nc

Mandy,

I read through your email but am not sure how to answer your question.

First, you're correct, the message_type_map is an option in the
ascii2nc
configuration file.  But it's only used when processing ascii
observations
of type little_r.  These "key" strings from the little_r format and
converted to the corresponding "val" strings in the output.  If you're
not
processing little_r observation data, you don't need to worry about
the
this config file entry.

What is the ascii data that you currently have?  Typically, users
convert
custom ascii formats into the 11-column format supported by ascii2nc
that's
described in the user's guide.  If you'd like, you could send me a
sample
of your ascii format and I could see if I have any suggestions.

Hope that helps.

Thanks,
John

On Wed, Oct 25, 2017 at 10:32 AM, Zhang, Mandy via RT
<met_help at ucar.edu>
wrote:

>
> Wed Oct 25 10:32:20 2017: Request 82501 was acted upon.
> Transaction: Ticket created by Man.Zhang-1 at ou.edu
>        Queue: met_help
>      Subject: how to define message_type_map of  Ascii2nc
>        Owner: Nobody
>   Requestors: Man.Zhang-1 at ou.edu
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82501 >
>
>
> Hi John,
>
>       I try to use Asciitonc to convert ascii data to netcdf format.
when
> I read the guide, there's message_type_map to define the variables.
I find
> your previous answer about this question:
>
> And we do matching in the vertical for the
> "surface" based only on the message type.  Message types of "ADPSFC"
and
> "SFCSHP" are considered to be at the surface.  So if you're
verifying
> 2-meter temperature or 10-meter winds (which are "surface"
variables), you
> should verify against the "ADPSFC" or "SFCSHP" message type.  If you
use
> any other message type, Point-Stat shouldn't find any matched pairs.
>
>
> http://mailman.ucar.edu/pipermail/met_help/2009-June/000750.html
>
> *******************************************************************
> message_type_map = [
> { key = "FM-12 SYNOP"; val = "ADPSFC"; },
> { key = "FM-13 SHIP"; val = "SFCSHP"; },
> { key = "FM-15 METAR"; val = "ADPSFC"; },
> { key = "FM-18 BUOY"; val = "SFCSHP"; },
> { key = "FM-281 QSCAT"; val = "ASCATW"; },
> { key = "FM-32 PILOT"; val = "ADPUPA"; },
> { key = "FM-35 TEMP"; val = "ADPUPA"; },
> { key = "FM-88 SATOB"; val = "SATWND"; },
> { key = "FM-97 ACARS"; val = "AIRCFT"; }
> ];
>
> So where to find such definitions of 2-meter temperature as ADFSFC
or
> surface precipitation, 10-meter temperature?
>
> Thank you!
>
> Mandy
>
>


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


More information about the Met_help mailing list