X
PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 21 Feb 2023 01:03 PM by  Krista West
ENVI vs. ENVI Classic: Identical Data but Different Outputs
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages

Krista West



New Member


Posts:8
New Member


--
21 Feb 2023 08:33 AM
    Using the same input Collection 2, Level-2 Landsat data set (spatially and spectrally subset, values below 0 and above 1 masked, both WGS 1984 UTM Zone 11N, pixels reportedly 30 m) to perform Linear Spectral Unmixing, I observe different ROI pixel coverage and reported areas depending on whether I use ENVI Classic + IDL (64-bit) or "New" (ENVI 5.6.3 + IDL 8.8.3, 64-bit).

    When I use the ROI Tool with the three ROIs that have 6, 6, and 3 pixels (which I created in ENVI "New"): When I apply those ROIs to the aforementioned Landsat file in ENVI Classic, I see that those 6, 6, and 3 pixel grouping line up with the Landsat pixels and the ROI Tool reports the expected areas of: 5400, 5400, and 2700 sq m, respectively. When I apply those same ROIs to the same Landsat file in ENVI "New," the ROI Tool reports ROI coverage of 6, 6, and 3 pixels but also "pixel counts" of 21, 20, and 9 respectively, and the ROIs have different shapes in the image (e.g., polygons of three pixels instead of a single pixel). Additionally, the imagery does not have defined pixel edges in ENVI "New" (the way it does in Classic), so I don't see that ROI pixels are lining up with image pixel edges.

    Unsurprisingly, when I run Linear Spectral Unmixing and output the values from my generated reference sampling grids, I receive slightly different results from ENVI Classic than "New."

    I understand that ENVI Classic is being phased out, so I hesitate to use it and that is why I have been doing my work in the "New" ENVI. However, I see the visuals that I expect in Classic, and now I am worried about the data outputs from ENVI "New."

    Have you come across these disparities between the two? What is your recommendation regarding which to trust moving forward?

    MariM



    Veteran Member


    Posts:2396
    Veteran Member


    --
    21 Feb 2023 11:44 AM
    Hi Krista,
    The main difference between classic and ENVI ROI is that ENVI ROIs are geometry-based and map aware while Classic ROIs are pixel based. This required a different selection process for what is 'inside' vs 'outside' a polygon and is discussed in the documentation here:
    https://www.l3harrisgeospatial.com/docs/backgroundroipixelinclusion.html

    If you draw your ROIs as points in ENVI and export these to Classic, do you see a difference in the number of pixels selected?

    Krista West



    New Member


    Posts:8
    New Member


    --
    21 Feb 2023 01:03 PM
    Hello Mari,
    Thank you very much for your response, and for sharing the ROI Pixel Inclusion Background documentation.

    When I draw ROIs as points in ENVI and export them to the Classic .roi file, I see the same number of pixels (and same areal coverage) reported. I opened the files in both ENVI and Classic.

    I also created another ROI file in Classic and opened it in ENVI -- I see the same number of pixels and area. To test it further, I saved the .roi file as a .xml file -- same number of pixels and area again.

    Now I'm confused. When I look back at the ROI files that prompted me to reach out to the forum this morning, I see that the .roi file from Classic has the expected number of pixels an area. But it's the .xml file (created by File > Save As... > .xml) that shows an increase in the number of pixels (and area). Do you know why I might have run into an issue (error?) with that set of ROI files, but cannot recreate the problem today?
    You are not authorized to post a reply.