Open jakimowb opened 3 months ago
Hi @jakimowb, currently, the RasterReader only supports GDAL raster.
If we want to, we can also support Web Coverage Service (WCS). So far, there was no need for it.
It's not only because of WCS. There are several other data providers, e.g. for virtual rasters. Also the spectral processing widget uses its own rasterdataprovider to avoid data redundancy.
If the RasterReader supports GDAL sources only, it should be better renamed.
However, I think it would be better if it's features present a true superset of features of a standard QgsRasterLayer. It should work with any rasterlayer instance, and provides additional options in case of GDAL rasterproviders.
Yes, totally agree, but let's have a seperate Issue for each new provider, which we need/want to support.
I don't think it is necessary to create an issue for each single provider. The RasterReader just should work fine with any QgsRasterData provider. On top, it might add value in case of providers like gdal, e.g. by reading metadata from extra files. However, it should still work generically with any QgsRasterData interface.
WMS provider should work now (see #865)
@jakimowb, which provider should be implemented next? Anything urgent before the v3.14 release?
The RasterReader should generally accept all QgsRasterLayers/QgsRasterDataProviders.
I'll enhance (somewhen) the enmapbox.testing.TestObject to provide a set of rasterlayers with different providers. See #870
Waiting for enmapbox.testing.TestObject enhancement.
The RasterReader fails to read QgsRasterLayers that use other data provider than GDAL (which is the case for 6 of 7 standard QGIS QgsRasterDataProviders)
Supported QgsRasterDataProviders
gdal
virtualraster
wcs
postgresraster
grassraster
arcgismapserver
wms
The
openWithGdal
keyword seems to have no effect.How to reproduce:
relates to #764