20010315: lots of missing data

Diana,
I probably need a clarification as to where "no stations
reporting at this time" is appearing. Is this in SNLIST?

If this is in SNLIST, then I'd need to see your input for
AREA and DATTIM, but let me start with the Denver example.

For Denver, the WMO id is 72469. So, if you give AREA=@72469,
then according to the etc/stat2000.txt file, you should start seeing
data about Oct 15, 1948. However, the station ID for this point is
LRY not DEN! So, if you gave AREA=@DEN, then you won't see any
upper air data until August 1956.

Also, the early sounding data is generally at 3Z and 15Z (instead of 0Z and 
12Z),
so you should be expecting that time difference as well. This is why I gave
the example that showed selecting all sounding times from the CD using
FSL's program (and not the option they provide of only 0Z and 12Z).

If you give DATTIM=list, you will see the available times in the file.
If you give DATTIM=ALL, AREA=@72469, then you will see the times that 
sounding data is available for Denver. If there are other times/stations
in the file, then there may be times where Denver doesn't exist.

So, using the example above, you you see any output for 72469 starting in 1948?

Steve Chiswell
Unidata User Support


>From: address@hidden
>Organization: UCAR/Unidata
>Keywords: 200103160042.f2G0g7L18703

>
>Hi Steve,
>        I use Splus software, so I decided to create separate file for 
>each station/year as indicated in the script you wrote.  The script
>is working fine...thanks so much for sending it.
>        BUT, I'm running into a big problem.  I've been running the 
>script for one station at a time, to test that everything is working okay.
>(before looking at all 60 stations).  Most of the stations I ran so far,
>including the Denver station, are turning up the msg. "no stations
>reporting at this time"...for every year!  So, it's not finding the data
>for those stations in the YEAR.gem files. I've looked at about 10 stations
>so far, and only the Brownsville, TX had data...it calculated all of the
>indices I needed for all times.
>       My original FSL text file 
>(after extracting the 60 stations) was huge - almost 2GB.  So, the 
>data must have been there.  Do you think there was a problem in 
>converting that to the gem format?  I'll paste the size of the yearly 
>gem files below.  Do you have any idea what could be wrong?
>
>sorry to trouble you with all of this...hopefully , i'll be on my way soon.
>
>Diana
>
>
>3488 -rw-r--r--   1 ccd      twenty   1775104 Mar  9 16:56 1946.gem
>3504 -rw-r--r--   1 ccd      twenty   1784320 Mar  9 16:56 1947.gem
>5616 -rw-r--r--   1 ccd      twenty   2859520 Mar  9 17:01 1948.gem
>5632 -rw-r--r--   1 ccd      twenty   2877440 Mar  9 17:01 1949.gem
>5776 -rw-r--r--   1 ccd      twenty   2998784 Mar  9 17:01 1950.gem
>6384 -rw-r--r--   1 ccd      twenty   3261440 Mar  9 17:02 1951.gem
>6992 -rw-r--r--   1 ccd      twenty   3567104 Mar  9 17:02 1952.gem
>7728 -rw-r--r--   1 ccd      twenty   3950592 Mar  9 17:02 1953.gem
>7744 -rw-r--r--   1 ccd      twenty   3950592 Mar  9 17:02 1954.gem
>7344 -rw-r--r--   1 ccd      twenty   3749376 Mar  9 17:02 1955.gem
>8080 -rw-r--r--   1 ccd      twenty   4138496 Mar  9 17:02 1956.gem
>8256 -rw-r--r--   1 ccd      twenty   4215296 Mar  9 17:02 1957.gem
>8624 -rw-r--r--   1 ccd      twenty   4416000 Mar  9 17:02 1958.gem
>8288 -rw-r--r--   1 ccd      twenty   4236800 Mar  9 17:02 1959.gem
>7488 -rw-r--r--   1 ccd      twenty   3821056 Mar  9 17:02 1960.gem
>7872 -rw-r--r--   1 ccd      twenty   4019712 Mar  9 17:02 1961.gem
>7792 -rw-r--r--   1 ccd      twenty   3977728 Mar  9 17:02 1962.gem
>6896 -rw-r--r--   1 ccd      twenty   3521536 Mar  9 17:02 1963.gem
>7952 -rw-r--r--   1 ccd      twenty   4069888 Mar  9 17:02 1964.gem
>7984 -rw-r--r--   1 ccd      twenty   4079104 Mar  9 17:02 1965.gem
>
>