19990123: IMGREMAP to match AAMAP invocation

>From: Anthony James Wimmers <address@hidden>
>Organization: UVa
>Keywords: 199901232100.OAA26192 McIDAS IMGREMAP AAMAP

Tony,

>What are the correct set of commands to do this in ADDE?:
>
>AAMAP 9950 9970 X PS 35 105 15 SMOOTH=YES
>
>I tried this:
>
>IMGREMAP LA.9950 LA.9970 PRO=PS LATLON=35 105 RES=15 SMOOTH=YES SSIZE=ALL
>DSIZE=ALL
>
>but the image does not center at 35 North, 105 West.

I did the following to get the match:

AAMAP 8000 1234 X PS 35 105 15 SMOOTH=YES

IMGLIST MYDATA/IMAGES.1234 FORM=EXP
Image file directory listing for:MYDATA/IMAGES
 Pos Satellite/         Date       Time      Center      Res (km)   Image_Size
     sensor                                 Lat  Lon    Lat   Lon
 --- -------------  ------------  --------  ---- ----  ----- ----- ------------
1234  GOES-7        13 MAR 93072  17:01:00    35  105
    Band: 1   0.65 um Daytime cloud detection           15.0  15.0   480 x  640
     proj:    0 created: 1999024    439  memo: AAA-MSI TO VIS      VIA ARCHIVE
     type:VISR     cal type:BRIT
     offsets:  data=  768 navigation=  256 calibration=    0 auxillary=    0
     doc length:   0   cal length:   0   lev length:   0 PREFIX=   0
     valcod:          0 zcor:  1 avg-smp: A
     start yyddd: 1993072  start time:170105  start scan:   56
     lcor: 2596  ecor:  5200  bytes per pixel: 1  ss: 32
     Image Center Point Res (derived)  Lat:  12.63 (km)  Lon:  12.62 (km)

IMGLIST: done


IMGREMAP MYDATA/IMAGES.8000 MYDATA/IMAGES.1235 PRO=PS LATLON=35 105 RES=15 
SMOOTH=YES

IMGLIST MYDATA/IMAGES.1235 FORM=EXP
Image file directory listing for:MYDATA/IMAGES
 Pos Satellite/         Date       Time      Center      Res (km)   Image_Size
     sensor                                 Lat  Lon    Lat   Lon
 --- -------------  ------------  --------  ---- ----  ----- ----- ------------
1235  GOES-7        13 MAR 93072  17:01:00    35  105
    Band: 1   0.65 um Daytime cloud detection           15.0  15.0   480 x  640
     proj:    0 created: 1999024   1803  memo: AAA-MSI TO VIS      VIA ARCHIVE
     type:VISR     cal type:BRIT
     offsets:  data=  768 navigation=  256 calibration=    0 auxillary=    0
     doc length:   0   cal length:   0   lev length:   0 PREFIX=   0
     valcod:          0 zcor:  1 avg-smp: A
     start yyddd: 1993072  start time:170105  start scan:   56
     lcor: 2596  ecor:  5200  bytes per pixel: 1  ss: 32
     Image Center Point Res (derived)  Lat:  12.63 (km)  Lon:  12.62 (km)

IMGLIST: done

As you can see from the IMGLIST outputs, the image created by AAMAP is
the same as the image created by IMGREMAP.

The next question is why your invocation didn't produce the desire
results?  I believe that the answer lies in the DSIZE= keyword.  From
the IMGREMAP documentation, I see that the default for SSIZE= is ALL, so
specifying this on the command line should be redundant.  DSIZE=, on the
other hand, does the following:

  DSIze=line ele | number of lines and elements in ddataset; the 'ele'
                   value must be a multiple of 4; DSIZE is not valid
                   with PRO=DEST (def=480 640)
       =ALL      | creates an image large enough to include
                   geographical coverage of sdataset

By specifying DSIZE=ALL, you were telling IMGREMAP to create an output
image that had enough lines and elements to encompass the entire
geographical extent of the image that you are remapping.  Apparently,
this overrides the LATLON= keyword specification of the center location
of the ouput image.  This was as unexpected for me as I am sure it will
be for you.

I don't know whether or not I would classify the above behaviour as a
bug or a feature.  I can tell you that if you adjust the DSIZE= keyword
in the exact same manner as the line and ele positionals for AAMAP, you
always get the center location that you specify in LATLON=.  For instance:

AAMAP 8000 1234 X PS 35 105 15 600 800

and 

IMGREMAP MYDATA/IMAGES.8000 MYDATA/IMAGES.1235 PRO=PS LATLON=35 105 RES=15 
SMOOTH=YES DSIZE=600 800

create the same output image.

>Thanks,

I hope that this helped...

Tom

>From address@hidden  Mon Jan 25 09:51:18 1999
Thanks! Now it's workin' fine.

Tony