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

20030122: McIDAS - Tru64 - ptlist not listing CMAN stations (cont.)



>From: "Angel Li" <address@hidden>
>Organization: University of Miami
>Keywords: 200301211600.h0LG0gD13023 McIDAS-XCD CMAN

Hi Angel,

re:
>I created both STNDB.USER and STNDB.SITE (actually Otis did) and the stnlist
>works but only lists those 3 stations, I thought it would list others too.

I logged onto sapodilla this morning as 'mcidas' and did the following:

1) renamed ~mcidas/workdata/STNDB.SITE ~mcidas/workdata/STNDB.SITE.otis
   The reason for this is that I include a STNDB.SITE file with my
   McIDAS-X distribution, and it gets installed in the ~mcidas/data
   directory.  Creation of a STNDB.SITE in ~mcidas/workdata supercedes
   the copy in ~mcidas/workdata given the MCPATH definition that is
   in place for your 'mcidas' user:

mcidas* echo $MCPATH
/mcidas/workdata:/mcidas/data:/mcidas/help

   Adding definitions for MLRF, LONF, and KTNF in a STNDB.USER file
   is all that you should have to do for the values to be seen/used.

2) I ran stnlist.k as 'mcidas' to verify that the definitions for
   MLRF, LONF, and KTNF can be seen:

mcidas* stnlist.k TYPE=CMAN ST=FL
 IDN  ID     Station Name         Data Types      ST CO  LAT        LON        
ELE
 ---  MLRF   Molasses Reef                      C FL US   25:00:36   80:22:48   
 16
 ---  LONF   Long Key                           C FL US   24:50:24   80:51:36   
  7
 ---  KTNF   Keaton Beach                       C FL US   29:49:12   83:35:24   
 10
 ---  CDRF1  CEDAR KEY                          C FL US   29:08:24   83:02:24   
  2
99436 CSBF1  CAPE SAN BLAS                      C FL US   29:40:12   85:22:12   
  2
 ---  DRYF1  DRY TORTUGAS                       C FL US   24:22:48   82:31:12   
  0
 ---  FWYF1  FOWEY ROCKS                        C FL US   25:35:24   80:06:00   
  0
99405 LKWF1  LAKE WORTH                         C FL US   26:37:12   80:01:48   
  5
 ---  SANF1  SAND KEY                           C FL US   24:27:00   81:52:48   
  0
99441 SAUF1  ST. AUGUSTINE                      C FL US   29:52:12   81:16:12   
  8
99441 SAUF1  ST. AUGUSTINE                      C FL US   29:52:12   81:16:12   
  8
 ---  SMKF1  SOMBRERO KEY                       C FL US   24:37:48   81:06:36   
  0
99439 SPGF1  SETTLEMENT POINT                   C FL US   26:40:48   79:00:00   
  2
99422 VENF1  VENICE PIER                        C FL US   27:04:12   82:27:00   
  4
99422 VEN    VENICE PIER                        C FL US   27:04:12   82:27:00   
  4
Number of stations listed: 15
stnlist.k: Done

   STNLIST (stnlist.k) uses geographical extents defined in a navigated
   display for the current frame, or specified by keywords like ST=FL,
   LAT=slat nlat, LON=elon wlon, or CO= to know which stations to list
   information for.  So, for instance, you can list out all of the CMAN
   stations known to McIDAS with the STNLIST invocation:

stnlist.k LAT=-90 90 LON=-180 180 TYPE=CMAN
   
   If you do this, you will see that McIDAS only knows about 40 CMAN
   stations, and these are all in the US.  You can expand McIDAS'
   knowledge of CMAN stations by adding definitions to the file
   ~mcidas/workdata/STNDB.USER,

>A ptlist command does not display any data for the newly created stations.

OK, this is the second part of the exercise.  I just did a grep for
MLRF in all of the textual information we receive in IDS|DDPLUS,
and I see that the station ID is actually MLRF1, not MLRF.  Here
is one example:

2003012414_DDPLUS.wmo:2240C45C 02414062328097 1400 MLRF1 46/// /008243(/010255) 
10053 30239(3////) 40252(4////) 222// 00184 333 921268(921281) 
WWW003246(005258)W002246(004258)W357254(001267)W356259(360273)W357265(002278)W357264(001277)W00531607(00933000)W359256(002268)W022(023)
 S1111 A10010 A20036 FIO000035  18.37    48.0    36.45   N/A    #.##    13.0

The comment is true for LONF and KTNF:

LONF ID is actually LONF1
KTNF ID is actually KTNF1

Given this, I altered the STNDB.USER entries in your ~mcidas/workdata
directory to read:

ID=MLRF1 LATLON=25.01 80.38 ELE=16 ST=FL CO=US NAME='Molasses Reef' 
DATATYPE=CMAN
ID=LONF1 LATLON=24.84 80.86 ELE=7 ST=FL CO=US NAME='Long Key' DATATYPE=CMAN
ID=KTNF1 LATLON=29.82 83.59 ELE=10 ST=FL CO=US NAME='Keaton Beach' DATATYPE=CMAN

Now, a STNLIST of CMAN stations in Florida looks correct:

mcidas* stnlist.k ST=FL TYPE=CMAN
 IDN  ID     Station Name         Data Types      ST CO  LAT        LON        
ELE
 ---  MLRF1  Molasses Reef                      C FL US   25:00:36   80:22:48   
 16
 ---  LONF1  Long Key                           C FL US   24:50:24   80:51:36   
  7
 ---  KTNF1  Keaton Beach                       C FL US   29:49:12   83:35:24   
 10
 ---  CDRF1  CEDAR KEY                          C FL US   29:08:24   83:02:24   
  2
99436 CSBF1  CAPE SAN BLAS                      C FL US   29:40:12   85:22:12   
  2
 ---  DRYF1  DRY TORTUGAS                       C FL US   24:22:48   82:31:12   
  0
 ---  FWYF1  FOWEY ROCKS                        C FL US   25:35:24   80:06:00   
  0
99405 LKWF1  LAKE WORTH                         C FL US   26:37:12   80:01:48   
  5
 ---  SANF1  SAND KEY                           C FL US   24:27:00   81:52:48   
  0
99441 SAUF1  ST. AUGUSTINE                      C FL US   29:52:12   81:16:12   
  8
99441 SAUF1  ST. AUGUSTINE                      C FL US   29:52:12   81:16:12   
  8
 ---  SMKF1  SOMBRERO KEY                       C FL US   24:37:48   81:06:36   
  0
99439 SPGF1  SETTLEMENT POINT                   C FL US   26:40:48   79:00:00   
  2
99422 VENF1  VENICE PIER                        C FL US   27:04:12   82:27:00   
  4
99422 VEN    VENICE PIER                        C FL US   27:04:12   82:27:00   
  4
Number of stations listed: 15
stnlist.k: Done

Question:  Do you happen to know WMO numbers for these stations? (Do
they even have WMO numbers)?  If yes, these should be included in the
station definitions in STNDB.USER.  GEMPAK tables indicate that the WMO
number for MLRF1 is 99443, so I added it to the STNDB.USER entry.
GEMPAK doesn't have WMO numbers for either of the other two stations.

Hopefully, when the next file is decoded by XCD these stations will be
included.

re: U Miami acting as an IDD relay node for sites in Central and South America

>We would be glad to relay data down south.

Wonderful!  We really appreciate this!!

>I'm home nursing a cold and I'll do what ever I can while home.

We can wait to setup the feeds to Brazil (Rio and Belem) until you are well.
Part of the setup will be the installation of a new LDM, LDM 6, that
Steve Emmerson has been working on for the past two months.  This LDM
version can move substantially more data in the same period of time
than LDM 5.

Again, thanks to you/U Miami for your willingness to help us extend
our IDD!

Tom


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.