20050922: 20050825: JOSS-Derived BUFR Files and Gempak's NAMSND

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to address@hidden for more info.

Bill,

I cleaned up the STATIONS.TXT file. The last entry was missing
lat/lon/elev information. I deleted that for this test.
Also, I created an  id "SHIP" for the ship
station where you have "        " for the station ID, and "999999"
for the number.

Similarly, you have s few lined in the DATA.TXT file where there is no
station ID (I'll asume that is now SHIP).

The problem you were having may be that you specified SFFSRC as TEXT,
which would only store the raw reports, but no station data.

I ran:

1)
 SFOUTF   = test.sao
 SFPRMF   = PMSL;TMPC;DWPC;SPED;DRCT;GUMS;WWMO;VSBK
 STNFIL   = STATIONS.TXT
 SHIPFL   = NO
 TIMSTN   = 100/100
 SFFSRC   =
 GEMPAK-SFCFIL>r

 SFCFIL PARAMETERS:

 New surface file:      test.sao
 Parameter file:        PMSL;TMPC;DWPC;SPED;DRCT;GUMS;WWMO;VSBK
 Station file:
 Number of stations in STNFIL:     764
 Number of additional stations:    100
 Total number of stations:         864
 Total number of times:            100

 This file will be a standard surface file.

Enter <cr> to accept parameters or type EXIT:
 The file has been created.
 Parameters requested: SFOUTF,SFPRMF,STNFIL,SHIPFL,TIMSTN,SFFSRC.
 GEMPAK-SFCFIL>
--------------------------------------------------------------------'


2)
 SFEFIL    Surface edit file                 DATA.TXT
 SFFILE    Surface data file                 test.sao
 Parameters requested: SFEFIL,SFFILE.
 GEMPAK-SFEDIT>r

 SFEDIT PARAMETERS:

 Edit file:           DATA.TXT
 Output surface file: test.sao

 Parameters to be added to file:

 PMSL TMPC DWPC SPED DRCT GUMS WWMO VSBK
Enter <cr> to accept parameters or type EXIT:
 Parameters requested: SFEFIL,SFFILE.
 GEMPAK-SFEDIT>
---------------------------------------------------------------------------

3) I plotted the data with SFMAP for 980111/0000 and was sucessful.

I've attached the modified STATIONS.TXT, DATA.TXT and the test.sao back
to this reply for your referral.

Steve Chiswell
Unidata User Support



****************************************************************************
Unidata User Support                                    UCAR Unidata Program
303 497 8643                                                  P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata WWW Service              http://my.unidata.ucar.edu/content/support
****************************************************************************

On Fri, 30 Sep 2005, Capehart, William J wrote:

> Hi Steve:
>
> I'm attaching all the relevant files to this email.
>
> I am also cutting and pasting the GEMPAK commands including the options we 
> used.  They'll be attached in a text file as well (which includes the GEMPAK 
> settings for SFCFIL and SFEDIT.)
>
> Ideas would be appreciated.  Thanks for your time on this....
>
> Cheers and Thanks
> Bill
>
>
>
>
>
> ================================================================
> Bill Capehart <address@hidden>   Associate Professor
> Institute of Atmospheric Sciences         Land Surface Processes
> 213 Mineral Industries Building                 Hydrometeorology
> South Dakota School of Mines and Technology Ph:  +1-605-394-1994
> 501 East Saint Joseph Street                Fax: +1-605-394-6061
> Rapid City, SD 57701-3995                Mobile: +1-605-484-5692
> =================== http://capehart.sdsmt.edu ==================
>
> -----Original Message-----
> From: Unidata Support [mailto:address@hidden]
> Sent: Thursday, 22 September, 2005 17:17
> To: Capehart, William J
> Cc: Unidata Support
> Subject: 20050922: 20050825: JOSS-Derived BUFR Files and Gempak's NAMSND
>
>
> Bill.
>
> You didn't show your input for SFCFIL, however, I suspect that is the problem.
> You need to specify SFPRMF as a list of parameters and order that will
> be in your DATA.TXT file. Alternatively, you can create a packing file for 
> your
> data set. Either approach is valid, but the parameters used to create your 
> sao file
> must match those in your TXT file.
>
> If you still have trouble, send me your SFCFIL input as well as a sample 
> DATA.TXT
> and station table file.
>
> Steve Chiswell
> Unidata User SUpport
>
>
>
> >From: "Capehart, William J" <address@hidden>
> >Organization: UCAR/Unidata
> >Keywords: 200509222240.j8MMecYJ019082
>
> >Hi Steve and sorry for the delay in getting back with you on this.
> >
> >From communicating with the people across town from you, JOSS's format for 
> >BUF
> > R is not compatible with what Gempak is wanting.
> >
> >In the interim we went to a more two fisted approach and requested the data 
> >in
> > to ASCII and ported the data over into an ASCII format that could be 
> > ingested
> >  into GEMPAK as recommended from the gempak tutorials via the pages
> >
> >http://www.unidata.ucar.edu/software/gempak/tutorial/decoders3.html
> >
> >
> >and
> >
> >http://www.unidata.ucar.edu/software/gempak/tutorial/importingdata.html
> >
> >We not only used this with our formerly JOSS provided data, but with the 
> >examp
> > les provided in the above URLs (the aircraft example) and even real gempak 
> > su
> > rface data, dropping into into ASCII
> >
> >With each of these approaches (following the tutorial examples to the best 
> >tha
> > t we can see), we the same consistent failure message.
> >
> >GEMPAK-SFEDIT>list
> > SFEFIL   = DATA.TXT
> > SFFILE   = lkice.sao
> > GEMPAK-SFEDIT>run
> > [SFEDIT -8]  Parameter PMSL is not in the data set.
> > [SFEDIT -8]  Parameter TMPC is not in the data set.
> > [SFEDIT -8]  Parameter DWPC is not in the data set.
> > [SFEDIT -8]  Parameter SPED is not in the data set.
> > [SFEDIT -8]  Parameter DRCT is not in the data set.
> > [SFEDIT -8]  Parameter GUMS is not in the data set.
> > [SFEDIT -8]  Parameter WWMO is not in the data set.
> > [SFEDIT -8]  Parameter VSBK is not in the data set.
> > [SFEDIT -9]  SFEDIT cannot continue with invalid parameters.
> > Parameters requested: SFEFIL,SFFILE.
> > GEMPAK-SFEDIT>
> >
> >My suspicions is that we are inches from getting this but are doing something
> > "obvious."  Do you guys have any ideas here?
> >
> >Cheers and Thanks
> >Bill
> >
> >
> >================================================================
> >Bill Capehart <address@hidden>   Associate Professor
> >Institute of Atmospheric Sciences         Land Surface Processes
> >213 Mineral Industries Building                 Hydrometeorology
> >South Dakota School of Mines and Technology Ph:  +1-605-394-1994
> >501 East Saint Joseph Street                Fax: +1-605-394-6061
> >Rapid City, SD 57701-3995                Mobile: +1-605-484-5692
> >=================== http://capehart.sdsmt.edu ==================
> >
> >
> >-----Original Message-----
> >From: Unidata Support [mailto:address@hidden]
> >Sent: Monday, 29 August, 2005 10:29
> >To: Capehart, William J
> >Cc: address@hidden
> >Subject: 20050825: JOSS-Derived BUFR Files and Gempak's NAMSND
> >
> >
> >Bill,
> >
> >NAMSND is a program to decode the Model output upperair BUFR files
> >generated by NCEP. It is not capable of decoding other formats of BUFR data,
> >such as a surface file. What format of data is JOSS capable of providing for
> >your data set?
> >
> >Steve Chiswell
> >
> >
> >>From: "Capehart, William J" <address@hidden>
> >>Organization: UCAR/Unidata
> >>Keywords: 200508252057.j7PKvIjo017107
> >
> >>
> >>
> >>(CCing to both JOSS and GEMBUD)
> >>
> >>I have been trying to translate a BUFR file of surface data provided by 
> >>NCAR'
> > s
> >>  JOSS office using Gempak's NAMSND program to no avail.  Are the BUFR files
> > f
> >> rom JOSS compatible with what Gempak's NAMSND program expects or am I 
> >> barkin
> > g
> >>  up the wrong tree.  If they are not compatible, what tools are out there 
> >> to
> >
> >> plot out the JOSS BUFR files in station model form (ala Gempak's SFMAP).
> >>
> >>Cheers and Thanks.
> >>================================================================
> >>Bill Capehart <address@hidden>   Associate Professor
> >>Institute of Atmospheric Sciences         Land Surface Processes
> >>213 Mineral Industries Building                 Hydrometeorology
> >>South Dakota School of Mines and Technology Ph:  +1-605-394-1994
> >>501 East Saint Joseph Street                Fax: +1-605-394-6061
> >>Rapid City, SD 57701-3995                Mobile: +1-605-484-5692
> >>========== http://www.hpcnet.org/sdsmt/wcapehart/about =========
> >>
> >>
> >--
> >************************************************************************> 
> >>Unidata User Support                                    UCAR Unidata Pro> 
> >>(303)497-8643                                                  P.O. Box > 
> >>address@hidden                                   Boulder, CO 8> 
> >>------------------------------------------------------------------------> 
> >>Unidata WWW Service              http://my.unidata.ucar.edu/content/supp> 
> >>------------------------------------------------------------------------> 
> >>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.
> >
> --
> *************************************************************************> 
> Unidata User Support                                    UCAR Unidata Prog> 
> (303)497-8643                                                  P.O. Box 3> 
> address@hidden                                   Boulder, CO 80> 
> -------------------------------------------------------------------------> 
> Unidata WWW Service              http://my.unidata.ucar.edu/content/suppo> 
> -------------------------------------------------------------------------> 
> 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.
>