[gdal-dev] GDALWarpOptions vs GDALWarpAppOptions

[Fitch, Simeon]

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 completely different universe from ones needing GDALWarpAppOptions?

GDALWarpOptions seems clear, with requisite C functions for
manipulating it, whereas GDALWarpAppOptions seems to only accept key/value
pairs via GDALWarpAppOptionsSetWarpOption, which seems quite limiting.

I was hoping to provide users a single entry point for specifying warp
options, but wanted some expert advice before going down a dead end.

Thanks!

Simeon

-- 
Simeon Fitch
Co-founder & CTO
Astraea, Inc.

-- 
The content of this email is intended for the person or entity to which it 
is addressed only. This email may contain confidential information. If you 
are not the person to whom this message is addressed, be aware that any 
use, reproduction, or distribution of this message is strictly prohibited. 
If you received this in error, please contact the sender and immediately 
delete this email and any attachments.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20240131/d643036b/attachment.htm>