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

[McIDAS #QFU-969979]: Retaining calibrated units after imgremap



Hi Greg,

re:
> I'm still working on saving area files in netCDF format from
> GOES-10 for this particular project we are working on very soon. I'd
> like to have 1 netCDF file per scan for the 1km Vis channel and
> another netCDF file that contains the other 4 channels at 4km
> resolution. The problem I'm having is that I can't seem to get all 4
> channels, in TEMP units into the same netCDF file. Here's what I get
> for various attempts:
> 
> IMGCOPY MYDATA/IMAGES.1076 MYDATA/NCDF.6 SIZE=800 800 BAND=2-5 UNIT=TEMP
> IMGCOPY: Server does not support BAND lists
> IMGCOPY: done
> IMGCOPY failed, RC=1
> 
> IMGCOPY MYDATA/IMAGES.1076 MYDATA/NCDF.3 SIZE=800 800 BAND=ALL
> Beginning Image Data transfer, bytes= 5128080
> Transferring AREA data outbound, bytes= 5128160
> IMGCOPY: MYDATA/IMAGES.1076 copied to MYDATA/NCDF.3
> IMGCOPY: done
> 
> The above seemed to work but the netCDF file contains variables with
> raw instead of calibrated units.

I think that the IMGCOPY invocation you are looking for is:

IMGCOPY MYDATA/IMAGES.1076 MYDATA/NCDF.6 SIZE=800 800 BAND=2 3 4 5 UNIT=TEMP

This assumes, however, that the image in MYDATA/IMAGES.1076 is multibanded.

I just ran the following and it seemed to work as desired:

IMGCOPY SOUTH/SH NETCDF/IMAGES.1 BAND=2 3 4 5 UNIT=TEMP TIME=23:45 DAY=265

> IMGCOPY MYDATA/IMAGES.1076 MYDATA/NCDF.3 SIZE=800 800 BAND=ALL UNIT=TEMP
> IMGCOPY: BAND=ALL is invalid for a non-native UNIT=
> IMGCOPY: done
> IMGCOPY failed, RC=1

Presumably this failed since MYDATA/IMAGES.1076 _is_ multibanded and contains
the Vis channel (0.65 um) as one of the bands.  The UNIT=TEMP keyword 
combination
should fail in this case as TEMP is not a valid calibration type for Vis images.

> FYI, this is what MYDATA/IMAGES.1076 contained:
> IMGLIST MYDATA/IMAGES.1076 FORM=ALL
> Image file directory listing for:MYDATA/IMAGES
> Pos Satellite/         Date       Time      Center      Res (km)
> Image_Size
> sensor                                 Lat  Lon    Lat   Lon
> --- -------------  ------------  --------  ---- ----  ----- -----  
> ------------
> 1076  G-10 IMG      19 SEP 08263  21:58:00   -18   82
> Band: 2    3.9 um IR Low Cloud/Fog,Fire Detection    4.00  3.82    800 x  800
> Band: 3    6.8 um IR Mid-level Water Vapor           4.00  3.82    800 x  800
> Band: 4    10.7 um IR Surface/Cloud-top Temp         4.00  3.82    800 x  800
> Band: 5    12.0 um IR SFC/Cloud Temp, Low-level WV   4.00  3.82    800 x  800
> proj:    0 created: 2008260 173158  memo: RT GVAR
> type:GVAR     cal type:RAW
> offsets:  data=    1280 navigation=  256 calibration=  768  auxiliary=    0
> doc length:   0   cal length:   0   lev length:   8 PREFIX=   8
> valcod:          0 zcor:  0 avg-smp: N
> start yyddd: 2008260  start time:162810  start scan:  818
> lcor: 9601  ecor:  9601  bytes per pixel: 2  ss: 74
> Resolution Factors (base=1):   Line=    1.0   Element=    1.0
> IMGLIST: done

Very good. The image is multibanded.

> Is there a way I can concatenate all of the 4km resolution channels
> into a single netCDF file in calibrated units?

Try using BAND=2 3 4 5 instead of BAND=2-5.

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: QFU-969979
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.