Le 18/03/2021 à 17:06, Evert Etienne (SITEMARK) a écrit :
Does one of the 2 options keep more settings of the input file? Such as NoData
value, BIGTIFF creation option…?
gdal_calc modify the nodata value settings AFAIR. You have to consult
its doc. gdal_translate should be fine. But when res
Does one of the 2 options keep more settings of the input file? Such as NoData
value, BIGTIFF creation option…?
But indeed, the possibility to use VRT does seem better since then it can be
done during tiling. This probably only saves space and not time, correct (due
to lack of understanding of
"gdal_translate -scale 0 1 0 factor in out" could also be used. As a
bonus point, this works with VRT as an output if you don't want to
materialize the intermediate file.
Even
Le 18/03/2021 à 12:20, Evert Etienne (SITEMARK) a écrit :
For reference, I decided to go for a simple gdal_calc with
For reference, I decided to go for a simple gdal_calc with
`f"--calc=A*{factor}”`
> On 12 Mar 2021, at 20:43, Evert Etienne (SITEMARK)
> wrote:
>
> Hello all,
>
> I was wondering what the best or recommended way was to convert the vertical
> unit of a DEM/DSM. I am able to use gdal_translate
Hello all,
I was wondering what the best or recommended way was to convert the vertical
unit of a DEM/DSM. I am able to use gdal_translate, gdal_calc.py, GDAL python
bindings or rasterio. I will afterwards be tiling using gdal2tiles.
Any pointers would be appreciated.
Greetings
___
