Global Mapper 24.0 and 24.1 do not read ENVI .IMG/HDR files properly anymore

danielek

Hello -

All the satellite images in ENVI img format were perfectly read until v23. In v24, the satellite images are still properly referenced but only one corner of the image is displayed and it is repeated several times over the whole image width (see the attached screenshot).

The solution I found is to change the img format to a standard format, such as tiff, in ENVI, but in spite of being time consuming when tens of images are concerned, I have identified two annoying consequences :

• it requires twice more storage space
• The customizable name of the bands in GM are not read from the ENVI header file (hdr) any longer. This was very useful when the image has many bands, for instance it made it possible to insert band wavelength in band name (like in the screenshot below). There is I think no way (are there?) to change band names in GM for vizualization in the layer Options>Band Setup box, which are not informative and sometimes confusing.

Is there any plan to make ENVI image format compatible with GM again?

Suggestion: Could changing band names manually in the Options>Band Setup be implemented in a future release?

Thanks

bmg_mike

Hello,

Can you provide a sample ENVI IMG/HDR that does not load correctly in Global Mapper v24.1? It certainly wasn't our intention to break that, so it should be pretty easy to fix it. Unfortunately we don't have any ENVI IMG/HDR samples that demonstrate the issue.

I have also created a todo item for allowing customization of band names.

Thanks,

Mike

Global Mapper Guru

danielek

Mike,

Looking forward to the band name customization some time in the future! How luxury it will be.

I have uploaded an ENVI image there:

https://uncloud.univ-nantes.fr/index.php/s/cJsY5JPGZCRrdE2 HDR file

https://uncloud.univ-nantes.fr/index.php/s/etdyFAdwNNKwzw6 IMG file

Thanks,

daniel

bmg_mike

Hi Daniel,

I haven't been able to reproduce any issues with the sample that you provided. It looks like below in v23.0 and v24.1. What does this image look like on your machine?

Thanks,

Mike

Global Mapper Guru

danielek

Hi Mike,

The image below is what I get in my algorithm.

However, I removed all the other files from the glw file, keeping only this one, and it gives the right result with v24.1, the same as what you get. The problem is therefore inside the gmw file, which works fine with v23 but for some reason does not open the img files properly in v24.

Upon opening in v24, the gmw file also starts with giving three times an error message: "Would you like to cancel the entire operation?". Three times is not related to the number of img files, I have tens of img files in this gmw file. But it is also an error that does not appear in v23.

I generated several, smaller and smaller gmw files from the original one (517 Mb), gradually removing vector files, png and tif files, etc. to detect at which point it stop failing. I ended up with this file, which includes img files only, some of them display correctly and others do not:

https://uncloud.univ-nantes.fr/index.php/s/RiDsF5MpfDYJ2H9

The error message above does no longer appear with this test12.gmw file though.

I did not attach the linked files, but from the file structure perhaps can some idea why the img files do not open properly be inferred.

Thanks,

daniel

bmg_mike

Hi Daniel,

Thanks for the information, I was able to reproduce the issue with the data file that you provided by loading the same file about 10 times within a single workspace. Internally, when over some number of GB of image files are loaded, we switch to a tile-based approach rather than mapping the entire file into memory, and that tile-based logic was incorrect for BSQ-organized images like your ENVI IMG files.

I have fixed the issue, so tomorrow's v24.1.x daily build at https://www.bluemarblegeo.com/products/global-mapper-daily-builds.php should display them properly regardless of how many are loaded.

For your 'Would you like to cancel the entire operation' issues, if you can provide an errlog.txt when this happens it may provide a clue. It sounds like some load is silently cancelling internally, resulting in the script processing asking you if you want to cancel the entire operation.

Thanks,

Mike

Global Mapper Guru

danielek

Mike, thanks, the files open well.

As to the recurring 'Would you like to cancel the entire operation', they are still there and the error log retrieves 3 failures:

[04/04/2023 19:14:06] [DEBUG] Failed to initialize GeoCalc: Cannot find the path to the Blue Marble Geographic Calculator executable folder. Either the application is not installed on this computer or it is installed in a non-standard location.

[04/04/2023 19:14:06] [WARNING] Failed to get TRIM property for physical drive '\\?\PhysicalDrive0' (volume '\\.\C:'): <Incorrect function.>

[04/04/2023 19:14:18] [WARNING] Failed to get TRIM property for physical drive '\\?\PhysicalDrive2' (volume '\\.\D:'): <The parameter is incorrect.>

The three errors are close in time and close to the GM launch time, in agreement with the timing of the error message.

C: is the program files drive, D: is the external drive where all the Global Mapper data files are located, and none are SSB. Correct that GeoCalc is not installed, should I do so?

errorlog_04-04-2023.txt

bmg_mike

Hi Daniel,

You do NOT need to install GeoCalc, that is just a Debug log message to let us know that GeoCalc wasn't found, which is normal. You can also ignore the 'Failed to get TRIM property' message, that is also normal for non-SSD drives.

I have added a display when you load a .gmw file and commands are cancelled listing each script command from the .gmw that was cancelled so we can pinpoint what is actually cancelling as there wasn't anything in the log. If you get the 24.1.x daily build tomorrow it should show a message box at the end of the script load indicating which commands cancelled and triggered the 'cancel all' prompt.

Thanks,

Mike

Global Mapper Guru

danielek

Hi Mike,

1. The log obtained at the end of script opening shows that the errors refer to three Landsat Geocover2000 mosaics:

-----------------------------------------------------------

The following errors were generated loading the workspace file:

CANCELLED command:

IMPORT AUTO_CONTRAST="NO" CLIP_COLLAR="NONE" CONTRAST_MODE="NONE" CONTRAST_SHARED="YES" \

FILENAME="D:\Ethiopie\_GIS SHARED DATA\MrSID\Geocover2000\N-37-10_2000\N-37-10_2000.sid" \

HIDDEN="YES" LABEL_FIELD_FORCE_OVERWRITE="NO" LABEL_FORMAT_NUMBERS="YES" LABEL_PRECISION="-1" \

LABEL_REMOVE_TRAILING_ZEROS="YES" LABEL_USE_SCIENTIFIC_NOTATION="NO" LAYER_GROUP="Geocover 2000" \

SAMPLING_METHOD="NEAREST_NEIGHBOR" TEXTURE_MAP="NO" TYPE="MRSID"

CANCELLED command:

IMPORT AUTO_CONTRAST="NO" CLIP_COLLAR="NONE" CONTRAST_MODE="NONE" CONTRAST_SHARED="YES" \

FILENAME="D:\Ethiopie\_GIS SHARED DATA\MrSID\Geocover2000\N-38-10_2000\N-38-10_2000.sid" \

HIDDEN="YES" LABEL_FIELD_FORCE_OVERWRITE="NO" LABEL_FORMAT_NUMBERS="YES" LABEL_PRECISION="-1" \

LABEL_REMOVE_TRAILING_ZEROS="YES" LABEL_USE_SCIENTIFIC_NOTATION="NO" LAYER_GROUP="Geocover 2000" \

SAMPLING_METHOD="NEAREST_NEIGHBOR" TEXTURE_MAP="NO" TYPE="MRSID"

CANCELLED command:

IMPORT AUTO_CONTRAST="NO" CLIP_COLLAR="NONE" CONTRAST_MODE="NONE" CONTRAST_SHARED="YES" \

FILENAME="D:\Ethiopie\_GIS SHARED DATA\MrSID\Geocover2000\N-38-15_2000\N-38-15_2000.sid" \

HIDDEN="YES" LABEL_FIELD_FORCE_OVERWRITE="NO" LABEL_FORMAT_NUMBERS="YES" LABEL_PRECISION="-1" \

LABEL_REMOVE_TRAILING_ZEROS="YES" LABEL_USE_SCIENTIFIC_NOTATION="NO" LAYER_GROUP="Geocover 2000" \

SAMPLING_METHOD="NEAREST_NEIGHBOR" TEXTURE_MAP="NO" TYPE="MRSID"

----------------------------------------------

2. Moreover, the standard errlog.txt file does not yield any error with the Geocover2000 files, as can be read in this log extract:

---------------------

[04/04/2023 19:14:20] [DEBUG] Load of <N-37-10_2000.sid> from file [D:\Ethiopie\_GIS SHARED DATA\MrSID\Geocover2000\N-37-10_2000\N-37-10_2000.sid] SUCCEEDED in 0.58 s [0x000000000BCE2360]

[04/04/2023 19:14:24] [DEBUG] Load of <N-38-10_2000.sid> from file [D:\Ethiopie\_GIS SHARED DATA\MrSID\Geocover2000\N-38-10_2000\N-38-10_2000.sid] SUCCEEDED in 1.11 s [0x000000000BCE4900]

[04/04/2023 19:14:26] [DEBUG] Load of <N-38-15_2000.sid> from file [D:\Ethiopie\_GIS SHARED DATA\MrSID\Geocover2000\N-38-15_2000\N-38-15_2000.sid] SUCCEEDED in 0.48 s [0x000000000C098F60]

--------------------------

3. I made a gmw file that contains only one of the three problematic .sid files. It generated the same error message, so it seems related to the image format. The SID file is here:

https://uncloud.univ-nantes.fr/index.php/s/dpXrTKroNf3iArH

4. I transformed the SID file in (3) to jp2 and tif. There is no "Would you like to cancel the entire operation" any longer (but te fils are 5 to 32 times larger).

5. Strangely enough, Geocover1990 mosaics in the same SID format do not give a "Would you like to cancel the entire operation" message. One of these images is here:

https://uncloud.univ-nantes.fr/index.php/s/N3qA4Hpyx9mmRfi

In summary, some SID images are the cause of the error message, but some others are not, and the data in the bad SID files are ok enough to be correctly translated to jp2 and tif.

thanks,

daniel

bmg_mike

Hi Daniel,

I was able to track down and fix the issue based on your sample files. Tomorrow's v24.1.x daily build should no longer show the 'cancel entire operation' prompt.

Thanks,

Mike

Global Mapper Guru

danielek

Yes it works. Many thanks for your time!

daniel