Open janzandr opened 3 weeks ago
@jakimowb it is not really clear what the current logic is, by just looking at the dialog:
I guess you just take the first pixel you find for a polygon (?). Or do you aggregate all the pixels? I would suggest to extract all the pixels -> this would fix the bug.
Final result should look like this:
Also, the progress bar isn't updating correctly, because of a TypeError:
TypeError: setValue(self, progress: int): argument 1 has unexpected type 'float'
https://github.com/EnMAP-Box/enmap-box/issues/919#issuecomment-2151747525
@janzandr is this the right screenshot? In case of the land_cover_potsdam_point
dataset there is no need to handle multiple profile per (polygon)-geometry.
#919 (comment) @janzandr is this the right screenshot? In case of the
land_cover_potsdam_point
dataset there is no need to handle multiple profile per (polygon)-geometry.
The Screenshot is showing the wrong layers. I used the enmap_potsdam and polygons.
When importing all profiles covered by polygons, most of the pixel profiles are missing in the library:![image](https://github.com/EnMAP-Box/enmap-box/assets/45030715/4aa84299-0cb3-410a-8f3c-2ed59bcd1be1)
E.g. for this forest patch, I only get a single pixel profile:![image](https://github.com/EnMAP-Box/enmap-box/assets/45030715/018ac8a5-b611-4c84-8bca-fa889dab4c53)
I would expect get all the pixel profiles covered by the forst patch.