>
> --> this returns a GDALDatasetH. You need to GDALClose() it before
> being able to reopen it, so that its content gets flushed to storage.
>
Well, I have to say I'm impressed. Everything works smoothly. Thank you
for your help :)
Julien Osman.
__
On jeudi 1 octobre 2020 17:17:41 CEST Julien Osman wrote:
> Dear Frank,
>
> Thank you for this great advice. It seems to be the best options.
>
> Nevertheless, I fail to make it work. I use the SRTM DEM, witch consist
> of a bunch of files in a directory. So I load each file in a Dataset,
> then
Dear Frank,
Thank you for this great advice. It seems to be the best options.
Nevertheless, I fail to make it work. I use the SRTM DEM, witch consist
of a bunch of files in a directory. So I load each file in a Dataset,
then I build a VRT file that I store as a memory dataset. Then I provide
this
Julien,
The least disruptive approach to this would be for you to store your DEM in
a "memory dataset" and reference that. I've done this in the past when I
had it in a numpy array by using the numpy driver. The "MEM" dataset can
be used to reference approximately arbitrary in-memory arrays.
Be
Dear GDAL community,
I use the RPC transformer available in GDAL (GDALCreateRPCTransformer
and GDALRPCTransform).
To provide a DEM to the transformer, one needs to set the option
"RPC_DEM" with the path to the DEM file. In my workflow, this is not
very convenient because the DEM is already loaded
