Combination View Flat View Tree View
Threads [ Previous | Next ]
Change of radiance values when bands exported to GeoTiff
toggle
I have been trying to use VISAT to reproject MERIS SMILE-corrected radiances, and cloud probabilties to GeoTiff. When I export the 15 MERIS bands, and then import into Idrisi, the radiance values are rescaled to a very large range. However, if I delete all but one band, and export just that one, the radiance values in the GeoTiff file (read in Idrisi) are not altered. I realize that VISAT may select a new data type to accomodate differences among the bands in the product, but in this case, I assume all numbers are the same data type.

Can anyone tell me what I am doing wrong?
Flag Flag
RE: Change of radiance values when bands exported to GeoTiff
3/18/10 9:04 AM as a reply to Greg K. McCullough.
Hello Greg,

When we export multiple bands to GeoTIFF we try to find the smallest data type in which all bands fit, because in GeoTIFF all bands must have the same data type.
I first thought that it has something to do with scaling factor and offset (see this entry), but after reprojecting scaling and offset are applied to the bands.

What is the value range of the bands in Idrisi?

best wishes
Marco
Flag Flag
RE: Change of radiance values when bands exported to GeoTiff
3/18/10 7:24 PM as a reply to Marco Peters.
Thanks for the response.

The original values are radiances; e.g. band 7 values range from 6.7-249.2. The output as Idris reads it is 0-1,132,015,616.

In this case, I deleted all bands from the SMILE product except 7,8,9 and 10, and exported the product containing only these 4 bands to GeoTiff.
Flag Flag
RE: Change of radiance values when bands exported to GeoTiff
3/19/10 9:01 AM as a reply to Greg K. McCullough.
I don't know what's going wrong.
The data type of the bands should be Float32. May be Idrisi is interpreting this wrong. With Envi we are able to read them correctly.

Can you upload such a GeoTIFF somewhere, so that I can get it and investigate the data?

best wishes
Marco
Flag Flag
RE: Change of radiance values when bands exported to GeoTiff
3/21/10 10:36 PM as a reply to Marco Peters.
I placed zipped sample files on the web in a freeware filesharing sited called 4shared. You should be able to access them via the links below.

The original smile-corrected (& reprojected to utm) product is in
http://www.4shared.com/file/246284007/71375b68/BERENS090912_smile-correctedre.html

Two exported tifs are in
http://www.4shared.com/file/246282716/3f0f13e6/BERENS090912_exported_tifs.html

One tif contains all 15 radiance bands (but not the flags and detector index bands, because I thought they miight be part of the problem.
The other tif contains only band 15.

When I import the latter tif into Idrisi, I get correct numeric values, e.g. for band 15, values range from 0 - 119.2 mW/sr/m2/nm.

When I import the former file containing all 15 radiance bands, for band 15, values range from 0 - 1122978360.

I also included in the zip file the two Idrisi raster files for band 15.

I hope you can make sense of it!

Thanks, Greg
Flag Flag
RE: Change of radiance values when bands exported to GeoTiff
3/22/10 10:39 AM as a reply to Greg K. McCullough.
We have tested the GeoTIFF files you've provided with ENVI. The value ranges are correct in both cases. Probably Idrisi can't handle the case correctly if a GeoTIFF contains multiple bands. May be it tries to to interpret it as RGB or it interprets the Float32 data as Int32. Maybe you have to configure the reading process somehow or ask the support of Idrisi. Maybe they can help you.
If you get an answer it would be nice when you let us know.

best wishes
Marco
Flag Flag
RE: Change of radiance values when bands exported to GeoTiff
3/23/10 12:06 AM as a reply to Marco Peters.
Thanks for looking into it, Marco.

I will try Idrisi and let you know if they can help me.

Greg
Flag Flag

 

Welcome to the BEAM Forum!

We encourage you to sign in our forum and participate in the BEAM community. The forum is maintained by the BEAM project team who will most likely answer your questions within 24 hours (except during common holidays) - if not done by other community members. Collaborate, share your knowledge and learn from other users!

If you don't find what you are looking for, please also consider the following external forums: