I am trying to stitch a global elevation raster dataset made of 14,000 files
into 1 single 120GB file. I already have the VRT generated and have tried
applying both gdal warp and gdal translate on it with varying results in speed.
Although I am not warping anything (same projection for the input a
Hi,
I'm considering retiring the osgeo/gdal:alpine-ultra-small Docker image.
It's size difference with the osgeo/gdal:alpine-small one is small (50
MB vs 59 MB), and with arm64 images being now generated, the
cross-compilation time for it becomes a bit painful. Any opposition to that?
Even
Thank you Even for your help.
From: Even Rouault
Sent: August 24, 2021 3:28 PM
To: ni hao ; gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] NITF DES
Le 24/08/2021 à 20:07, ni hao a écrit :
Hi Even,
Thank you for your reply.
Is there a simpler example to re
Hi Even,
Thanks for looking into it. I suspected it might be something we have to live
with, but thanks for confirming.
I can get round the problem by creating a dummy feature using the input layer
extent then deleting it later, but it's an ugly workaround.
Weirdly, once you've hit the error,
Jon,
I believe this is a bug/feature of the (closed source) FileGDB SDK
itself when it . Not sure we can do much about that. Or according to
some mysterious parts of the documentation of the SDK perhaps we could
offer to the user, as layer creation options, the possibility to specify
the valu
Hello all,
I'm using GDAL 3.2.1 on Python 3.6.8 and am looking for more information on
FileGDB spatial indexes. I have a File GDB layer containing some features and
where the geometry is below a certain size, I'm trying to replace it with a
larger geometry. However, I'm getting the error Runtim
Le 25/08/2021 à 13:12, Idan Miara a écrit :
Thanks Even!
For my case, max(data types) is good enough, but I see that for the
general case calling this function might be a better option.
I couldn't find a reference for GDALWarpResolveWorkingDataType in the
python wrappers, or the warp tester
Thanks Even!
For my case, max(data types) is good enough, but I see that for the general
case calling this function might be a better option.
I couldn't find a reference for GDALWarpResolveWorkingDataType in the
python wrappers, or the warp tester:
https://github.com/OSGeo/gdal/blob/master/autote
