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

[Frank Warmerdam]

Hermann Peifer wrote:
> On 04/10/2010 16:31, Even Rouault wrote:
>>
>> This raises quite a few questions :
>> * what is a standard grid ?
> 
> Ours starts at 0,0, then goes in all directions with the given tr
> 
> 
>> * what syntax would you imagine to pass to gdal utilities to define 
>> how you want
>> the rounding ?
> 
> Some creation options like standard=yes, standard_origin=0,0
> 
>> * do you want to round/ceil/floor ? or so that the adjusted extent 
>> includes the
>> exact extent ? or so that the adjusted extent is contained inside the 
>> exact
>> extent ?
> 
> The adjusted extend includes the exact extent.
> 
>> * which gdal utilities would be impacted ?
> 
> All the ones that create new raster files: gdal_rasterize, 
> gdal_translate, gdalwarp, ...

Even,

I would suggest "-tap" for "target aligned pixels" to go with "-tr".  I
would think that gdalwarp, gdal_rasterize, and perhaps gdal_merge.py and
gdalbuildvrt would be appropriate applications to support this switch.

I don't see how it would be appropriate for gdal_translate.

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