Even Rouault

closing that one as staled. Please reopen if progress is made

I know very little about Oracle and the OCI driver, but I doubt this is an issue about quoting. Perhaps an issue with encoding, decimal separator, etc. ? https://gdal.org/drivers/vector/oci.html mentions:...

> * all above `#include "foo.h"` should be replaced by `#include ` why ? Looking on my system with other packages, both styles are used. For example https://github.com/madler/zlib/blob/643e17b7498d12ab8d15565662880579692f769d/zlib.h#L34 uses ``#include...

> just checked 3.8.1 and `#include "zlib.h"` still is used in public API interface. yes, I mentioned I removed those files in master / 3.9.0dev. They will remain in the...

closing, as I don't believe there's any further action needed

> gdalwarp -t_srs EPSG:4326 MSG4-SEVI-MSG15-0100-NA-20220419091243.184000000Z-NA.nat output.tiff @mdbmdb74 Could you retry with -r bilinear or -r cubic ? The default nearest neighbour resampling is not good to assess sub-pixel shifts. @g8sqh...

> if this could be extended to reading single blocks I don't see any easy resolution for that. This goes against a lot of assumptions in the design of GDAL....

CC @szekerest

> Also progress messages should go to stderr, not stdout! this is quite disputed in https://unix.stackexchange.com/questions/331611/do-progress-reports-logging-information-belong-on-stderr-or-stdout . I'm not sure all GDAL utilities are consistent regarding this, but for now...

> will just need elaborate filters to clean the progress messages out of standard output when piping to other programs. hum, good point. Most GDAL programs have not both an...