allow hubflow.core.ClassDefinition to use none-zero based classification scheme
Issue #508
resolved
hubflow.core.ClassDefinition
assumes classes are labeled starting from zero (like assumed by GDAL), e.g. 1st class is labeled with raster value = 1, 2nd class value = 2 and so on.
It would be nice to allow for class definitions with explicite labels, similar to the QGIS Paletted raster renderer or the QPS widget to define a ClassificationScheme:
Comments (2)
-
-
- changed status to resolved
resolves
#508→ <<cset ef32c8b00aad>>
- Log in to comment
You can now use the ids keyword to autofill the inbetween classes:
results in: