Try setting the parameter without the '/ ' which usually is just a toggle for on/off for a parameter. Using g_levels, you want to set it to a value. For example: g_levels=64

Ok - so just to verify, I should slip in ", g_levels=64" instead of ", /g_levels=64"?

No, that would be /g_levels instead of g_levels=64. I hope that works for you. - Peg Exelis VIS

So I just put in /g_levels to turn it on? How do I specify 64 then?

Thanks for helping with figuring out the g_levels switch. It worked when I just put in "g_levels=64" without the slash. It's helped me move along a lot on my project. Once I got past that, I noticed that once my raster data passed through the Texture_CoOccur_DoIt procedure, I just got 70 back garbled blank bands, when the input data has only 5 and when using the GUI in ENVI returns five layers bands 5 bands back. What could be wrong?

Yes, the G_LEVELS keyword is an assignment to a scalar value up to 256. If you process your 70 band image in the application using quantization of 64, do you get the same results as your code? If you do not use quantization, do you get a result?

When I run it without the IDL script with 64 gray scale quantization, 5 bands go in, and 5 bands go out. Without the script nor gray quantization, the same comes out. When I did it without the gray scale quantization, I still had the same issue.

It turned out that I was using the wrong dimensions and band names for this do_it command. Removing the g_levels option didn't change anything. The only issue I have now is that when I run the script, I get an error: "File: No Carriage returns found. Unable to read the file as an ASCII file" Then I get this error: "File: pathname to input LAS file Projection: 1.000 Problem: An unknown map projection is referenced in the map projection. Unable to use". This happens earlier in the script as it reads the projection information and dimensions as it converts .LAS data into ENVI data to go through the co-occurence measures. Is this likely because I'm using Windows and it is struggling with UNIX text files?

If the file is in LAS format, it should not matter. I assume you are using ENVI_CONVERT_LIDAR_DATA_DOIT to open the file? Did you set up the omap? Are you able to successfully import the file using the interface?

I talked with the source of the files and they did something weird with the map projection data. Once I reprojected the data, it worked. Thanks for your standing by while I figured this out!