Open Jonasvsl opened 4 weeks ago
@Jonasvsl @leendertvanwolfswinkel Issue was caused by the fact that raster instance was missing origin, upper_bound and pixelsize information. As a workaround set fallback raster resolution value to 1.0.
I tested it and it seems to work correctly.
However, the mentioned fallback value for the raster resolution is not filled in in the raster resolution widget, which is a bit confusing.
One thing I was wondering: What is supposed to happen if the chosen pixel size is 0? Same for when the selected CRS is "Invalid CRS". Perhaps we should not allow this? I.e. show a message when the user clicks "accept"?
I tested it and it seems to work correctly.
However, the mentioned fallback value for the raster resolution is not filled in in the raster resolution widget, which is a bit confusing.
One thing I was wondering: What is supposed to happen if the chosen pixel size is 0? Same for when the selected CRS is "Invalid CRS". Perhaps we should not allow this? I.e. show a message when the user clicks "accept"?
If pixel size is 0 then it will be calculated based on raster metadata pixelsize. If projection is invalid then there is no projection assigned to the raster task.
Added adjustments to the raster resolution widget.
@ldebek tested, please merge
When downloading this dataset via de lizard plugin: