Hi Even,
Thanks for getting back to me. I should have mentioned we're using the Python
bindings, but presumably we can still do something like this?
ds = gdal.OpenEx(path, open_options=['OVERVIEW_LEVEL=NONE'])
Jon
e: jon.mor...@jbarisk.com
t: +44 (0)1756 799919
www.jbarisk.com
All JBA Risk Man
With GDAL 3.3, you could add -oo OVERVIEW_LEVEL=NONE. See
https://gdal.org/api/raster_c_api.html?highlight=overview_level#_CPPv410GDALOpenExPKcjPPCKcPPCKcPPCKc
Le 28/05/2021 à 15:56, Jon Morris a écrit :
Hello all,
One of our users reported a difference in outputs after we upgraded
from GDAL
Hello all,
One of our users reported a difference in outputs after we upgraded from GDAL
2.2 to 3.2. Our tool is using gdal_translate to resample a raster from 5m to
10m and the outputs are very different.
I'm ok with things changing between major versions, but when investigating, I
found that
Hi,
I guess that by "data" you mean datasets like GeoJSON file or GeoTIFF image.
For individual coordinates folks in the Finnish Geospatial Institute (FGI)
do conversions like in this cs2cs example
echo 2258573.56109 1010806.43899 5859099.49087 2021.26 | cs2cs -d 4 --area
finland EPSG:7789 EPSG