[gdal-dev] Not writing PAM files
Even Rouault
even.rouault at spatialys.com
Mon Nov 3 08:19:19 PST 2025
FLIR should be fined. It has a "PamFlagKeeper oKeeper(nPamFlags);" guard
that makes sure to restore the PAM flags to its initial value after
metadata has been set
Le 03/11/2025 à 17:08, Javier Jimenez Shaw a écrit :
> Thank you Even!
>
> Probably the same is needed for FLIR, as DJI logic was based in FLIR
> code also in jpgdataset.cpp
>
> On Mon, 3 Nov 2025 at 17:04, Even Rouault <even.rouault at spatialys.com>
> wrote:
>
> Hi Javier,
>
> .aux.xml file is no longer generated on opening per
> https://github.com/OSGeo/gdal/commit/2ad4ebf4ddcaa74af2d4cea212fb61f0ac382f20
>
> Even
>
> Le 03/11/2025 à 10:13, Javier Jimenez Shaw via gdal-dev a écrit :
> > Hi
> >
> > When I read some raster files (in particular thermal JPEG files), a
> > side car file .aux.xml appears next to it.
> >
> > I would like to avoid the creation of this side car file, but I
> want
> > to use any .aux.xml file if it is already there. Yes, I could
> imagine
> > there is a performance impact if I read it several times, but I am
> > going to read the file only once.
> >
> > The config option GDAL_PAM_ENABLED seems to be completely disabling
> > PAM functionality:
> >
> https://gdal.org/en/stable/user/configoptions.html#persistent-auxiliary-metadata-pam-options
> > Reading the documentation, I would imagine that the PAM is
> completely
> > disabled, not only the creation of the side car file while
> reading a
> > raster.
> >
> > Is it posible to not create the .aux.xml, but use it if present?
> >
> > Thank you
> >
> > _______________________________________________
> > gdal-dev mailing list
> > gdal-dev at lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/gdal-dev
>
> --
> http://www.spatialys.com
> My software is free, but my time generally not.
>
--
http://www.spatialys.com
My software is free, but my time generally not.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20251103/cce505e1/attachment.htm>
More information about the gdal-dev
mailing list