[Gdal-dev] Error appears in 1.4.3 which wasn't in 1.4.2

[Frank Warmerdam]

Seth Price wrote:
> I have another bug for you guys. This seems to have appeared in 1.4.3. 
> It seems to be having a problem with my '-dstnodata "0 0 20"' option. 
> With the current version, GDAL errors out and produces a 4KB GeoTIFF. 
> With v1.4.2, no error is produced and the GeoTIFF is as expected.
> 
> Am I doing everything right here?
> 
> v1.4.2:
> $ ./gdalwarp -dstnodata "0 0 20" -of GTiff -ts 256 256 -t_srs 
> '+proj=merc +a=6378137.0 +b=6378137.0 +wktext +units=m' -te 
> -8233185.1903991 1110477.1468928 -8228293.220589 1115369.1167029 
> N010W074_x1.merc.tif 1_03868.srs.tif
> Creating output file that is 256P x 256L.
> Processing input file N010W074_x1.merc.tif.
> :0...10...20...30...40...50...60...70...80...90...100 - done.
> 
> v1.4.3:
> $ ./gdalwarp -dstnodata "0 0 20" -of GTiff -ts 256 256 -t_srs 
> '+proj=merc +a=6378137.0 +b=6378137.0 +wktext +units=m' -te 
> -8233185.1903991 1110477.1468928 -8228293.220589 1115369.1167029 
> N010W074_x1.merc.tif 1_03868.srs.tif
> Creating output file that is 256P x 256L.
> Processing input file N010W074_x1.merc.tif.
> ERROR 1: Invalid nBandCount or bMaskIsFloat argument in SourceNoDataMask

Seth,

There were some changes with regard to -dstnodata handling which
have apparently had unexpected side effects.  Could you file a
bug report including an input data file (or at least a gdalinfo
report of one) so we can reproduce this?

Thanks,
-- 
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | President OSGeo, http://osgeo.org