Super helpful. I was incorrectly thinking of `GDALWarp` as the lower-level
entrypoint that the other warper calls used, which is where I got confused.
Sounds like `GDALWarp` is basically the entrypoint for the `gdalwarp`
executable, hence the string-oriented API. I should go back and study the
C++
Simeon,
Le 31/01/2024 à 21:38, Fitch, Simeon via gdal-dev a écrit :
I'm on the `georust/gdal` bindings team, working on the warp routines,
and trying to understand the relationship between GDALWarpOptions vs
GDALWarpAppOptions.
I'm not seeing any way to create a GDALWarpOptions from a
GDALWa
I'm on the `georust/gdal` bindings team, working on the warp routines, and
trying to understand the relationship between GDALWarpOptions vs
GDALWarpAppOptions.
I'm not seeing any way to create a GDALWarpOptions from a
GDALWarpAppOptions or vice versa. Are functions needing GDALWarpOptions in
a com
