[gdal-dev] Why gdal2tiles creates png.aux.xml files

Hi, I noticed this question in gis.stacexchange https://gis.stackexchange.com/questions/429896/how-to-not-generate-png-aux-xml-files-when-using-gdal2tiles. The current gdal2tiles.py really seems to write the aux.xml files except for the base tiles. I wonder if it is necessary and if there is an

Re: [gdal-dev] Standardize gdal-utils scripts return code for "no arguments"

Thank you for the study path Idan, much appreciated and I will use it. > Bottom line, returncode 2 is from the very last line in argparse.py, > the builtin ArgumentParser (function ArgumentParser.error()): > `self.exit(2, _('%(prog)s: error: %(message)s\n') % args)` Hmmm. Since return 2 is the de

Re: [gdal-dev] Standardize gdal-utils scripts return code for "no arguments"

Hi Matt, Since you mentioned that you don't understand how classes work (i.e. super function) I would highly recommend spending some time to go over some basic Python OOP, it's not complicated and I'm confident that it would be very useful. >From a quick search, maybe this link would be useful htt

[gdal-dev] GDAL compilation on Centos8 with MrSID

Hello, I'm struggling to compile GDAL on Centos8 with MrSID driver. I got the MrSID SDK from online (https://www.extensis.com/support/developers), however for linux only gcc 4.8.2 and gcc 5.3.1 versions of the SDK are available. I can manage to compile GDAL on Centos7 (gcc 4.8.5) with MrSID SDK (gc