[gdal-dev] ECW writing (was GTiff optimisation)

[Jean-Claude Repetto]

Le 01/09/2011 14:12, Even Rouault a écrit :

> I've just commited a new changeset. Now the support for updating the header info
> has been successfully tested on Linux 64bit with 3.3 SDK, Windows 32bit with 3.3
> SDK and Windows 32bit with 4.2 Read-Only SDK.
>
> At first, I had an issue with 4.2 Read-only SDK because the new functions used
> were not in the header file where they used to be in the 3.3 SDK. But they are
> luckily located in a new header file. So the Read-only SDK is a bit more than
> read-only...

Hi Even,

I have tested gdal_edit, here are a few comments :

- The -tr option doesn't work, or I don't understand how to use it :
$ gdal_edit.py -tr 10 10 France.ecw
Traceback (most recent call last):
   File "/usr/share/gdal/samples/gdal_edit.py", line 152, in <module>
     sys.exit(gdal_edit(sys.argv))
   File "/usr/share/gdal/samples/gdal_edit.py", line 132, in gdal_edit
     gt = ds.GetGeoTransform(gt)
UnboundLocalError: local variable 'gt' referenced before assignment

- gdal_edit reports no error when the parameters are wrong :
$ gdal_edit.py -mo KJHJKHJKHJ=GKFLLLMM France.ecw

- It would be nice if gdal_edit could display the current parameters 
when called without options.
Example :
$ gdal_edit.py France.ecw
Datum = NTFPARIS
Projection = LM1FRA2D
Origin = (35000.000000, 2700000.000000)
Pixel Size = (50.000000, -50.000000)
Corner Coordinates:
Upper Left = (35000.000000, 2700000.000000)
Upper Right = (1085000.000000, 2700000.000000)
Lower Left = (35000.000000, 1650000.000000)
Lower Right = (1085000.000000, 1650000.000000)

- Does gdal_edit work for other file formats, such as GeoTiff ?

Jean-Claude