[gdal-dev] Strange behaviour of gdal_translate with ECW on linux (libecw 3.3)

[andreaerdna]

I've done some tests using a PNG image (22080x11520 pixels, 4 bands,
469.969.142 bytes) as source dataset.


Testing Operative Systems are:

1) MS Windows 7 HP SP1 64-bit 
2) Ubuntu Linux 10.04 64-bit (kernel 2.6.32-38.83)
3) MS Windows XP Pro SP3 32-bit


Testing GDAL versions are:

1) builds for Windows from www.gisinternals.com/sdk [with related 3.3 ECW
plugin]:
GDAL 1.9.0 [64-bit] (release-1600-x64-gdal-1-9-0-mapserver-6-0-1)
GDAL 1.9.0 [32-bit] (release-1600-gdal-1-9-0-mapserver-6-0-1)
GDAL 1.8.1 [64-bit] (release-1600-x64-gdal-1-8-1-mapserver-6-0-1)
GDAL 1.8.1 [32-bit] (release-1600-gdal-1-8-1-mapserver-6-0-1)
GDAL 1.8.0 [64-bit] (release-1600-x64-gdal-1-8-0-mapserver-6-0-0)
GDAL 1.8.0 [32-bit] (release-1600-gdal-1-8-0-mapserver-6-0-0)
GDAL 1.7.3 [64-bit] (release-1600-x64-gdal-1-7-3-mapserver-5-6-5)
GDAL 1.7.3 [32-bit] (release-1600-gdal-1-7-3-mapserver-5-6-5)

2) builds for Ubuntu 10.04 64 bit from UbuntuGis repository [using the ECW
libecwj2 3.3 library built by myself from ERDAS SDK Source Code
libecwj2-3.3-2006-09-06.zip]:
GDAL 1.9.0 [64 bit] (gdal-bin 1.9.0-1~exp1~lucid3 / libgdal-ecw-src
1.9.0-2~lucid1 / libgdal-dev 1.9.0-1~exp1~lucid3)
GDAL 1.8.0 [64 bit] (gdal-bin 1.8.0-2~lucid2 / libgdal-ecw-src
1.8.0-2~lucid1 / libgdal1-dev 1.8.0-2~lucid3)

3) build for Windows from OSGeo4W [with 3.3 ECW plugin from
release-1500-gdal-1-8-1-mapserver-6-0-1 at www.gisinternals.com/sdk]:
GDAL 1.8.1 [32-bit] (gdal 1.8.1-5)

4) build for Windows from FWTools [with related ECW plugin]:
GDAL 1.7.0b2 [32-bit] (FWTools 2.4.7)



Results:

- all 64-bit GDAL versions/builds on 64-bit Operative Systems (both Windows
and Linux) tested using gdal_translate with "TARGET=70" creation option
behave the same way producing an output ECW file of 159.832.544 bytes (with
the same checksums);

- almost all 64-bit GDAL versions/builds on 64-bit Operative Systems (both
Windows and Linux) tested using gdal_translate without a "TARGET" creation
option behave the same way producing an output ECW file of 24.982.036 bytes
(with the same checksums) with the only exception of GDAL 1.7.3 [64-bit]
(from www.gisinternals.com/sdk) on Windows 7 64-bit that produces a
considerably different (about 5 time bigger) output ECW file of 129.634.758
bytes;

- all 32-bit GDAL versions/builds on 64-bit/32-bit Windows tested using
gdal_translate with "TARGET=70" creation option behave the same way
producing an output ECW file of 192.085.632 bytes (with the same checksums)
that is slightly bigger than that produced by 64-bit GDAL versions with the
same "TARGET=70" creation option;

- the 32-bit GDAL versions/builds 1.9.0, 1.8.1, 1.8.0 from
www.gisinternals.com/sdk and 1.8.1 from OSGeo4W on 64-bit/32-bit Windows
tested using gdal_translate without a "TARGET" creation option behave the
same way producing an output ECW file of 52.777.560 bytes (with the same
checksums);

- the 32-bit GDAL versions/builds 1.7.3 from www.gisinternals.com/sdk and
1.7.0b2 from FWTools 2.4.7 on 64-bit/32-bit Windows tested using
gdal_translate without a "TARGET" creation option behave the same way
producing an output ECW file of 164.417.131 bytes (with the same checksums)
that is about 3 times bigger than that produced by the other 32-bit GDAL
versions tested.



I hope to do further investigation in the coming days


Andrea Giudiceandrea


--
View this message in context: http://osgeo-org.1560.n6.nabble.com/gdal-dev-Strange-behaviour-of-gdal-translate-with-ECW-on-linux-libecw-3-3-tp4498738p4518428.html
Sent from the GDAL - Dev mailing list archive at Nabble.com.