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

[McIDAS #UGD-896576]: IMGREMAP of GOES-16 for use in GEMPAK



Hi Robert,

I ran your IMGREMAP command (slightly adjusted for output ADDE dataset);
displayed the result in McIDAS-X; and verified that McIDAS returns fully
calibrated values when the image is interrogated:

IMGREMAP RTGOESR/CONUSC13 MYDATA/IMAGES.3000 RES=2 PRO=MERC SIZE=ALL
***********************************************
*                  WARNING                    *
* The entire source image will be used to     *
* create the destination image. If the source *
* image is located on a remote server, the    *
* total number of bytes transfered will be:   *
*                  3.75 MB                    *
***********************************************
Beginning Image Data transfer, bytes= 3753076
IMGREMAP: transformations complete ... begin data move
Transferring AREA data outbound, bytes= 16321312
IMGREMAP: Done...
 
LWU LIST AREA3000 0 64
       0.          0           4 HEX:        0        4 ASCII:
       2.        186      118032 HEX:       BA    1CD10 ASCII:
       4.     222226        6202 HEX:    36412     183A ASCII:  d   :
       6.       6421           0 HEX:     1915        0 ASCII:
       8.       2976        5484 HEX:      BA0     156C ASCII:      l
      10.          1           1 HEX:        1        1 ASCII:
      12.          1           1 HEX:        1        1 ASCII:
      14.          0           0 HEX:        0        0 ASCII:
      16.     118032      223018 HEX:    1CD10    3672A ASCII:      *g
      18.       4096           0 HEX:     1000        0 ASCII:
      20.          0           0 HEX:        0        0 ASCII:
      22.          0           0 HEX:        0        0 ASCII:
      24. 1397051207  1126191661 HEX: 53454F47 4320522D ASCII: GOES -R C
      26. 1398107759           0 HEX: 53556E6F        0 ASCII: onUS
      28.          0           0 HEX:        0        0 ASCII:
      30.          0           0 HEX:        0        0 ASCII:
      32.       3000         768 HEX:      BB8      300 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           0 HEX:        0        0 ASCII:
      46.          0           0 HEX:        0        0 ASCII:
      48.          0           0 HEX:        0        0 ASCII:
      50.          0  1381189974 HEX:        0 52534956 ASCII:      VISR
      52. 1414091330           0 HEX: 54495242        0 ASCII: BRIT
      54.          0           0 HEX:        0        0 ASCII:
      56. 1313423937           0 HEX: 4E494241        0 ASCII: ABIN
      58.          0           0 HEX:        0        0 ASCII:
      60.          0           0 HEX:        0        0 ASCII:
      62.          0           2 HEX:        0        2 ASCII:
      64. 1129465165           0 HEX: 4352454D        0 ASCII: MERC
 --END OF LISTING

IMGDISP MYDATA/IMAGES.3000
Beginning Image Data transfer, bytes= 1410928
IMGDISP: loaded frame  1
IMGDISP: done
 

     Image Name           Day      Nominal Time   Scan Time    Band
  ----------------      -------    ------------   ---------    ----
  MYDATA/IMAGES.3000   1 Feb 18032   22:22:26      MISSING       13

                        File     Nominal  Image     RAW         TEMP        BRIT
       Lat/Lon      Line/Element  Line/Element                    K
 51:21:52/ 133:16:33   455/ 1008    6657/ 7429            193      225.00       
  193

IMGPROBE: Done

A quick look at the listing of AREA file header word values suggests
where GEMPAK is failing:

      50.          0  1381189974 HEX:        0 52534956 ASCII:      VISR
      52. 1414091330           0 HEX: 54495242        0 ASCII: BRIT
      54.          0           0 HEX:        0        0 ASCII:
      56. 1313423937           0 HEX: 4E494241        0 ASCII: ABIN
      58.          0           0 HEX:        0        0 ASCII:
      60.          0           0 HEX:        0        0 ASCII:

Word 56 in the LWU listing is the 4-character ASCII text string ABIN.
McIDAS uses this word as the key to know which calibration module
to use to convert pixel values into calibrated units.

The Unidata-Wisconsin GOES-East image sectors are created by IMGREMAPping
an RTGOESR full disk image into an existing GVAR image.  The result
of this is word 56 being GVAR, not ABIN:

IMGCOPY RTIMAGES/GE-IR MYDATA/IMAGES.3001 SIZE=SAME
Beginning Image Data transfer, bytes= 4724568
Transferring AREA data outbound, bytes= 4724648
IMGCOPY: RTIMAGES/GE-IR.96 copied to MYDATA/IMAGES.3001
IMGCOPY: done
 
LWU LIST AREA3001 0 64
       0.          0           4 HEX:        0        4 ASCII:
       2.        180      118032 HEX:       B4    1CD10 ASCII:
       4.     221545        2605 HEX:    36169      A2D ASCII: ia   -
       6.       9017           0 HEX:     2339        0 ASCII: 9#
       8.       2726        1732 HEX:      AA6      6C4 ASCII:
      10.          1           4 HEX:        1        4 ASCII:
      12.          8           1 HEX:        8        1 ASCII:
      14.          0           0 HEX:        0        0 ASCII:
      16.     118032      223827 HEX:    1CD10    36A53 ASCII:      Sj
      18.          8           0 HEX:        8        0 ASCII:
      20.          0           0 HEX:        0        0 ASCII:
      22.          0           0 HEX:        0        0 ASCII:
      24. 1193301074     5390678 HEX: 47205452   524156 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.       3001        2816 HEX:      BB9      B00 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      118008 HEX:        0    1CCF8 ASCII:
      46.      71519         356 HEX:    1175F      164 ASCII: _    d
      48.          0           0 HEX:        0        0 ASCII:
      50.          0  1381189974 HEX:        0 52534956 ASCII:      VISR
      52. 1414091330           2 HEX: 54495242        2 ASCII: BRIT
      54.          0           0 HEX:        0        0 ASCII:
      56. 1380013639   538976288 HEX: 52415647 20202020 ASCII: GVAR
      58.          1           0 HEX:        1        0 ASCII:
      60.          0           0 HEX:        0        0 ASCII:
      62.          0           5 HEX:        0        5 ASCII:
      64. 1380013639           0 HEX: 52415647        0 ASCII: GVAR
 --END OF LISTING

My (educated) guess is that GEMPAK understands GVAR calibration.  I
know that GEMPAK does not understand ABIN calibration, so the reason
that no calibrated value of TEMPerature is shown in GEMPAK is that
it doesn't understand how to convert image pixel values into TEMPeratures.

Now, one can tweak the AREA file to indicate that it has GVAR
calibration using the LWU command:

LWU POKE AREA3000 GVAR 56 TYPE=ASCII
 Value was:   1313423937 HEX:     4E494241 ASCII: ABIN
 
LWU LIST AREA3000 0 64
       0.          0           4 HEX:        0        4 ASCII:
       2.        186      118032 HEX:       BA    1CD10 ASCII:
       4.     222226        6202 HEX:    36412     183A ASCII:  d   :
       6.       6421           0 HEX:     1915        0 ASCII:
       8.       2976        5484 HEX:      BA0     156C ASCII:      l
      10.          1           1 HEX:        1        1 ASCII:
      12.          1           1 HEX:        1        1 ASCII:
      14.          0           0 HEX:        0        0 ASCII:
      16.     118032      223018 HEX:    1CD10    3672A ASCII:      *g
      18.       4096           0 HEX:     1000        0 ASCII:
      20.          0           0 HEX:        0        0 ASCII:
      22.          0           0 HEX:        0        0 ASCII:
      24. 1397051207  1126191661 HEX: 53454F47 4320522D ASCII: GOES -R C
      26. 1398107759           0 HEX: 53556E6F        0 ASCII: onUS
      28.          0           0 HEX:        0        0 ASCII:
      30.          0           0 HEX:        0        0 ASCII:
      32.       3000         768 HEX:      BB8      300 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           0 HEX:        0        0 ASCII:
      46.          0           0 HEX:        0        0 ASCII:
      48.          0           0 HEX:        0        0 ASCII:
      50.          0  1381189974 HEX:        0 52534956 ASCII:      VISR
      52. 1414091330           0 HEX: 54495242        0 ASCII: BRIT
      54.          0           0 HEX:        0        0 ASCII:
      56. 1380013639           0 HEX: 52415647        0 ASCII: GVAR
      58.          0           0 HEX:        0        0 ASCII:
      60.          0           0 HEX:        0        0 ASCII:
      62.          0           2 HEX:        0        2 ASCII:
      64. 1129465165           0 HEX: 4352454D        0 ASCII: MERC
 --END OF LISTING

After this change, McIDAS will use the GVAR calibration to return
TEMPerature values:

LWU POKE AREA3000 GVAR 56 TYPE=ASCII

The question then becomes how the GVAR calibration compares with the
ABIN calibration?

Here is the comparison of calibrations for 4 randomly chosen points in
the image:

LWU COPY AREA3000 AREA3001
AREA3000 Copied to AREA3001
 
LWU LIST AREA3000 0 64
 ...
      50.          0  1381189974 HEX:        0 52534956 ASCII:      VISR
      52. 1414091330           0 HEX: 54495242        0 ASCII: BRIT
      54.          0           0 HEX:        0        0 ASCII:
      56. 1313423937           0 HEX: 4E494241        0 ASCII: ABIN
      58.          0           0 HEX:        0        0 ASCII:
 ...
 --END OF LISTING
 
LWU LIST AREA3001 0 64
 ...
      50.          0  1381189974 HEX:        0 52534956 ASCII:      VISR
      52. 1414091330           0 HEX: 54495242        0 ASCII: BRIT
      54.          0           0 HEX:        0        0 ASCII:
      56. 1313423937           0 HEX: 4E494241        0 ASCII: ABIN
      58.          0           0 HEX:        0        0 ASCII:
 ...
 --END OF LISTING
 
LWU POKE AREA3001 GVAR 56 TYPE=ASCII
 Value was:   1313423937 HEX:     4E494241 ASCII: ABIN
 
LWU LIST AREA3001 0 64
 ...
      50.          0  1381189974 HEX:        0 52534956 ASCII:      VISR
      52. 1414091330           0 HEX: 54495242        0 ASCII: BRIT
      54.          0           0 HEX:        0        0 ASCII:
      56. 1380013639           0 HEX: 52415647        0 ASCII: GVAR
      58.          0           0 HEX:        0        0 ASCII:
 ...
 --END OF LISTING
 
SF 1;IMGDISP MYDATA/IMAGES.3000
Beginning Image Data transfer, bytes= 1410928
IMGDISP: loaded frame  1
IMGDISP: done
 
SF 2;IMGDISP MYDATA/IMAGES.3001
Beginning Image Data transfer, bytes= 1410928
IMGDISP: loaded frame  2
IMGDISP: done

LB 1 2
    Image Frame=    1    2
          Dwell=    2    2
LB: Done
 

     Image Name           Day      Nominal Time   Scan Time    Band
  ----------------      -------    ------------   ---------    ----
  MYDATA/IMAGES.3000   1 Feb 18032   22:22:26      MISSING       13

                        File     Nominal  Image     RAW         TEMP        BRIT
       Lat/Lon      Line/Element  Line/Element                    K
 53:26:09/ 134:27:42   266/  942    6468/ 7363            195      223.00       
  195

IMGPROBE: Done
 

     Image Name           Day      Nominal Time   Scan Time    Band
  ----------------      -------    ------------   ---------    ----
  MYDATA/IMAGES.3001   1 Feb 18032   22:22:26      MISSING       13

                        File     Nominal  Image     RAW         TEMP        BRIT
       Lat/Lon      Line/Element  Line/Element                   K
 53:26:09/ 134:27:42   266/  942    6468/ 7363            195      223.00       
  195

IMGPROBE: Done
 

     Image Name           Day      Nominal Time   Scan Time    Band
  ----------------      -------    ------------   ---------    ----
  MYDATA/IMAGES.3000   1 Feb 18032   22:22:26      MISSING       13

                        File     Nominal  Image     RAW         TEMP        BRIT
       Lat/Lon      Line/Element  Line/Element                    K
 51:38:38/ 130:46:43   430/ 1147    6632/ 7568            188      230.00       
  188

IMGPROBE: Done
 

     Image Name           Day      Nominal Time   Scan Time    Band
  ----------------      -------    ------------   ---------    ----
  MYDATA/IMAGES.3001   1 Feb 18032   22:22:26      MISSING       13

                        File     Nominal  Image     RAW         TEMP        BRIT
       Lat/Lon      Line/Element  Line/Element                   K
 51:38:38/ 130:46:43   430/ 1147    6632/ 7568            188      230.00       
  188

IMGPROBE: Done
 

     Image Name           Day      Nominal Time   Scan Time    Band
  ----------------      -------    ------------   ---------    ----
  MYDATA/IMAGES.3000   1 Feb 18032   22:22:26      MISSING       13

                        File     Nominal  Image     RAW         TEMP        BRIT
       Lat/Lon      Line/Element  Line/Element                    K
 48:53:19/ 133:20:52   670/ 1004    6872/ 7425            118      271.00       
  118

IMGPROBE: Done
 

     Image Name           Day      Nominal Time   Scan Time    Band
  ----------------      -------    ------------   ---------    ----
  MYDATA/IMAGES.3001   1 Feb 18032   22:22:26      MISSING       13

                        File     Nominal  Image     RAW         TEMP        BRIT
       Lat/Lon      Line/Element  Line/Element                   K
 48:53:19/ 133:20:52   670/ 1004    6872/ 7425            118      271.00       
  118

IMGPROBE: Done
 

     Image Name           Day      Nominal Time   Scan Time    Band
  ----------------      -------    ------------   ---------    ----
  MYDATA/IMAGES.3000   1 Feb 18032   22:22:26      MISSING       13

                        File     Nominal  Image     RAW         TEMP        BRIT
       Lat/Lon      Line/Element  Line/Element                    K
 46:20:46/ 125:53:30   880/ 1419    7082/ 7840            183      235.00       
  183

IMGPROBE: Done
 

     Image Name           Day      Nominal Time   Scan Time    Band
  ----------------      -------    ------------   ---------    ----
  MYDATA/IMAGES.3001   1 Feb 18032   22:22:26      MISSING       13

                        File     Nominal  Image     RAW         TEMP        BRIT
       Lat/Lon      Line/Element  Line/Element                   K
 46:20:46/ 125:53:30   880/ 1419    7082/ 7840            183      235.00       
  183

IMGPROBE: Done


So, for the 4 randomly chosen locations, the returned TEMPeratures were
identical.  Quite frankly, I am surprised by this, but what the hey!

So, I am suggesting that you add changing AREA header word 56 to GVAR
right after you create an image using IMGREMAP:

imgremap.k RTGOESR/CONUSC13 TEMP/IMAGES.1 RES=2 PRO=MERC SIZE=ALL
lwu.k POKE AREA???? GVAR 56 TYPE=ASCII

(I don't know how you defined your TEMP/IMAGES dataset, so I can't say
what the AREA file name that the result of the IMGREMAP was written into.)

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: UGD-896576
Department: Support McIDAS
Priority: Normal
Status: Closed
===================
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.



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.