[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20060317: gdgsfc question
- Subject: 20060317: gdgsfc question
- Date: 17 Mar 2006 09:32:06 -0700
Jon,
Double check your ATE station entry to make sure
you haven't used tabs in the columns. A look at the
SLAT;SLON;SELV might give a tip as to where the
column are off, or if the data is coming from another
station in the table with that unexpected lat/lon.
Steve Chiswell
Unidata User Support
On Fri, 2006-03-17 at 09:11, Case.Jon wrote:
> Dear Gembud,
>
> I'm tring to extract NWP point forecasts into a surface file in the
> following manner:
>
> (1) Created a sub-set list of the sfstns.tbl file, adding a new
> station to the list (which I called "ATE" for now).
> (2) Created new surface file with sfcfil.
> (3) Run gdgsfc to extract the surface parameters to the stations in
> the surface file created in (2).
> (4) Examine extracted data using sflist.
>
> The problem I've encountered is with the new station "ATE". Even
> though I defined the lat/lon and rest of its station data correctly in
> the sub-setted .tbl file, the data are not getting corrected extracted
> to the station. In fact, sflist shows the slat and slon as completely
> incorrect, not at all reflecting the values I put into the station
> table file used in sfcfil.
>
> So, what can I do to get the new station data recognized within the
> surface file?
> Thanks in advance,
> Jon
>
> -----------------------------------------------------------------
> Jonathan L. Case, Meteorologist
> ENSCO Inc. / Applied Meteorology Unit
> 1980 N. Atlantic Ave., Suite 230
> Cocoa Beach, FL 32931
> Voice: (321) 853-8264
> Fax: (321) 853-8415
> ----------------------------------------------------------------
>
>
> The information contained in this email message is intended only for
> the use of the individuals to whom it is addressed and may contain
> information that is privileged and sensitive. If the reader of this
> message is not the intended recipient, you are hereby notified that
> any dissemination, distribution or copying of this communication is
> strictly prohibited. If you have received this communication in error,
> please notify the sender immediately by email at the above referenced
> address. Thank you.
>