Oh, wait, it does put IGEOLO in the output nitf, but I also get the
warning:
Warning 6: driver NITF does not support creation option IGEOLO
On Sun, 26 Feb 2023 16:04:16 +1100, Brad Hards wrote:
> On Sunday, 26 February 2023 2:33:31 PM AEDT Amadeus WM via gdal-dev
> wrote:
>&g
Feb 2023 16:04:16 +1100, Brad Hards wrote:
> On Sunday, 26 February 2023 2:33:31 PM AEDT Amadeus WM via gdal-dev
> wrote:
>> So I just noticed that if I call
>>
>> dataset->SetMetadataItem();
>>
>> then it creates a file out.ntf.aux.xml and whatever fields I
ose fields in out.ntf and not in
out.ntf.aux.xml? What determines where they go?
On Sat, 25 Feb 2023 16:55:54 +1100, Brad Hards wrote:
> On Saturday, 25 February 2023 4:44:10 PM AEDT Amadeus WM via gdal-dev
> wrote:
>> Hello everyone,
>>
>> I'm new to GDAL and I'm
7+28.562-080.577+28.562-080.578");
Again, NITF_ICORDS and NITF_GEOLO do get printed in the loop in the code,
but don't make it in the output file, so no joy yet.
On Sat, 25 Feb 2023 16:55:54 +1100, Brad Hards wrote:
> On Saturday, 25 February 2023 4:44:10 PM AEDT Amadeus WM via gdal-dev
Hello everyone,
I'm new to GDAL and I'm trying to figure out how to create a NITF file
given the raw data, that also has the NITF_IGEOLO field set. With a
little help from chatGPT I came up with the c++ program below (it has
to be in c++). It writes the file, but it does not contain the
NITF_IGEOL
