20010828: accessing TEXT products at UPRM

>From:  Unidata Mcidas Account <address@hidden>
>Organization:  UPRM
>Keywords:  200108281408.f7SE8l110539 LDM request

Luis,

Sorry I couldn't get to this a couple of days ago, but I was in the middle
of selling my house and moving.

>   Hi again, Amos wants me to add a few more things to our ldm stream.  I
>would try to add them myself, but I'd probably end up downloading more
>stuff than what's necessary, and since we've got bandiwth problems I
>think efficiency is very important.

OK.

>These are: the Molleweide products

You are already getting these images.  While pointing at atmos.uprm.edu
(DATALOC ADD RTIMAGES atmos.uprm.edu), I created the following listings
that demonstrate that you are receiving the Mollweide image products
in the Unidata-Wisconsin datastream:

IMGLIST RTIMAGES/MOLL-IR.ALL
Image file directory listing for:RTIMAGES/MOLL-IR
 Pos Satellite/         Date       Time      Center   Band(s)
     sensor                                 Lat  Lon
 --- -------------  ------------  --------  ---- ---- ------------
   1  G-8 IMG       30 AUG 01242  09:00:00     0   -1 4
   2  G-8 IMG       30 AUG 01242  12:00:00     0   -1 4
   3  G-8 IMG       30 AUG 01242  15:00:00     0   -1 4
   4  G-8 IMG       29 AUG 01241  12:00:00     0   -1 4
   5  G-8 IMG       29 AUG 01241  15:00:00     0   -1 4
   6  G-8 IMG       29 AUG 01241  18:00:00     0   -1 4
   7  G-8 IMG       29 AUG 01241  21:00:00     0   -1 4
   8  G-8 IMG       30 AUG 01242  00:00:00     0   -1 4
   9  G-8 IMG       30 AUG 01242  03:00:00     0   -1 4
  10  G-8 IMG       30 AUG 01242  06:00:00     0   -1 4
IMGLIST: done
 
IMGLIST RTIMAGES/MOLL-WV.ALL
Image file directory listing for:RTIMAGES/MOLL-WV
 Pos Satellite/         Date       Time      Center   Band(s)
     sensor                                 Lat  Lon
 --- -------------  ------------  --------  ---- ---- ------------
   1  G-8 IMG       29 AUG 01241  21:00:00     0   -1 3
   2  G-8 IMG       30 AUG 01242  00:00:00     0   -1 3
   3  G-8 IMG       30 AUG 01242  03:00:00     0   -1 3
   4  G-8 IMG       30 AUG 01242  06:00:00     0   -1 3
   5  G-8 IMG       30 AUG 01242  09:00:00     0   -1 3
   6  G-8 IMG       30 AUG 01242  12:00:00     0   -1 3
   7  G-8 IMG       30 AUG 01242  15:00:00     0   -1 3
   8  G-8 IMG       29 AUG 01241  12:00:00     0   -1 3
   9  G-8 IMG       29 AUG 01241  15:00:00     0   -1 3
  10  G-8 IMG       29 AUG 01241  18:00:00     0   -1 3
IMGLIST: done

>and all the weather text for SJU (he gave me an example of what he wants
>http://www.srh.noaa.gov/data/sju).  Is it possible to get those?

You are already getting these also.  If I remember correctly (my login
to atmos no longer appears to work), you are requesting all of the DDPLUS
and IDS data (the volume for this is low), and are feeding both of
these streams into the McIDAS-XCD process in ~ldm/pqact.conf:

DDPLUS|IDS      ^.*     PIPE
        xcd_run DDS

The textual products are contained in the RTWXTEXT dataset and are all
listable using the WXTLIST application of McIDAS.  Here are a couple of
examples:

First, here is the listing one gets from the URL you sent:

www.srh.noaa.gov - /data/sju/

[To Parent Directory]
   8/30/01  8:25 AM        <dir> ABV
   8/30/01  7:29 AM        <dir> AFD
   8/30/01  4:35 AM        <dir> CCF
   3/22/01  4:12 PM        <dir> CFW
 ...

www.srh.noaa.gov - /data/sju/ABV/

[To Parent Directory]
   8/30/01  8:25 AM          451 SJUABVSJU.1.txt
   8/29/01  8:21 PM          493 SJUABVSJU.2.txt
   8/29/01  8:23 AM          450 SJUABVSJU.3.txt
 ...

www.srh.noaa.gov/data/sju/ABV/SJUABVSJU.1.txt

UFUS42 TJSJ 301323
ABVSJU
78526 TTCC  80121 78526 70872 68358 09023 50079 57760 09040 
30406 54362 10038 20667 51563 10052 10124 40571 10534 88999 
77999=

TTDD  8012/ 78526 11936 74157 22678 68958 33639 64559 44594 
65159 55551 60159 66405 52961 77330 55961 88259 54962 99223 
51163 11177 51964 22113 45368 33090 38173 44080 38374 55071 
38373=

PPDD  80120 78526 9558/ 06506 09017 966// 09040 970// 08538 
986// 09552 990// 10052 1009/ 10545 10032=


This product is an upperair listings for San Juan, TJSJ.  You can access them
using the WXTLIST application looking at your own machine:

DATALOC ADD RTWXTEXT ATMOS.UPRM.EDU

Group Name                    Server IP Address
--------------------         ----------------------------------------
RTWXTEXT                     ATMOS.UPRM.EDU

<LOCAL-DATA> indicates that data will be accessed from the local data directory.
DATALOC -- done
 
WXTLIST APRO=ABV ASTN=SJU
UFUS42 TJSJ 301323                                              2001242 1330
ABVSJU
78526 TTCC  80121 78526 70872 68358 09023 50079 57760 09040
30406 54362 10038 20667 51563 10052 10124 40571 10534 88999
77999=
TTDD  8012/ 78526 11936 74157 22678 68958 33639 64559 44594
65159 55551 60159 66405 52961 77330 55961 88259 54962 99223
51163 11177 51964 22113 45368 33090 38173 44080 38374 55071
38373=
PPDD  80120 78526 9558/ 06506 09017 966// 09040 970// 08538
986// 09552 990// 10052 1009/ 10545 10032=
WXTLIST: done

Notice how the value for APRO= is the first three characters of the AWIPS
product header, and the value for ASTN= is the last three characters of
the AWIPS product header:

ABVSJU
\_/\_/
 |  |__ ASTN= value
 |_____ APRO= value

As is always the case with McIDAS, there is more than one way to get the same
information.  Here is an alternate WXTLIST invocation:

WXTLIST WMO=UFUS42 WSTN=TJSJ

UFUS42 TJSJ 301323                                              2001242 1330
ABVSJU
78526 TTCC  80121 78526 70872 68358 09023 50079 57760 09040
30406 54362 10038 20667 51563 10052 10124 40571 10534 88999
77999=
TTDD  8012/ 78526 11936 74157 22678 68958 33639 64559 44594
65159 55551 60159 66405 52961 77330 55961 88259 54962 99223
51163 11177 51964 22113 45368 33090 38173 44080 38374 55071
38373=
PPDD  80120 78526 9558/ 06506 09017 966// 09040 970// 08538
986// 09552 990// 10052 1009/ 10545 10032=
WXTLIST: done

In this case, I searched on the WMO product header, UFUS42, specifying
that I want the information for the WMO station ID, TJSJ.

You can tailor your WXTLIST request by specifying more or fewer keywords
on the invocation command line.  In particular, you might want to look
for data for a particular day/time.  How far back you can look in time
will be determined by how much of the TEXT data that you keep on your
system at any time.  The real beauty of ADDE is that if your system
is not keeping enough days of data online (i.e., you are interested in
textual reports for several days ago), you can always point at a different
cooperating server and see if it has the data.

You can find out more on how to run WXTLIST through the online help:

HELP WXTLIST

and/or in the Unidata McIDAS User's Guide:

Unidata McIDAS-X User's Guide
http://www.unidata.ucar.edu/packages/mcidas/780/users_guide
  Commands by Alphabetical Order
  http://www.unidata.ucar.edu/packages/mcidas/780/users_guide/McHTML-79.HTML
    WXTLIST
    http://www.unidata.ucar.edu/packages/mcidas/780/users_guide/McHTML-259.HTML

>If
>you send me the request lines for those it'll be more than enough,
>I'm pretty sure I can do the rest (and I won't be wasting your time).

The good news is that you don't have to touch anything in the LDM setup.
The bad news is that you have to learn how to run WXTLIST :-)

>   Following up on our previous conversation, we've begun to shop around
>for a dedicated internet connection.  We're supposed to get an estimate
>today.  The good news is we seem to have enough funding for a decent
>connection.

This is very good news indeed, especially considering that Puerto Rico
just connected to much higher speed networking.

>On the other hand, we seem to be missing some of the products
>during local network peak hours.  Hope this will be fixed with the new
>connection.

I hope so too.  Good luck!

>   Thank you,

You are welcome.  Please let me know if you run into any problems
figuring out how to run WXTLIST to see the textual data you/Amos wants.

Tom

>From address@hidden Fri Aug 31 14:58:54 2001
>Subject: Re: 20010828: accessing TEXT products at UPRM

Tom,
   Hi, everything seems to be working fine now.  Thanks.  For some strange
reason, our connection to San Juan got an upgrade this week.  It wasn't
announced, and I still don't know if it's going to be permanent or
anything else about it for that matter.  What I've heard is that it's some
sort of optical line, and that it could be an (OC-3) but nothing sure.
No more connections problem(at least for this week).  Great news.  We have
lost no images all week long.

Luis Munoz
System Administrator
Caribbean Climate Center @ UPRM