Hi.
Currently my c++ app creates COG files from GeoTiff tiled files.
GeoTiff files are created using JPEG compression with YCBCR photometric using
following creation options:
* PROFILE=GeoTIFF
* TILED=YES
* BLOCKXSIZE=xxx
* BLOCKYSIZE=xxx
* COMPRESS=JPEG
* PHOTOMETRIC=Y
Hi,
I have some results.
First of all note that fprintf(stderr,...) does nothing on Android since it is
redirected to /dev/null. I had to modify cpl_simple.txt in order to use
__android_log_print(ANDROID_LOG_INFO,LOG_TAG, ... instead.
You can find the full logs here:
https://www.virtual-wi
Hi Even,
Sorry for the delay, but I’ve now tested with PR3216, alone, and then with
PR3127. I’m getting the same behavior as I reported below. Perhaps my best
chance at getting this to work is to either directly make proj calls, or
construct the pipeline myself and pass through gdal?
Steve
Known issue: https://github.com/OSGeo/gdal/issues/3627
Le 28/03/2022 à 16:08, volkan yazici a écrit :
Hi,
I use this code for raster stacking:
outvrt = ('result/raster_stack_vrt.tif')
outtif = ('result/raster_stack.tif')
tifs = glob.glob('data/*.tif')
outds = gdal.BuildVRT(outvrt, tifs, separa
Hi,
I use this code for raster stacking:
outvrt = ('result/raster_stack_vrt.tif')
outtif = ('result/raster_stack.tif')
tifs = glob.glob('data/*.tif')
outds = gdal.BuildVRT(outvrt, tifs, separate = True)
outds = gdal.Translate(outtif, outds)
Band names are automatically generated as band_1, band_
Thanks Even and Greg for your fast replies
The app and GDAL are built with Android NDK 21 (I have tried NDK 30 and 31) and
is targeting SDK 30. High memory Android device is 10Gb or even 14Gb with RAM
PLUS. I can add that the app itself is based on Qt 5.15.8 and runs fine on
Windows, Linux, Ra
Hi,
didn't hear about Scudo before, but it seems it is a LLVM side project:
https://llvm.org/docs/ScudoHardenedAllocator.html
So perhaps you could build and use it on Linux as shown in
https://llvm.org/docs/ScudoHardenedAllocator.html#library
Besides a potential bug in the allocator, it mig
Philippe Lelong writes:
> What I can see is that the memory grows exponentially until no more
> memory is available and crash, even on systems with huge memory
> available while an Android device without SCUDO and very limited
> memory (let's say 4Gb) in the same exact conditions, with the same
Hi,
I am searching for this issue for months now, and cannot find any solution.
To make a long story short, we are using GDAL to decode OGR/S57 charts for
years now. We are facing numerous crashes under Android 11 and up if and only
if this Android 11 implementation is using SCUDO as a memory
