The side effect of using a file where this warning is emitted is that
this COMRAT field which indicates the compression rate will be set to a
invalid value (or probably set to blank. I haven't checked). Pedantic
software or validation procedures might be unhappy with that. GDAL based
software
Brook,
to methods can still be used. We just have restricted invalid
conversions, like a LineString to Polygon
A great part of what is valid is tested in
https://github.com/OSGeo/gdal/blob/1ec0b63d8820b2d3f0cfb792e05f3f5fea49892c/autotest/cpp/test_ogr.cpp#L787
Even
Le 14/08/2021 à
Raymond,
I believe this has been fixed per this commit in master done a few weeks
ago:
https://github.com/OSGeo/gdal/commit/0decd82d582015c07bcf22c52cc03bbdda952ce9
I've just backported it to the 3.3 branch
Even
Le 14/08/2021 à 13:22, Chastain, Raymond Lee (MU-Student) a écrit :
When we
When we enable JPEG-2000 compression (or any IC=* creation option) alongside
"SDE_TRE=YES" we get:
"Warning 1: Unable to locate COMRAT to update in NITF header."
We require the precision increase provided by "SDE_TRE=YES" and dropping the IC
creation option
explodes the size of our final
