20000518: sat images on NWS FTP server (cont.)

>From: weather <address@hidden>
>Organization: NMSU/NSBF
>Keywords:  200005180320.e4I3KaT10388 NOAA FTP imagery

Robert,

>From:      weather <address@hidden>
>Date:      Thu, 18 May 2000 03:20:49 -0000
>Subject:   sat images on NWS FTP server

>One of weak points is satellite data. Does anyone
>know what format the images on the NWS ftp server are in and what
>would be required to view them?

>ftp://ftp.ncep.noaa.gov/pub/data/images/satellite/


>I figured that out last night after I posted the message,
>well I'm not smart enough to figure it out, I just
>renamed it as an AREA file and put it in the right place.

Hopefully, the McIDAS-X 7.7 (due to be received by me any day now) will
contain ADDE server upgrades that will allow sites to create datasets
of imagery in McIDAS AREA format without the AREAnnnn naming convention
(like my ADDE GINI, NIDS, NOWrad (tm WSI Corp.), and BOMR (Australian
Bureau of Meteorlogy servers).

Right now, however, you could look at the file using the McIDAS LWU
command and get a quick idea if it is an AREA:

LWU LIST fname 0 64

The first word in a valid McIDAS AREA will be a 0, the second a 4, and
then the next few will have the satellite identification number, date
[YYYDDD], time [HHMMSS] format:

lwu.k LIST IR_000518_1345 0 64
       0.          0           4 HEX:        0        4 ASCII:
       2.         70      100139 HEX:       46    1872B ASCII:    F    +
       4.     134500        6310 HEX:    20D64     18A6 ASCII:    d
       6.       7440           0 HEX:     1D10        0 ASCII:
       8.        500         640 HEX:      1F4      280 ASCII:
      10.          1           8 HEX:        1        8 ASCII:
      12.          8           1 HEX:        8        1 ASCII:
      14.          0           0 HEX:        0        0 ASCII:
      16.     100139      140622 HEX:    1872B    2254E ASCII:    +   %N
      18.          8          -1 HEX:        8 FFFFFFFF ASCII:
      20.          0           0 HEX:        0        0 ASCII:
      22.          0           0 HEX:        0        0 ASCII:
      24. 1381244999  1447121408 HEX: 52542047 56415200 ASCII: RT G VAR
      26.          0           0 HEX:        0        0 ASCII:
      28.          0           0 HEX:        0        0 ASCII:
      30.          0           0 HEX:        0        0 ASCII:
      32.       1440        3328 HEX:      5A0      D00 ASCII:
      34.        256           0 HEX:      100        0 ASCII:
      36.          0           0 HEX:        0        0 ASCII:
      38.          0           0 HEX:        0        0 ASCII:
      40.          0           0 HEX:        0        0 ASCII:
      42.          0           0 HEX:        0        0 ASCII:
      44.          0      100139 HEX:        0    1872B ASCII:         +
      46.     134514         351 HEX:    20D72      15F ASCII:    r    _
      48.          0           0 HEX:        0        0 ASCII:
      50.          0  1447646034 HEX:        0 56495352 ASCII:      VISR
      52. 1112688980           2 HEX: 42524954        2 ASCII: BRIT
      54.          0           0 HEX:        0        0 ASCII:
      56. 1196835154   538976288 HEX: 47564152 20202020 ASCII: GVAR
      58.          1           0 HEX:        1        0 ASCII:
      60.          0           0 HEX:        0        0 ASCII:
      62.       2816           5 HEX:      B00        5 ASCII:
      64. 1296388675           0 HEX: 4D455243        0 ASCII: MERC
 --END OF LISTING

You have to be careful in interpreting the numbers, however, since the
'endian'ness of the image may be reversed from what your machine is
expecting.  For instance, the file that I looked at was big endian.  If
I had looked at it with a little endian machine (e.g., PC running
Solaris x86), the numbers would have been byte flipped.

>Nice to know there is another repository of stuff.

There are more than that.  A good site to know/use is one operated by
the Marshall Space Flight Center (MSFC) of NASA:

cyclone.msfc.nasa.gov

I have been chatting with a contact at MSFC about making their imagery
archives available to the Unidata community through ADDE.

Also, there are now two sites from which you can get ADDE access to the
GINI imagery in NOAAPORT: adde.unidata.ucar.edu and snow.plymouth.edu.
Check out the holdings using the RTGINI dataset:

DATALOC ADD RTGINI SNOW.PLYMOUTH.EDU
DSINFO IMAGE RTGINI
IMGDISP RTGINI/GE1KVIS STA=KDFW EU=IMAGE SF=YES REFESH='EG;MAP X 5 COU=ALL 
ST=TX;MAP H WID=2'

I am looking for more sites receiving NOAAPORT channels 1 and/or 2 that
would be willing to give ADDE access to the GINI imagery to the Unidata
community.  If you know of any, please pass the information along so I
can contact them.  Thanks.

Tom

>From address@hidden Thu May 18 08:54:52 2000
>Subject: 20000518: sat images on NWS FTP server 

Thanks Tom,

I have used the MSFC site before, I did not know about the ADDE
Gini stuff.  I will have to check that out.

Thanks,
Robert