| 16 Sep 2015 02:02 PM |
|
|
Hello,
I would like to read VIIRS images (From the NOAA CLASS archive) using ENVI in batch mode. The idea is to load the image, perform bow-tie correction and then output a georeferenced TIFF file for later use. Effectively just the same procedure as File->Load with a VIIRS H5 file in the GUI program.
But I can't figure out how to do this in batch mode. IF I try:
COMPILE_OPT IDL2
e = ENVI(/HEADLESS)
VImg = e.OpenRaster(infile])
Then I get an error: "% Dataset name must be provided."
Do you know te correct procedure for reading a VIIRS image in the batch mode? A simple example would be great.
Thanks,
Simon
|
|
|
|
Deleted User
New Member
Posts:59  
| 16 Sep 2015 03:34 PM |
|
|
Hi,
You can use the ENVIReprojectGLTTask routine to open the VIIRS dataset (.h5) and to perform bowtie correction. Please see the ReprojectGLT documentation for a code example. Because HDF5 datasets contain multiple datasets within, you will need to know the raster array indices that correspond to the main image, Latitude band, Longitude band, Height band, and Quality band. The code example I pointed you to shows the case of a land surface temperature EDR dataset.
I'm a little puzzled by the error though...it seems to be looking for a specific dataset within the HDF5 file. You may need to set the DATASET_NAME keyword to e.OpenRaster to open a specific raster dataset, as shown in the ENVI::OpenRaster documentation.
|
|
|
|
Deleted User
New Member
Posts:
| 20 Sep 2015 01:58 AM |
|
|
Hi,
Thanks for the response. Your technique works and I can now generate reprojected images. However, some of the scenes produce very big output (around 70-80Gbyte) rather than the usual 65-70Mbyte. Do you have any idea why that is? I knew it was a problem in ENVI 5.0 but I thought it was fixed in 5.1 and later?
Cheers,
Simon
|
|
|
|
Deleted User
New Member
Posts:59
| 21 Sep 2015 07:31 AM |
|
|
I'm glad that you were able to create the reprojected images. I will do some research and try to track down why some of the resulting images are so big and why this issue still persists. Thanks!
|
|
|
|
Deleted User
New Member
Posts:59
| 21 Sep 2015 07:54 AM |
|
|
Ok, it appears that this is still an open issue, according to our bug-tracking system. Other customers are reporting output files that are tens of gigabytes too. It's in the engineers' queue to fix, but I will try to push it to a higher priority.
|
|
|
|
Deleted User
New Member
Posts:59
| 04 Dec 2015 08:53 AM |
|
|
I wanted to point out that this issue has been fixed. The fix will be available in the next release of ENVI.
|
|
|
|