[gdal-dev] GeoEye-1 NITF - Warning 1: Image with 11 bits per sample will not be interpreted properly

Gong, Shawn (Contractor) Shawn.Gong at drdc-rddc.gc.ca
Fri Aug 14 10:08:53 EDT 2009

Hi Frank and list,

I rebuilt Gdal on a 64-bit Linux server, adding libecwj2, and it
ingested GeoEye-1 NITF just fine (a bit slow though).
So you are right that this warning should not really apply. 

My question is then why it failed on Windows XP, at libecwj2's
ncsjpcbuffer.cpp CNCSJPCBuffer(). The Jpeg2000 file is 463MB, after
decompression it is 2.375 GB. Do I need to specify "large file" when
building Gdal on Windows?


-----Original Message-----
From: gdal-dev-bounces at lists.osgeo.org
[mailto:gdal-dev-bounces at lists.osgeo.org] On Behalf Of Frank Warmerdam
Sent: Wednesday, August 12, 2009 10:12 AM
To: Gong, Shawn (Contractor)
Cc: gdal-dev at lists.osgeo.org
Subject: Re: [gdal-dev] GeoEye-1 NITF - Warning 1: Image with 11 bits
per sample will not be interpreted properly

On Tue, Aug 11, 2009 at 12:17 PM, Gong, Shawn
(Contractor)<Shawn.Gong at drdc-rddc.gc.ca> wrote:
> hi list,
> I found help clues to build libecwj2 on Windows.


Congrats on working though this issue!  Perhaps you would like to add
some notes to:


> However when I tried to open GeoEye-1 NITF, I got "Warning 1: Image
with 11
> bits per sample will not be interpreted properly".

I thought there were changes in trunk to avoid this warning when the
image is jpeg2000 and being handled by a suitable codec.  However,
I think I only tested this specific issue when using JP2KAK for the
jpeg2000 support.  I'm not sure if there are problems with the ecw sdk
and such files or not.  However, the note about being badly corrupted
should not really apply.

> There are two sub-datasets in NITF (please see the gdalinfo at the
end). If
> I open the 2nd sub-dataset, the data show only 73 pixels and 220
> digital numbers are either 0 or 255.

Hmm, I don't know why it would be particularly small in size.
I'm also surprised that the latest windows fwtools has problems.
Perhaps you could file a ticket on the issue and I could look into
it a bit next week (especially since problems can be reproduced
with FWTools which I think uses JP2KAK for this purpose).

Hmm, on second thought, I believe I removed JP2KAK from
FWTools for licensing reasons - so perhaps it is using the
ecw jpeg2000 driver too.

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
gdal-dev mailing list
gdal-dev at lists.osgeo.org

More information about the gdal-dev mailing list