[Met_help] [rt.rap.ucar.edu #83854] History for question on ASCII2NC
John Halley Gotway via RT
met_help at ucar.edu
Tue Jul 9 12:03:56 MDT 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi,
I'm investing the use of a new ASCAT dataset. This is processed through
GEMPAK, and dumped out into an ascii file, containing LAT,LON,WIND_SPEED,
and no other information.
I see that in order to use the ASCII2NC, I need more information, like
station ID, GRIB code, elevation, and other things. Where do I find these
things, if the original file doesn't have that information? Can I use
dummy variables?
If I take the original file (lat,lon, wind_speed), and create a netCDF file
using python, what else do I need to add to that file so that it will work
with MET?
Thanks!
Roz
--
Rosalyn MacCracken
Support Scientist
Ocean Applilcations Branch
NOAA/NWS Ocean Prediction Center
NCWCP
5830 University Research Ct
College Park, MD 20740-3818
(p) 301-683-1551
rosalyn.maccracken at noaa.gov
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: question on ASCII2NC
From: John Halley Gotway
Time: Tue Jan 30 13:39:26 2018
Hi Roz,
Sounds like you have two choices here:
(1) Dump to ascii and then use ascii2nc.
(2) Write a python script to create the NetCDF file directly yourself.
My guess is that option (1) will be easier. And I'll assume that
you're
using met-6.1.
Here's the 11 column format expected by ascii2nc:
(1) Message_Type - ASCAT
(2) Station_ID - If you don't have one, just put any string here,
"SID"
(3) Valid_Time(YYYYMMDD_HHMMSS)
(4) Lat(Deg North)
(5) Lon(Deg East)
(6) Elevation(msl) - Just use "NA"
(7) Grib_Code - This should have been updated for met-6.1 to be
"GRIB_Code
or Var_Name". In 6.1, you could use "WIND" which is the GRIB code
abbreviation for wind speed. Really, you can put any string here
which
describes the observation value. In the Point-Stat config file,
you'll use
the same string to tell Point-Stat which observations it should use.
(8) Level - Put pressure level info here... or just "NA" is it doesn't
apply
(9) Height(msl or agl) - If this is at the surface, just use 0.
(10) QC_String - Put a quality control string or just "NA".
(11) Observation_Value - Actual wind speed value
Hope that helps.
John
On Tue, Jan 30, 2018 at 9:50 AM, Rosalyn MacCracken - NOAA Affiliate
via RT
<met_help at ucar.edu> wrote:
>
> Tue Jan 30 09:50:35 2018: Request 83854 was acted upon.
> Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> Queue: met_help
> Subject: question on ASCII2NC
> Owner: Nobody
> Requestors: rosalyn.maccracken at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83854 >
>
>
> Hi,
>
> I'm investing the use of a new ASCAT dataset. This is processed
through
> GEMPAK, and dumped out into an ascii file, containing
LAT,LON,WIND_SPEED,
> and no other information.
>
> I see that in order to use the ASCII2NC, I need more information,
like
> station ID, GRIB code, elevation, and other things. Where do I find
these
> things, if the original file doesn't have that information? Can I
use
> dummy variables?
>
> If I take the original file (lat,lon, wind_speed), and create a
netCDF file
> using python, what else do I need to add to that file so that it
will work
> with MET?
>
> Thanks!
> Roz
>
> --
> Rosalyn MacCracken
> Support Scientist
>
> Ocean Applilcations Branch
> NOAA/NWS Ocean Prediction Center
> NCWCP
> 5830 University Research Ct
> College Park, MD 20740-3818
>
> (p) 301-683-1551
> rosalyn.maccracken at noaa.gov
>
>
------------------------------------------------
Subject: question on ASCII2NC
From: Rosalyn MacCracken - NOAA Affiliate
Time: Tue Jan 30 14:32:41 2018
Hi John,
Yes, that definitely helps. We're still using MET 6.0, but, just got
MET
6.1 installed. I need to test that tomorrrow. But, regardless, I
should
be able to follow what you wrote, and fill in my ASCII file, correct?
Roz
On Tue, Jan 30, 2018 at 3:39 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Hi Roz,
>
> Sounds like you have two choices here:
>
> (1) Dump to ascii and then use ascii2nc.
> (2) Write a python script to create the NetCDF file directly
yourself.
>
> My guess is that option (1) will be easier. And I'll assume that
you're
> using met-6.1.
>
> Here's the 11 column format expected by ascii2nc:
> (1) Message_Type - ASCAT
> (2) Station_ID - If you don't have one, just put any string here,
"SID"
> (3) Valid_Time(YYYYMMDD_HHMMSS)
> (4) Lat(Deg North)
> (5) Lon(Deg East)
> (6) Elevation(msl) - Just use "NA"
>
> (7) Grib_Code - This should have been updated for met-6.1 to be
"GRIB_Code
> or Var_Name". In 6.1, you could use "WIND" which is the GRIB code
> abbreviation for wind speed. Really, you can put any string here
which
> describes the observation value. In the Point-Stat config file,
you'll use
> the same string to tell Point-Stat which observations it should use.
>
> (8) Level - Put pressure level info here... or just "NA" is it
doesn't
> apply
> (9) Height(msl or agl) - If this is at the surface, just use 0.
> (10) QC_String - Put a quality control string or just "NA".
> (11) Observation_Value - Actual wind speed value
>
> Hope that helps.
>
> John
>
> On Tue, Jan 30, 2018 at 9:50 AM, Rosalyn MacCracken - NOAA Affiliate
via RT
> <met_help at ucar.edu> wrote:
>
> >
> > Tue Jan 30 09:50:35 2018: Request 83854 was acted upon.
> > Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> > Queue: met_help
> > Subject: question on ASCII2NC
> > Owner: Nobody
> > Requestors: rosalyn.maccracken at noaa.gov
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83854 >
> >
> >
> > Hi,
> >
> > I'm investing the use of a new ASCAT dataset. This is processed
through
> > GEMPAK, and dumped out into an ascii file, containing
LAT,LON,WIND_SPEED,
> > and no other information.
> >
> > I see that in order to use the ASCII2NC, I need more information,
like
> > station ID, GRIB code, elevation, and other things. Where do I
find
> these
> > things, if the original file doesn't have that information? Can I
use
> > dummy variables?
> >
> > If I take the original file (lat,lon, wind_speed), and create a
netCDF
> file
> > using python, what else do I need to add to that file so that it
will
> work
> > with MET?
> >
> > Thanks!
> > Roz
> >
> > --
> > Rosalyn MacCracken
> > Support Scientist
> >
> > Ocean Applilcations Branch
> > NOAA/NWS Ocean Prediction Center
> > NCWCP
> > 5830 University Research Ct
> > College Park, MD 20740-3818
> >
> > (p) 301-683-1551
> > rosalyn.maccracken at noaa.gov
> >
> >
>
>
--
Rosalyn MacCracken
Support Scientist
Ocean Applilcations Branch
NOAA/NWS Ocean Prediction Center
NCWCP
5830 University Research Ct
College Park, MD 20740-3818
(p) 301-683-1551
rosalyn.maccracken at noaa.gov
------------------------------------------------
Subject: question on ASCII2NC
From: John Halley Gotway
Time: Tue Jan 30 20:24:56 2018
Roz,
Yes, that’s correct. The difference between 6.0 and 6.1 is that for
6.0
you’d use the GRIB code for wind speed, 32:
http://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html
With 6.1, you can use a string description instead, I.e WIND... or
wind_speed or whatever else you’d like to call it.
John
On Tue, Jan 30, 2018 at 2:32 PM Rosalyn MacCracken - NOAA Affiliate
via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83854 >
>
> Hi John,
>
> Yes, that definitely helps. We're still using MET 6.0, but, just
got MET
> 6.1 installed. I need to test that tomorrrow. But, regardless, I
should
> be able to follow what you wrote, and fill in my ASCII file,
correct?
>
> Roz
>
> On Tue, Jan 30, 2018 at 3:39 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
> > Hi Roz,
> >
> > Sounds like you have two choices here:
> >
> > (1) Dump to ascii and then use ascii2nc.
> > (2) Write a python script to create the NetCDF file directly
yourself.
> >
> > My guess is that option (1) will be easier. And I'll assume that
you're
> > using met-6.1.
> >
> > Here's the 11 column format expected by ascii2nc:
> > (1) Message_Type - ASCAT
> > (2) Station_ID - If you don't have one, just put any string here,
"SID"
> > (3) Valid_Time(YYYYMMDD_HHMMSS)
> > (4) Lat(Deg North)
> > (5) Lon(Deg East)
> > (6) Elevation(msl) - Just use "NA"
> >
> > (7) Grib_Code - This should have been updated for met-6.1 to be
> "GRIB_Code
> > or Var_Name". In 6.1, you could use "WIND" which is the GRIB code
> > abbreviation for wind speed. Really, you can put any string here
which
> > describes the observation value. In the Point-Stat config file,
you'll
> use
> > the same string to tell Point-Stat which observations it should
use.
> >
> > (8) Level - Put pressure level info here... or just "NA" is it
doesn't
> > apply
> > (9) Height(msl or agl) - If this is at the surface, just use 0.
> > (10) QC_String - Put a quality control string or just "NA".
> > (11) Observation_Value - Actual wind speed value
> >
> > Hope that helps.
> >
> > John
> >
> > On Tue, Jan 30, 2018 at 9:50 AM, Rosalyn MacCracken - NOAA
Affiliate via
> RT
> > <met_help at ucar.edu> wrote:
> >
> > >
> > > Tue Jan 30 09:50:35 2018: Request 83854 was acted upon.
> > > Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> > > Queue: met_help
> > > Subject: question on ASCII2NC
> > > Owner: Nobody
> > > Requestors: rosalyn.maccracken at noaa.gov
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83854
> >
> > >
> > >
> > > Hi,
> > >
> > > I'm investing the use of a new ASCAT dataset. This is processed
> through
> > > GEMPAK, and dumped out into an ascii file, containing
> LAT,LON,WIND_SPEED,
> > > and no other information.
> > >
> > > I see that in order to use the ASCII2NC, I need more
information, like
> > > station ID, GRIB code, elevation, and other things. Where do I
find
> > these
> > > things, if the original file doesn't have that information? Can
I use
> > > dummy variables?
> > >
> > > If I take the original file (lat,lon, wind_speed), and create a
netCDF
> > file
> > > using python, what else do I need to add to that file so that it
will
> > work
> > > with MET?
> > >
> > > Thanks!
> > > Roz
> > >
> > > --
> > > Rosalyn MacCracken
> > > Support Scientist
> > >
> > > Ocean Applilcations Branch
> > > NOAA/NWS Ocean Prediction Center
> > > NCWCP
> > > 5830 University Research Ct
> > > College Park, MD 20740-3818
> > >
> > > (p) 301-683-1551
> > > rosalyn.maccracken at noaa.gov
> > >
> > >
> >
> >
>
>
> --
> Rosalyn MacCracken
> Support Scientist
>
> Ocean Applilcations Branch
> NOAA/NWS Ocean Prediction Center
> NCWCP
> 5830 University Research Ct
> College Park, MD 20740-3818
>
> (p) 301-683-1551
> rosalyn.maccracken at noaa.gov
>
>
------------------------------------------------
Subject: question on ASCII2NC
From: Rosalyn MacCracken - NOAA Affiliate
Time: Wed Jan 31 06:32:37 2018
Hi John,
That sounds easy enough to add in. I'll first try MET6.0, since I
know
that works, then test MET6.1, using "WIND" as the Grib code.
Oh, and if my winds are at 10m, then my Hgt will be 10, correct? I
think
in my config file I use Z10.
Thanks for your help!
Roz
On Tue, Jan 30, 2018 at 10:24 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Roz,
>
> Yes, that’s correct. The difference between 6.0 and 6.1 is that for
6.0
> you’d use the GRIB code for wind speed, 32:
>
> http://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html
>
> With 6.1, you can use a string description instead, I.e WIND... or
> wind_speed or whatever else you’d like to call it.
>
> John
>
> On Tue, Jan 30, 2018 at 2:32 PM Rosalyn MacCracken - NOAA Affiliate
via RT
> <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83854 >
> >
> > Hi John,
> >
> > Yes, that definitely helps. We're still using MET 6.0, but, just
got MET
> > 6.1 installed. I need to test that tomorrrow. But, regardless, I
should
> > be able to follow what you wrote, and fill in my ASCII file,
correct?
> >
> > Roz
> >
> > On Tue, Jan 30, 2018 at 3:39 PM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> > > Hi Roz,
> > >
> > > Sounds like you have two choices here:
> > >
> > > (1) Dump to ascii and then use ascii2nc.
> > > (2) Write a python script to create the NetCDF file directly
yourself.
> > >
> > > My guess is that option (1) will be easier. And I'll assume
that
> you're
> > > using met-6.1.
> > >
> > > Here's the 11 column format expected by ascii2nc:
> > > (1) Message_Type - ASCAT
> > > (2) Station_ID - If you don't have one, just put any string
here, "SID"
> > > (3) Valid_Time(YYYYMMDD_HHMMSS)
> > > (4) Lat(Deg North)
> > > (5) Lon(Deg East)
> > > (6) Elevation(msl) - Just use "NA"
> > >
> > > (7) Grib_Code - This should have been updated for met-6.1 to be
> > "GRIB_Code
> > > or Var_Name". In 6.1, you could use "WIND" which is the GRIB
code
> > > abbreviation for wind speed. Really, you can put any string
here which
> > > describes the observation value. In the Point-Stat config file,
you'll
> > use
> > > the same string to tell Point-Stat which observations it should
use.
> > >
> > > (8) Level - Put pressure level info here... or just "NA" is it
doesn't
> > > apply
> > > (9) Height(msl or agl) - If this is at the surface, just use 0.
> > > (10) QC_String - Put a quality control string or just "NA".
> > > (11) Observation_Value - Actual wind speed value
> > >
> > > Hope that helps.
> > >
> > > John
> > >
> > > On Tue, Jan 30, 2018 at 9:50 AM, Rosalyn MacCracken - NOAA
Affiliate
> via
> > RT
> > > <met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Tue Jan 30 09:50:35 2018: Request 83854 was acted upon.
> > > > Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> > > > Queue: met_help
> > > > Subject: question on ASCII2NC
> > > > Owner: Nobody
> > > > Requestors: rosalyn.maccracken at noaa.gov
> > > > Status: new
> > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=83854
> > >
> > > >
> > > >
> > > > Hi,
> > > >
> > > > I'm investing the use of a new ASCAT dataset. This is
processed
> > through
> > > > GEMPAK, and dumped out into an ascii file, containing
> > LAT,LON,WIND_SPEED,
> > > > and no other information.
> > > >
> > > > I see that in order to use the ASCII2NC, I need more
information,
> like
> > > > station ID, GRIB code, elevation, and other things. Where do
I find
> > > these
> > > > things, if the original file doesn't have that information?
Can I
> use
> > > > dummy variables?
> > > >
> > > > If I take the original file (lat,lon, wind_speed), and create
a
> netCDF
> > > file
> > > > using python, what else do I need to add to that file so that
it will
> > > work
> > > > with MET?
> > > >
> > > > Thanks!
> > > > Roz
> > > >
> > > > --
> > > > Rosalyn MacCracken
> > > > Support Scientist
> > > >
> > > > Ocean Applilcations Branch
> > > > NOAA/NWS Ocean Prediction Center
> > > > NCWCP
> > > > 5830 University Research Ct
> > > > College Park, MD 20740-3818
> > > >
> > > > (p) 301-683-1551
> > > > rosalyn.maccracken at noaa.gov
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > Rosalyn MacCracken
> > Support Scientist
> >
> > Ocean Applilcations Branch
> > NOAA/NWS Ocean Prediction Center
> > NCWCP
> > 5830 University Research Ct
> > College Park, MD 20740-3818
> >
> > (p) 301-683-1551
> > rosalyn.maccracken at noaa.gov
> >
> >
>
>
--
Rosalyn MacCracken
Support Scientist
Ocean Applilcations Branch
NOAA/NWS Ocean Prediction Center
NCWCP
5830 University Research Ct
College Park, MD 20740-3818
(p) 301-683-1551
rosalyn.maccracken at noaa.gov
------------------------------------------------
Subject: question on ASCII2NC
From: John Halley Gotway
Time: Wed Jan 31 07:04:23 2018
Roz,
If using met-6.0, put the integer 32 in the GRIB_code column... not a
string. And yes, for 10-m winds, set the height to 10.
Thanks
John
On Wed, Jan 31, 2018 at 6:32 AM Rosalyn MacCracken - NOAA Affiliate
via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83854 >
>
> Hi John,
>
> That sounds easy enough to add in. I'll first try MET6.0, since I
know
> that works, then test MET6.1, using "WIND" as the Grib code.
>
> Oh, and if my winds are at 10m, then my Hgt will be 10, correct? I
think
> in my config file I use Z10.
>
> Thanks for your help!
>
> Roz
>
> On Tue, Jan 30, 2018 at 10:24 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
> > Roz,
> >
> > Yes, that’s correct. The difference between 6.0 and 6.1 is that
for 6.0
> > you’d use the GRIB code for wind speed, 32:
> >
> > http://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html
> >
> > With 6.1, you can use a string description instead, I.e WIND... or
> > wind_speed or whatever else you’d like to call it.
> >
> > John
> >
> > On Tue, Jan 30, 2018 at 2:32 PM Rosalyn MacCracken - NOAA
Affiliate via
> RT
> > <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83854 >
> > >
> > > Hi John,
> > >
> > > Yes, that definitely helps. We're still using MET 6.0, but,
just got
> MET
> > > 6.1 installed. I need to test that tomorrrow. But, regardless,
I
> should
> > > be able to follow what you wrote, and fill in my ASCII file,
correct?
> > >
> > > Roz
> > >
> > > On Tue, Jan 30, 2018 at 3:39 PM, John Halley Gotway via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > > Hi Roz,
> > > >
> > > > Sounds like you have two choices here:
> > > >
> > > > (1) Dump to ascii and then use ascii2nc.
> > > > (2) Write a python script to create the NetCDF file directly
> yourself.
> > > >
> > > > My guess is that option (1) will be easier. And I'll assume
that
> > you're
> > > > using met-6.1.
> > > >
> > > > Here's the 11 column format expected by ascii2nc:
> > > > (1) Message_Type - ASCAT
> > > > (2) Station_ID - If you don't have one, just put any string
here,
> "SID"
> > > > (3) Valid_Time(YYYYMMDD_HHMMSS)
> > > > (4) Lat(Deg North)
> > > > (5) Lon(Deg East)
> > > > (6) Elevation(msl) - Just use "NA"
> > > >
> > > > (7) Grib_Code - This should have been updated for met-6.1 to
be
> > > "GRIB_Code
> > > > or Var_Name". In 6.1, you could use "WIND" which is the GRIB
code
> > > > abbreviation for wind speed. Really, you can put any string
here
> which
> > > > describes the observation value. In the Point-Stat config
file,
> you'll
> > > use
> > > > the same string to tell Point-Stat which observations it
should use.
> > > >
> > > > (8) Level - Put pressure level info here... or just "NA" is it
> doesn't
> > > > apply
> > > > (9) Height(msl or agl) - If this is at the surface, just use
0.
> > > > (10) QC_String - Put a quality control string or just "NA".
> > > > (11) Observation_Value - Actual wind speed value
> > > >
> > > > Hope that helps.
> > > >
> > > > John
> > > >
> > > > On Tue, Jan 30, 2018 at 9:50 AM, Rosalyn MacCracken - NOAA
Affiliate
> > via
> > > RT
> > > > <met_help at ucar.edu> wrote:
> > > >
> > > > >
> > > > > Tue Jan 30 09:50:35 2018: Request 83854 was acted upon.
> > > > > Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> > > > > Queue: met_help
> > > > > Subject: question on ASCII2NC
> > > > > Owner: Nobody
> > > > > Requestors: rosalyn.maccracken at noaa.gov
> > > > > Status: new
> > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > Ticket/Display.html?id=83854
> > > >
> > > > >
> > > > >
> > > > > Hi,
> > > > >
> > > > > I'm investing the use of a new ASCAT dataset. This is
processed
> > > through
> > > > > GEMPAK, and dumped out into an ascii file, containing
> > > LAT,LON,WIND_SPEED,
> > > > > and no other information.
> > > > >
> > > > > I see that in order to use the ASCII2NC, I need more
information,
> > like
> > > > > station ID, GRIB code, elevation, and other things. Where
do I
> find
> > > > these
> > > > > things, if the original file doesn't have that information?
Can I
> > use
> > > > > dummy variables?
> > > > >
> > > > > If I take the original file (lat,lon, wind_speed), and
create a
> > netCDF
> > > > file
> > > > > using python, what else do I need to add to that file so
that it
> will
> > > > work
> > > > > with MET?
> > > > >
> > > > > Thanks!
> > > > > Roz
> > > > >
> > > > > --
> > > > > Rosalyn MacCracken
> > > > > Support Scientist
> > > > >
> > > > > Ocean Applilcations Branch
> > > > > NOAA/NWS Ocean Prediction Center
> > > > > NCWCP
> > > > > 5830 University Research Ct
> > > > > College Park, MD 20740-3818
> > > > >
> > > > > (p) 301-683-1551
> > > > > rosalyn.maccracken at noaa.gov
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Rosalyn MacCracken
> > > Support Scientist
> > >
> > > Ocean Applilcations Branch
> > > NOAA/NWS Ocean Prediction Center
> > > NCWCP
> > > 5830 University Research Ct
> > > College Park, MD 20740-3818
> > >
> > > (p) 301-683-1551
> > > rosalyn.maccracken at noaa.gov
> > >
> > >
> >
> >
>
>
> --
> Rosalyn MacCracken
> Support Scientist
>
> Ocean Applilcations Branch
> NOAA/NWS Ocean Prediction Center
> NCWCP
> 5830 University Research Ct
> College Park, MD 20740-3818
>
> (p) 301-683-1551
> rosalyn.maccracken at noaa.gov
>
>
------------------------------------------------
Subject: question on ASCII2NC
From: Rosalyn MacCracken - NOAA Affiliate
Time: Wed Jan 31 07:15:15 2018
Got it. I'll try it out this morning and see how it goes.
Thanks for your help. I'll let you know how it goes.
Roz
On Wed, Jan 31, 2018 at 9:04 AM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Roz,
>
> If using met-6.0, put the integer 32 in the GRIB_code column... not
a
> string. And yes, for 10-m winds, set the height to 10.
>
> Thanks
> John
>
> On Wed, Jan 31, 2018 at 6:32 AM Rosalyn MacCracken - NOAA Affiliate
via RT
> <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83854 >
> >
> > Hi John,
> >
> > That sounds easy enough to add in. I'll first try MET6.0, since I
know
> > that works, then test MET6.1, using "WIND" as the Grib code.
> >
> > Oh, and if my winds are at 10m, then my Hgt will be 10, correct?
I think
> > in my config file I use Z10.
> >
> > Thanks for your help!
> >
> > Roz
> >
> > On Tue, Jan 30, 2018 at 10:24 PM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> > > Roz,
> > >
> > > Yes, that’s correct. The difference between 6.0 and 6.1 is that
for
> 6.0
> > > you’d use the GRIB code for wind speed, 32:
> > >
> > > http://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html
> > >
> > > With 6.1, you can use a string description instead, I.e WIND...
or
> > > wind_speed or whatever else you’d like to call it.
> > >
> > > John
> > >
> > > On Tue, Jan 30, 2018 at 2:32 PM Rosalyn MacCracken - NOAA
Affiliate via
> > RT
> > > <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83854
>
> > > >
> > > > Hi John,
> > > >
> > > > Yes, that definitely helps. We're still using MET 6.0, but,
just got
> > MET
> > > > 6.1 installed. I need to test that tomorrrow. But,
regardless, I
> > should
> > > > be able to follow what you wrote, and fill in my ASCII file,
correct?
> > > >
> > > > Roz
> > > >
> > > > On Tue, Jan 30, 2018 at 3:39 PM, John Halley Gotway via RT <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > > > Hi Roz,
> > > > >
> > > > > Sounds like you have two choices here:
> > > > >
> > > > > (1) Dump to ascii and then use ascii2nc.
> > > > > (2) Write a python script to create the NetCDF file directly
> > yourself.
> > > > >
> > > > > My guess is that option (1) will be easier. And I'll assume
that
> > > you're
> > > > > using met-6.1.
> > > > >
> > > > > Here's the 11 column format expected by ascii2nc:
> > > > > (1) Message_Type - ASCAT
> > > > > (2) Station_ID - If you don't have one, just put any string
here,
> > "SID"
> > > > > (3) Valid_Time(YYYYMMDD_HHMMSS)
> > > > > (4) Lat(Deg North)
> > > > > (5) Lon(Deg East)
> > > > > (6) Elevation(msl) - Just use "NA"
> > > > >
> > > > > (7) Grib_Code - This should have been updated for met-6.1 to
be
> > > > "GRIB_Code
> > > > > or Var_Name". In 6.1, you could use "WIND" which is the
GRIB code
> > > > > abbreviation for wind speed. Really, you can put any string
here
> > which
> > > > > describes the observation value. In the Point-Stat config
file,
> > you'll
> > > > use
> > > > > the same string to tell Point-Stat which observations it
should
> use.
> > > > >
> > > > > (8) Level - Put pressure level info here... or just "NA" is
it
> > doesn't
> > > > > apply
> > > > > (9) Height(msl or agl) - If this is at the surface, just use
0.
> > > > > (10) QC_String - Put a quality control string or just "NA".
> > > > > (11) Observation_Value - Actual wind speed value
> > > > >
> > > > > Hope that helps.
> > > > >
> > > > > John
> > > > >
> > > > > On Tue, Jan 30, 2018 at 9:50 AM, Rosalyn MacCracken - NOAA
> Affiliate
> > > via
> > > > RT
> > > > > <met_help at ucar.edu> wrote:
> > > > >
> > > > > >
> > > > > > Tue Jan 30 09:50:35 2018: Request 83854 was acted upon.
> > > > > > Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> > > > > > Queue: met_help
> > > > > > Subject: question on ASCII2NC
> > > > > > Owner: Nobody
> > > > > > Requestors: rosalyn.maccracken at noaa.gov
> > > > > > Status: new
> > > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > > Ticket/Display.html?id=83854
> > > > >
> > > > > >
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I'm investing the use of a new ASCAT dataset. This is
processed
> > > > through
> > > > > > GEMPAK, and dumped out into an ascii file, containing
> > > > LAT,LON,WIND_SPEED,
> > > > > > and no other information.
> > > > > >
> > > > > > I see that in order to use the ASCII2NC, I need more
information,
> > > like
> > > > > > station ID, GRIB code, elevation, and other things. Where
do I
> > find
> > > > > these
> > > > > > things, if the original file doesn't have that
information? Can
> I
> > > use
> > > > > > dummy variables?
> > > > > >
> > > > > > If I take the original file (lat,lon, wind_speed), and
create a
> > > netCDF
> > > > > file
> > > > > > using python, what else do I need to add to that file so
that it
> > will
> > > > > work
> > > > > > with MET?
> > > > > >
> > > > > > Thanks!
> > > > > > Roz
> > > > > >
> > > > > > --
> > > > > > Rosalyn MacCracken
> > > > > > Support Scientist
> > > > > >
> > > > > > Ocean Applilcations Branch
> > > > > > NOAA/NWS Ocean Prediction Center
> > > > > > NCWCP
> > > > > > 5830 University Research Ct
> > > > > > College Park, MD 20740-3818
> > > > > >
> > > > > > (p) 301-683-1551
> > > > > > rosalyn.maccracken at noaa.gov
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Rosalyn MacCracken
> > > > Support Scientist
> > > >
> > > > Ocean Applilcations Branch
> > > > NOAA/NWS Ocean Prediction Center
> > > > NCWCP
> > > > 5830 University Research Ct
> > > > College Park, MD 20740-3818
> > > >
> > > > (p) 301-683-1551
> > > > rosalyn.maccracken at noaa.gov
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > Rosalyn MacCracken
> > Support Scientist
> >
> > Ocean Applilcations Branch
> > NOAA/NWS Ocean Prediction Center
> > NCWCP
> > 5830 University Research Ct
> > College Park, MD 20740-3818
> >
> > (p) 301-683-1551
> > rosalyn.maccracken at noaa.gov
> >
> >
>
>
--
Rosalyn MacCracken
Support Scientist
Ocean Applilcations Branch
NOAA/NWS Ocean Prediction Center
NCWCP
5830 University Research Ct
College Park, MD 20740-3818
(p) 301-683-1551
rosalyn.maccracken at noaa.gov
------------------------------------------------
More information about the Met_help
mailing list