This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
re: > * > IMGCOPY > G13/VIS27APR11.29 > > IMGCOPY: Destination dataset name must be > entered > IMGCOPY: > done First, it looks like your IMGCOPY command was on two separate lines. Like I noted in a previous email, a McIDAS command has to be on a single line. Second, the syntax for IMGCOPY can be seen from the built in help: HELP IMGCOPY IMGCOPY -- Copies image data from a server IMGCOPY sdataset ddataset <keywords> Parameters: sdataset | source ADDE dataset name and position; specify as alias.position or group/descriptor.position; to use default position, either enter "0" or omit .position portion (no def for alias or group/descriptor, def=0 for position) ddataset | destination ADDE dataset name and position; specify as alias.position or group/descriptor.position; only positive integers (absolute positions) or the default are valid for the position number; to use the default position, omit the .position portion (no def for alias or group/descriptor, for position def=the position following the most recent image) Keywords: ********************* Image Positioning Keywords *********************** LATlon=lat lon | latitude and longitude of sdataset image to place at ddataset image location specified in PLACE keyword LINele=line ele sys | line and elem ... You will see that IMGCOPY needs to have input AND output datasets specified. On top of that, the output image dataset must be of type AREA, and you must have created it before you can use it. So, let's create a dataset whose members are all possible images in AREA file format: DSSERVE ADD MYDATA/IMAGES AREA 1 9999 "All AREA files After this runs successfully, you will have a dataset that you can use for IMGCOPYs, etc. Next, let's IMGCOPY a section from the original image dataset into a new element of the output dataset MYDATA/IMAGES: IMGCOPY G13/VIS27APR11.29 MYDATA/IMAGES.3000 LATLON=33 87 MAG=1 -2 SIZE=500 750 Next, take a look at the image just created: IMGLIST MYDATA/IMAGES.3000 FORM=ALL For good measure, let's create a second copy that is identical to the first copy: IMGCOPY G13/VIS27APR11.29 MYDATA/IMAGES.3001 LATLON=33 87 MAG=1 -2 SIZE=500 750 Now, let's remap one of your effective radius images into the first copy created by IMGCOPY: IMGREMAP G13/EFFRAD.56 MYDATA/IMAGES.3000 SSIZE=ALL Take a look at the result of the remap: IMGLIST MYDATA/IMAGES.3000 FORM=ALL You should note that the listing does not reflect header information pertinent to the effective radius image. This can be changed with the IMGCHA command. We will address that later. Finally, display the result of the remap: IMGDISP MYDATA/IMAGES.3000 LATLON=33 87 re: > IMGREMAP > G13/EFFRAD.56 > IMGREMAP: Invalid destination dataset name= Again, it looks like you did not specify everything on the same command line. re: > I Havent got to that IMGOLAY since the IMGCOPY COMMAND AND IMGREMAP HAS NOT > WORKED. WHY IS THAT THE CASE? See above. re: > FROM THERE I WILL TRY THE IMGOLAY COMMAND. Please try the above making sure that the various command invocations are contained on a single line. re: is there some reason that you are reluctant to provide me with the images I have requested? > *I will ask the professor once I complete this last step of overlaying. It would greatly help me to help you if I had the images you are trying to combine/overlay. Please ask the professor as soon as possible. > So sorry it took me so long to answer that question. No worries. 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: BJT-176673 Department: Support McIDAS Priority: Normal Status: Closed