[gdal-dev] Re: gdal_rasterize -tr and -te

Frank Warmerdam warmerdam at pobox.com
Wed Oct 6 10:34:35 EDT 2010


Hermann Peifer wrote:
>> $ 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.
...
> 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.

Herman,

Were you using GDAL 1.7 last week?  The above is related to the OGR SQL
upgrade - it is now more picky about types in expressions.   I may need
to consider some sort of adjustment.

Best regards,
-- 
---------------------------------------+--------------------------------------
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    | Geospatial Programmer for Rent



More information about the gdal-dev mailing list