On 06/10/2010 15:20, Hermann Peifer wrote:
On the other hand... The new, target aligned tiffs do only have NODATA values, which seems to be related to ERROR 1: $ gdal_rasterize --debug on --config GDAL_CACHEMAX 2000 -ot byte -a_nodata 0 -co compress=lzw -tr 255 255 -tap -l lu001l_luxembourg -burn 1 -where CODE=111 lu001l_luxembourg.shp out.tif OGR: OGROpen(lu001l_luxembourg.shp/0x1978ae0) succeeded as ESRI Shapefile. GDAL: QuietDelete(out.tif) invoking Delete() GDAL: GDALOpen(out.tif, this=0x19cbe00) succeeds as GTiff. GDAL: GDALDefaultOverviews::OverviewScan() GDAL: GDALClose(out.tif, this=0x19cbe00) GDAL: GDALDriver::Create(GTiff,out.tif,224,321,1,Byte,0x1979ab0) ERROR 1: Type mismatch or improper type of arguments to = operator. GTiff: Adjusted bytes to write from 8064 to 7392. GDAL: GDALClose(out.tif, this=0x19caf40) GDAL: GDALDeregister_GTiff() called. I am not sure if this new ERROR is related to your patch or some other changes which came through checking out -r 20770.
I see: ERROR 1 can be avoided by using: -where CODE=\'50000\' (CODE is a string field). In any case: I rasterize via a shell script and I did not get the same error when running the same script last week.
Hermann _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
