[gdal-dev] Testers with Kakadu needed

[Even Rouault]

Hi,

A ticket ( http://trac.osgeo.org/gdal/ticket/5257 ) has been opened about a 
potential issue that would affect the JPEG2000 files that are created with the 
JP2KAK driver in GDAL 1.9.0 or above.

This issue, if confirmed, would result in a corruption of the GMLJP2 box. This 
could easily get unnoticed since GDAL writes by default both a GMLJP2 and 
GeoJP2 box, and, when reading, uses the GeoJP2 box if both are found (and if 
GMLJP2 is corrupted, it will only see the GeoJP2 box)

The way to reliably confirm the problem is to generate a JPEG2000 with only a 
GMLJP2 box, by explictly disabling GeoJP2 box creation.

1) Download http://svn.osgeo.org/gdal/trunk/autotest/gcore/data/byte.tif
2) gdal_translate byte.tif byte.jp2 -of JP2KAK -co GEOJP2=NO
3) check if there's a byte.jp2.aux.xml file. If there's one, delete it (if it 
exists, that's an early sign of the problem)
4) gdalinfo byte.jp2

If gdalinfo reports a PROJCS["NAD27 / UTM zone 11N"...] and Origin = 
(440720.000000000000000,3751320.000000000000000, then it's fine. Otherwise 
there's a problem.

The reported problem was with Kakadu 6.3. It couldn't be reproduced with 
Kakadu 5.2 however. If people with a variety of Kakadu versions could make the 
above test and report their findings (Kakadu version, OS, 32/64 bit, little-
endian/big-endian machine, result of the test), that would be helpful.

Even

-- 
Geospatial professional services
http://even.rouault.free.fr/services.html