[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20000828: Map analyses

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20000828: Map analyses
  • Date: Tue, 29 Aug 2000 09:46:50 -0600
>From: Tom Priddy <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200008291421.e7TELiN22834

>From: Tom Priddy
>
>....on a different concern:   We now have our linux system up with ldm and
>gempak.
>A look at this morning's 9:00am temperature/isobaric anal on our unix system
>compared
>to our linux system show to very different maps.  I've enclosed both
>maps....latestusa.gif
>is from the unix gempak system......latestusb.gif is from the linux gempak sys
> tem.
>
>Any ideas why these two maps are different...when we are using the same script
> s
>on both gempak systems?  The linux maps doesn't indicate any of the 30's, 40's
>  and
>
>50's in NW US...while the unix map does? Help!
>


Tom,

I looked at the 2 gifs you refer to.

First, I noticed that the latestusa.gif map says 9AM while the latestusb.gif
says 8AM, so from the start, we are probably out in left field.

The latestusb.gif shows a 34 degree temperature plotted in Montana which
seems reasonable. The temperature contours do not seem to match this time
of day however. First, they imply 70's in Montana, and more importantly
100s in Kansas. Those temperatures in Kansas are more representative of
the daytime highs for the 28th, and not 8AM on the 29th. So, it would
appear that your temperature grid is not the same time as the plotted data.


Steve Chiswell