Christopher,
CPLFindFile() calls CPLFinderInit() which issues CPLGetConfigOption(
"GDAL_DATA", nullptr). But CPLFinderInit() runs once per-thread. So a
potential theory for what you observe would be that something runs
CPLFindFile() before you call CPLSetConfigOption("GDAL_DATA", ...).
Settin
I'm tracking down a bug with WFS data import in our app and it seems like
the cause is a call to CPLFindFile returning NULL, looking for a
gmlasconf.xml file that should be in the gdal share directory.
This is a Mac universal binary app that embeds GDAL as a dylib and also
includes the share files
Le 24/08/2021 à 20:07, ni hao a écrit :
Hi Even,
Thank you for your reply.
Is there a simpler example to remove DES (say DES ID = 1) from an
existing NITF, or replace DES with a null string?
No, there's no code to update/remove a DES . You'll need to edit the
file at byte level, or rewrite a
Hi Even,
Thank you for your reply.
Is there a simpler example to remove DES (say DES ID = 1) from an existing
NITF, or replace DES with a null string?
From: Even Rouault
Sent: August 24, 2021 1:50 PM
To: ni hao ; gdal-dev@lists.osgeo.org
Subject: Re: [gdal-d
Hello,
yes, first look:
- at the doc of the DES creation option in
https://gdal.org/drivers/raster/nitf.html#creation-issues
- at
https://gdal.org/drivers/raster/nitf_advanced.html#data-extension-segments-xml-des
you will need to compose the DES segment in a relatively low level.
Look at
Hi List,
Is there a GDAL utility or Python code to delete/alter/write to NITF Data
Extension Segments (DES) ?
Thanks.
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Looking at what is the proper way to burn in - to a COG?
Here are the steps I have came up with:
1. Remove overviews
2. gdal_rasterize the geometry into the COG
3. create new overviews.
Is there a way to just rebuild the overviews after burning in the values? I
want to manipulate the origin
