Replies: 8 comments 18 replies
-
|
I don't like that. |
Beta Was this translation helpful? Give feedback.
-
|
If the GDAL/QGIS data model implies giving priority to the aux.xml file over the hdr, then the GDAL/QGIS data model is not fully supporting the Envi format and you have to choose: being respectful of the GDAL/QGIS data model or fully supporting the Envi format. |
Beta Was this translation helpful? Give feedback.
-
|
I do not have envi myself, so this will take a while. According to janzandr, it is actually easier for you to check. |
Beta Was this translation helpful? Give feedback.
-
|
FYI @jakimowb , you can install the latest ENVI on your local system and connect to the HU license server via VPN. It's not complicated, just ask Stephan Schulz for the details. |
Beta Was this translation helpful? Give feedback.
-
|
FYI: scale & offset in ENVI hdr are soon available via GDAL data model OSGeo/gdal#6444 |
Beta Was this translation helpful? Give feedback.
-
|
@jakimowb @aloboa @janzandr
i.e. the data offset values read from the header file (data offset values = {5.00000000e+000}) as seen in "Edit ENVI header". All the values described in the test header file are correctly read in the "Edit ENVI header" visualizer.
In "modern" ENVI, there is an error probably due to the image size. I don't have much experience in the IDL environment, it seems that it cannot open *.img files directly. Hope to have had helped you, P.S. all ENVI programs are version 5.0 |
Beta Was this translation helpful? Give feedback.
-
|
@Mesadova many thanks.
The ENVI format is used well beyond ENVI itself in many other software packages for HSI processing, as it is the only format able to deal with hyperspectral metadata. It is used, for example, by many hyperspectral cameras. If you come up with a better format for EnMapBox, use it, but create a good import application. |
Beta Was this translation helpful? Give feedback.
-
|
Another ENVI feature now supported by GDAL: OSGeo/gdal#3876 |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
I fully agree with:
(jakimwb dixit on 20220910 in #31 (comment))
Envi format should be supported, at least, for reading and display (including all data exploration tools), as
well as for exporting via Translate.
Supporting the envi format means taking into consideration the raw and hdr files only:
aux.xml files are not compatible with the envi format because the user relies on the hdr.
Whenever an image in envi format is displayed in EnMapBox, the eventual aux.xml file should be ignored. If as a consequence of QGIS and/or GDAL oddities an aux.xml file is created for an image in envi format, that file should be automatically deleted when the image is removed or EnMapBox closed.
In case automatic deletion of aux.xml files is not possible or would create worse problems, at least warn the user at reading and writing images in Envi format that he/she must be aware of the eventual presence of aux.xml files that could interfere with the .hdr file.
Beta Was this translation helpful? Give feedback.
All reactions