Can you confirm that the WV-2 NITF dataset can be calibrated using the ENVI Radiometric Calibration tool in the application?  If so, then it should be possible to use the task with your dataset.  But it would be helpful to confirm if ENVI is reading the appropriate metadata for calibrating your file.

<p>Is there a specific way that you'd like me to check that for confirmation? I can confirm that the ENVI Radiometric Calibration GUI accepts the NITF file and IMD metadata for processing. As for the ENVITask function, adding the IMD information to the raster.metadata appears to work successfully. However, we've had to manually extract the calibration factor and effective bandwidth for each band from the IMD file because we are not aware of another method by which to do so within the Task.</p>

<p>That is good.&nbsp; It means ENVI is automatically reading all of the metadata from the file, including the metadata needed to calibrate the file.&nbsp; It should work the same with the API.&nbsp; I used the first code example from the ENVI Help for ENVIRadiometricCalibrationTask, using the .TIL as the input file (the data file is NTF and there is an IMD) and output using the default parameters.&nbsp; The result is a calibrated radiance image of the first image segment:</p> <p>Task.Input_Raster = Raster[0]</p> <p>I could have set the output to be TOA reflectance as well using:</p> <p>Task.Calibration_type=1</p> <p>It was not necessary to extract any information from the IMD in this case to perform the calibration.&nbsp; </p>

<p>The line Raster = e.OpenRaster(File) using the .TIL as my File gives me the error:</p> <p>"File does not appear to be a valid NITF file"</p> <p>When I unzip the .tar file associated with the .ntf, the .til file is stored inside two newly created folders, and the .til contains reference to an .ntf filename similar to the file I unzipped, but without the "WV02_" filename prefix, and a new suffix. In other words, the .til file is calling a different filename than the original .ntf file,&nbsp;which appears to be why IDL can't find the file. How did you avoid that problem?</p>

My file is not stored that way and I can't say I have seen that be the common case for WV data.&nbsp; The .til, data file (nitf or tiff) and all metadata are in a single folder for the MS and a separate folder for the Pan.&nbsp; Was this data pre-processed by a different data provider than Digital Globe?&nbsp; What if you put them all in the same folder with the same data file name as referenced in the TIL?

<p>Oh I see. Yes, our files were delivered from a different provider. That's the problem. Nevertheless, I was able to manually change the file search parameters and process them with this task. Thanks for your help!</p>