You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
janzandr opened this issue
Jun 13, 2023
· 0 comments
Labels
BugEither a bug report, or a bug fix. Let's hope for the latter!PyQGISRelated to the PyQGIS APIRastersRelated to general raster layer handling (not specific data formats)
I want to implement a custom QgsRasterDataProvider to do some on-the-fly raster processing/manipulation. It seams that the noDataValues aren't rendered correctly. NoDataValues should be transparent, instead they are rendered as normal values.
I prepared a minimalistic example reproducing the bug. The provider simply delivers data with values 0, 1, 2, and the value 1 is set as the noDataValue.
In QGIS the layer is wrongly rendered. The gray area in the middle should be transparent:
In the Layer Properties, the noDataValue is correctly displayed:
When using the Custom Transparency Options to manually mask out values of 1, it looks correct:
Steps to reproduce the issue
The minimalistic example can be executed in the QGIS Python Console:
QGIS version
3.28.7-Firenze
QGIS code revision fedae0e
Qt version
5.15.3
Python version
3.9.5
GDAL/OGR version
3.7.0
PROJ version
9.2.0
EPSG Registry database version
v10.082 (2023-02-06)
GEOS version
3.11.2-CAPI-1.17.2
SQLite version
3.41.1
PDAL version
2.5.3
PostgreSQL client version
unknown
SpatiaLite version
5.0.1
QWT version
6.1.6
QScintilla2 version
2.13.1
OS version
Windows 10 Version 2009
BugEither a bug report, or a bug fix. Let's hope for the latter!PyQGISRelated to the PyQGIS APIRastersRelated to general raster layer handling (not specific data formats)
What is the bug or the crash?
I want to implement a custom QgsRasterDataProvider to do some on-the-fly raster processing/manipulation. It seams that the noDataValues aren't rendered correctly. NoDataValues should be transparent, instead they are rendered as normal values.
I prepared a minimalistic example reproducing the bug. The provider simply delivers data with values 0, 1, 2, and the value 1 is set as the noDataValue.
In QGIS the layer is wrongly rendered. The gray area in the middle should be transparent:
In the Layer Properties, the noDataValue is correctly displayed:
When using the Custom Transparency Options to manually mask out values of 1, it looks correct:
Steps to reproduce the issue
The minimalistic example can be executed in the QGIS Python Console:
Versions
QGIS version
3.28.7-Firenze
QGIS code revision
fedae0e
Qt version
5.15.3
Python version
3.9.5
GDAL/OGR version
3.7.0
PROJ version
9.2.0
EPSG Registry database version
v10.082 (2023-02-06)
GEOS version
3.11.2-CAPI-1.17.2
SQLite version
3.41.1
PDAL version
2.5.3
PostgreSQL client version
unknown
SpatiaLite version
5.0.1
QWT version
6.1.6
QScintilla2 version
2.13.1
OS version
Windows 10 Version 2009
Active Python plugins
Coregistration
22.5.19
DataPlotly
3.9.2
ee_plugin
0.0.6
enmapboxplugin
3.13.0-alpha-0
IPyConsole
version 2.0
magnetic_bearing_measurement
0.5
nominatim_locator_filter
0.2.4
openlayers_plugin
2.0.0
qgis_stac
1.1.1
quick_map_services
0.19.33
rasterdataplotting
1.7
rastertimeseriesmanager
1.8
timeseriesviewerplugin
1.17.20210312T143004.master
vrtbuilderplugin
0.9.20210222T174536.master
zoomview
1.1.2
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.6
processing
2.12.99
sagaprovider
2.12.99
Supported QGIS version
New profile
Additional context
No response
The text was updated successfully, but these errors were encountered: