Shawn,
This sounds more like a unwanted integer overflow somewhere in the NITF
driver. Is this with a recent GDAL ? If so, please file a bug at
https://github.com/OSGeo/gdal/issues/new with all the details needed. A
link to the dataset would be ideal, but otherwise please provide in the
ticket description the output of "gdalinfo your.nitf"
Even
Le 06/04/2021 à 19:35, ni hao a écrit :
Hi list,
I encountered problem ingesting a large NITF Int16 image with GDAL:
NITF 2-band image in Int16 format, 4.3 GB. It has 19690 lines x 61180
pixels. The upper 90% of the image looks fine. But the last 2000
lines fail to load by GDAL. That coincides with the 32-bit boundary.
Note that another larger NITF in 32-bit float, 10.1 GB file loads fine.
Is there a hard limit on NITF Int16 file size?
Thanks,
Shawn
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
--
http://www.spatialys.com
My software is free, but my time generally not.
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
