gdal icon indicating copy to clipboard operation
gdal copied to clipboard
verified publisher icon georust

Expansion of Warp API bindings

Open metasim opened this issue 2 years ago • 6 comments

  • [X] I agree to follow the project's code of conduct.
  • [ ] I added an entry to CHANGES.md if knowledge of this change could be valuable to users.
  • [x] Extract replicated methods in *Options types into macros.
  • [ ] Figure out why warp::tests::test_create_reproject fails on GDAL < 3.4 due to statistics seemingly not respecting no-data values.

metasim avatar Dec 28 '23 21:12 metasim

Looks pretty good, but I only checked the first two commits.

lnicola avatar Jan 03 '24 17:01 lnicola

I do wonder, though, if we shouldn't go straight for GDALWarp. It's not that much harder to use, and I think that mailing list reply suggested that it's the most powerful API.

lnicola avatar Jan 03 '24 19:01 lnicola

I do wonder, though, if we shouldn't go straight for GDALWarp. It's not that much harder to use, and I think that mailing list reply suggested that it's the most powerful API.

Good point. I'll research. At first glance it looked like it required a bunch more work, but maybe I jumped to conclusions there.

metasim avatar Jan 03 '24 20:01 metasim

It's a lot of work to write the bindings for, it's similar to gdaldem.

lnicola avatar Jan 03 '24 20:01 lnicola

Recently I've been experimenting with using gdal-sys to make calls to GDALWarp, which I've finally gotten running to my liking (besides the pesky MEM format..). But of course, only afterwards did I stumble across this PR

Anyway, getting GDALWarp implemented into the gdal crate would be a big win, IMO. So, if it helps, I would be happy to push this topic forward a bit with my learnings from the past few days? Please let me know :)

sevberg avatar Aug 07 '24 23:08 sevberg