[gdal-dev] [1.6.0][GDALWARP] World file name is empty
didier.richard at ign.fr
Tue Feb 24 14:30:00 EST 2009
> yes that very same problem was detected in 1.6.0 as ticket
> http://trac.osgeo.org/gdal/ticket/2760 and it was fixed in both trunk and
> branches/1.6. So it will be solved in 1.6.1.
Thanks Even (I could not find it in the trac), and yes (Frank), it is
working with the trunk !
All the best,
> Best regards,
> Le Tuesday 24 February 2009 19:18:45 Frank Warmerdam, vous avez écrit :
>> RICHARD Didier wrote:
>> > Hi all,
>> > I am having the following behavior with gdalwarp (freshly compiled
>> > 1.6.0) when I am requiring to get a tfw file (former releases didn't
>> > this behavior) :
>> > $ gdalwarp ... -co "TFW=YES" in.tif out.tif
>> > "out.tif" and ".tfw" files are generated (before 1.6.0, I got
>> > and "out.tfw")
>> > If I remove the -co "TFW=YES", only the "out.tif" is produced. Then,
>> > $ gdal_translate -co "TFW=YES" out.tif out2.tif
>> > "out2.tif" and "out2.tfw" are generated as expected.
>> > I noticed that osFilename is empty in WriteGeoTIFFInfo() function.
>> > A workaround solution (for me only) was to add :
>> > poDS->osFilename = pszFilename;
>> > at line 5420 of GTiffDataset::Create() function in geotiff.cpp.
>> > Did anyone else face this behavior ?
>> > Should I put a ticket (I didn't find such a report in the trac) ?
>> I was unable to reproduce this problem and it appears that
>> GTiffDataset::Create() does assign osFilename with pszFilename fairly
>> prominately in trunk and 1.6 branch. I suspect this is a problem
>> already noticed and fixed. I'd appreciate it if you could confirm the
>> behavior no longer occurs for you with trunk (or 1.6 branch if that is
>> convenient for you to build from). If the problem persists, then filing
>> a ticket would be appropriate.
>> Best regards,
RICHARD Didier - Chef du pôle technique du Géoportail
2/4, avenue Pasteur - 94165 Saint Mandé Cedex
Tél : +33 (0) 1 43 98 83 23
More information about the gdal-dev