There should be no problem declaring it as optional (it is actually optional, so it fixed the decalration)
What surprises me a bit is that when running from the toolbox, an empty string is accepted as a valid value...if it is not optional, it should complain Anyway, that's a different thing :-) Feel free to update the paramter in the algorithm to fix that Thanks! 2016-04-25 17:31 GMT+02:00 René-Luc Dhont <[email protected]>: > Hi all, > > I encountered some trouble to integrate 'GDAL - Clip raster by extent' in a > model. > > The NODATA param is described as 'Nodata value, leave blank to take the > nodata value from input' and it is not optional. There is no problem if the > algorithm is executed alone. But when we integrated 'GDAL - Clip raster by > extent' in a model with an empty value for NODATA, because the field is > empty, the algorithm can't be added. > > The easy way to fix it is to decalre NODATA param as optional. What do you > think about it ? > > Do you know other potential optional parameters ? > > René-Luc > _______________________________________________ > Qgis-developer mailing list > [email protected] > List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer _______________________________________________ Qgis-developer mailing list [email protected] List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
