X
PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 10 Jun 2013 02:50 PM by  anon
Issues with SP3 and Landsat 8
 3 Replies
Sort:
You are not authorized to post a reply.
Author Messages

anon



New Member


Posts:12
New Member


--
10 Jun 2013 02:50 PM
    I am sure many of us have been anxiously awaiting this release. Here are a few issues I have found with some quick testing. Would love to hear what others are experiencing. Classic Interface ENVI will not open the meta file - The error message is "Problem: An error was encountered reading this file. Error: Variable is undefined: SENSOR_TYPE" Landsat calibration won't work on L8 files created via layer stacking - The error message is "Problem: Landsat Calibration only works with six bands of data with the exception of NLAPS TMS" This is curious since it WILL work with an eight-band file in the GUI version. Is this another step toward abandonment of the Classic interface? GUI Interface: When opening the meta file an error message is generated. "Internal Error: Count" A general question: Should the Cirrus band be a separate file? This is done with the pan and thermal bands and I suspect we will not use the Cirrus band for classifications or most other processing with the optical bands.

    MariM



    Veteran Member


    Posts:2396
    Veteran Member


    --
    11 Jun 2013 06:40 AM
    1. LDCM is not supported in ENVI Classic - only ENVI 5 SP3 2. I have seen this error occasionally and think it may be related to some configuration files or programs in the save_add or extensions folder. Could you try removing the .idl directory along with any programs in your \envi50\extensions folder and \envi50\classic\save_add to see if it resolves the issue? 3. Typically ENVI will open all bands with the same pixel size into one file.

    Deleted User



    New Member


    Posts:12
    New Member


    --
    11 Jun 2013 12:13 PM
    Mari, Removing the .idl folder seems to have resolved this issue. Thank you. I do believe that OLI support should be put into Classic, but I assume you (or I) don't get to make these types of decisions. Larry

    Deleted User



    New Member


    Posts:23
    New Member


    --
    12 Jun 2013 11:56 AM
    Hello, Again I agree with Larry that Landsat 8 support should be included in the Classic version. Is it possible to make a 'new feature request' for the Classic version at all? Since even within the ENVI Help, the Classic version is recommended sometimes (e.g. for creating AOIs), I think the Classic version 'deserves' to be updated still - at least until the ENVI 5 interface is loaded with all the Classic functionality. Mike
    You are not authorized to post a reply.