20030414: gempak 5.6.j question.

Stonie,

(getting back through the mail why I was out of the office fore 2 weeks)

NCEP uses NAMSND to decode BUFR soundings from the ftp servers.
This program creates both an upper air and surface data file.

One of the additions I did was to enhance NSHARP for using tables
for the drop down selections. I added ETAPFC (point fortcast) while
I was working on the changes (and it is referenced in 
$NAWIPS/tables/nsharp/nsharp_pfc.tbl). Subsequently, NCEP added 
ETASND and RUC2SND to their table for nsharp.

The prmlist.tbl for surface plotting references the ETASFC etc.

I don't have a traditional location for these....but would probably suggest
$GEMDATA/modsnd and $GEMDATA/modsfc. I'll add these to the default Gemenviron
as a place holder.

Steve Chiswell






>From: "Stonie R. Cooper" <address@hidden>
>Organization: Planetary Data, Incorporated
>Keywords: 200304141313.h3EDDP7U025702

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Steve and/or Unidata Support,
>
>In the new gempak 5.6.j, there are several config file references to Eta and 
>RUC derived surface and upper air files . . . and environmental vars such as 
>MODEL_SND and MODEL_SFC.
>
>- - are these files created locally - i.e. post processed from existing data? 
>- -or-, or these the BUFR files decoded from NOAA?
>
>- - if these fields are NOAA created, do you have a pqact.conf example on how 
>you decode?
>
>- - what do you normally set as the path under your MODEL_SND and MODEL_SFC 
>vars?
>
>Thanks!
>- -- 
>Stonie Cooper
>Planetary Data, Incorporated
>(402) 782-6611/(770) 713-6763
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.0.6 (GNU/Linux)
>Comment: For info see http://www.gnupg.org
>
>iD8DBQE+mrOr3iTdV0m17SQRAn95AJ4i2uzbClASz3ila9sKAPIIvb8aWwCfcWfy
>K0B6XZgS50Hp2ylzTgrO+34=
>=6sTu
>-----END PGP SIGNATURE-----
>
>