EnMAP-Box/enmap-box

Spectral library axis flipped

Closed this issue · 6 comments

Dear Team,
I am using the Tyrol_Austria_L2A example dataset from Enmap.
Everytime I try to create a spectral library, my axis are flipped i.e. x axis is band number and y axis is wavelength.
I have installed and reinstalled the enmap box a couple of times and I still get the same problem.

When I use the default example data from enmap box the axis are fine.

I am using the version 3.13.3.
Enmap Tyrol (please see x axis in the spectral library)
enmap_tyrol

EnMap box default example Potsdam
enmap_default_example

  1. Your plot is not correct, even with the Potsdam dataset:
    image
  2. I can't reproduce the problem on my system.
  3. Before we start narrowing down the problem, please make sure that you are using a recent QGIS 3.34+ together with the latest EnMAP-Box v3.14, and try again.

Dear Andreas,

I have updated now to a QGIS version of 3.36.3 and enmap box of 3.14.3. I still get the same .
The dataset I am using is freely available here - https://www.enmap.org/data_tools/exampledata/. I have downloaded the Tyrol, Austria L2A data.

I have tried the following

1. Raster input image using "Add data source" option .

The image I selected is "ENMAP01-____L2A-DT0000001049_20220612T105735Z_028_V010303_20230922T131826Z-SPECTRAL_IMAGE:.

enmap_tyrol

I even changed the x axis using the following tool

enmap_x_axis

2. using metadata - I get error which I am unable to understand how to debug it .

enmap_l2a_metadata

3. the default potsdam example looks like this now with upgraded enmap 3.14

enmap_default_example

Is my input image wrong? Also it would be very helpful if you can point out to any updated learning materials as the tutorials and youtube videos I checked do not show how to work with downloaded enmap data but rather only default examples in the previous versions of the software.

You need to import the EnMAP product (otherwise, the wavelength metadata is missing):
Menu > Project > Add product > EnMAP L2A

@ecoinfo-netra, sorry, I just realized, that you did use the product import algorithm.
The error you show is a known issue, which is caused by the very long file path:
image

You have to move the product folder, e.g. to C:\data<product folder>

Yes, thank you. Now it works.

Duplicate of #595.