11-12-2017 06:12 AM
11-14-2017 09:33 AM
What version of ERDAS IMAGINE are you using? Did you change your image in any way? For example, did you add or remove layers from the image? If the number of bands has changed in your image then you will be unable to associate it with the original signature file.
After you associate your image with the signature file again, save the signature file and close the Signature Editor dialog. Start a new session of ERDAS IMAGINE and try to create a new signature again.
Hexagon Geospatial Support
10-18-2018 05:50 PM
Hi Hexagon Staff
I am posting on here on behalf of my remote sensing teacher and class of 16 students. We currently have ERDAS Imagine 2015 and 2018 32 and 64 bit versions. More specifically:
2018 Version 16.5.0 and build 852
We are having the same issue of undertaking a supervised signature classification by collecting signatures, then closing the session and re-opening it, and having issues with the signature file not associating with the exact same image used during signature collection. We have found, at times, collecting another signature does work to re-associate the file with the image, however this does not work every time. We have tried, prior to this, the conventional and advised strategy to re-associate the file with the image using the Image Association tool and saving and closing then re-opening. Still, this does not solve the issue of signature file not associating to the correct image.
We are wondering if there is an update for our version due to a possible software glitch or error we must know about?
Any advice would be much appreciated.
Has this query been answered? I too have a class of ~40 students and this is happening to almost all of them using ERDAS 2018, 64 bit. I can confirm that the image was not changed in any way during this process. Nor was it moved from its original location.