Bug report #8736
Update raster analyses: access data through raster layer instead of GDAL
|Affected QGIS version:||3.0.0||Regression?:||No|
|Operating System:||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:||fixed/implemented|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||17451|
This affects various modules, e.g. Terrain analyses. This is bad also because they cannot deal with WCS layers, and users are not warned about this.
#2 Updated by Paolo Cavallini almost 4 years ago
but I get:
Traceback (most recent call last): File "/usr/local/src/qgis/QGIS/build_qgis3/output/python/plugins/processing/gui/AlgorithmDialog.py", line 151, in accept if checkCRS and not self.alg.checkInputCRS(): File "/usr/local/src/qgis/QGIS/build_qgis3/output/python/plugins/processing/core/GeoAlgorithm.py", line 416, in checkInputCRS crs = dataobjects.getObject(item).crs() AttributeError: 'NoneType' object has no attribute 'crs'
#3 Updated by Alexander Bruy almost 4 years ago
That's correct behavior for now. While native zonal statistics was adopted to access raster data via dataprovider, Processing itself still allows only rasters loaded with GDAL provider, because almost all algorithms can work only with local files.
As temporary workaround you can use PyQGIS in Python console if necessary.