Skip to content

Support of Envi format despite the eventual presence of aux.xml files #43

@aloboa

Description

@aloboa

I fully agree with:

Despite of all drawbacks (in my opinion too many), the ENVI Header file keeps to be a standard in the Imaging Spectroscopy Community to describe image metadata. So we need to support it and be able to take into account information describe in https://www.l3harrisgeospatial.com/docs/enviheaderfiles.html

(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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions