Python – Solving GDAL_CALC Works but Python Error at End of Each Process That Prevents Automation

errorgdalosgeo4wpythonwindows 7

Python 3.4.1,
GDAL 1.11.0,
OSGEO4W,
Windows 7,
OSGEO4W Windows Shell

All 64-bit

(ArcGIS is installed as well 10.2 with Python 2.7)

So gdal_translate works fine.

gdal_calc provides perfect outputs but at the end of each process I get the error below. This is a problem as I cannot automate anything due to this pop up error. I hit close and the error goes away, the output file is 100% perfect but then the next gdal_calc line gives me the same error.

This is a sample line of code that gives the error (almost all my gdal_calc commands give the error but not gdal_translate).

gdal_calc.py -A 2000025-2000032.s0481pfv50-sst-16b.hdf.tiff_C.tiff -B C:\temp\QUAL\2000025-2000032.m0481pfv50-qual.hdf.tiffBINARY.tiff  --outfile=A25_32_SSTQUAL4.tiff --calc="A*B"

and this is the error. As I say the process actually works and will continue when I close the error box. After the word DONE appears the error pops up, I close the window and then the next line of code runs, then the error pops up again and so on.

enter image description here

enter image description here

Additional Error message generated

> Problem signature:
  Problem Event Name:   APPCRASH
  Application Name: python.EXE
  Application Version:  0.0.0.0
  Application Timestamp:    5193f3af
  Fault Module Name:    ntdll.dll
  Fault Module Version: 6.1.7601.18247
  Fault Module Timestamp:   521eaf24
  Exception Code:   c0000005
  Exception Offset: 0000000000053290
  OS Version:   6.1.7601.2.1.0.256.48
  Locale ID:    1033
  Additional Information 1: 8c64
  Additional Information 2: 8c64dfac0942d27b36722f7434c64847
  Additional Information 3: e156
  Additional Information 4: e156d5603c95b65c33088aa70929b4be

Best Answer

As an extremely heavy-handed, last-ditch-effort approach to this, you can disable the crash dialogs in Windows using the DontShowUI value in the Windows Error Reporting registry keys.

Related Solutions

QGIS Python – Using QGIS with Pre-existing Python 3.2 and Matching GDAL

I had been putting off sorting this problem out for a long time but finally have a proper solution. The situation is this:

I need a 64bit version of Python 32 and GDAL for a package other than QGIS.
I need a 32bit version of GDAL to work with Python 2.7 for QGIS.
QGIS consistently loads the wrong DLL and complains that it is not a 32bit Windows application.

The reason and solution are simple. I have environment variables which point to the 64 bit GDAL installation - which was installed before QGIS and I need to leave alone so my other applications will work. OSGeo appends its path information to the system path but because it is put at the end of the path, my pre-existing installs for 64-bit Python 3.2 are always picked up. So, I added the following code at the start of the GdalTools.py file (I used the one in C:\Users\MyAccount.qgis\python\plugins\GdalTools):

# hack the path to force QGIS to look in OSGeo4w directory first
import sys
sys.path.reverse()

Now QGIS starts with zero errors and I can use the GDAL tools, without switching to another machine.

EDIT (Windows 64 bit version July 2014): I STILL have to do this hack because QGIS still uses Python27 and I need Python32 for other packages I use. I still get the same error message and forcing the paths in config section for QGIS still doesn't solve entirely the problem. However, this hack continues to neatly cure the issue (I am now editing the version of gdaltools.py in C:\OSGeo4W64\apps\qgis\python\plugins\GdalTools on my system.

[GIS] “ImportError: No module named gdalsrsinfo” What’s the issue

GDAL isn't all in python. The core is written in C/C++. You can, of course, use the GDAL/OGR library parts from python

You can also use those library parts using other APIs, including compiled languages such as C or C++. That is what many (although not all) of the command line utilities do. There is a list of command line utilities at http://www.gdal.org/gdal_utilities.html - you can safely assume those that end with .py are python scripts and those that do not end with .py are compiled executables (.exe in windows terms, typically an ELF format program in Linux, or Mach-O on MacOS).

The python utilities are intended to be used from the command line (Terminal.app or similar), just like the executable format utilities. You may be able to make use of them by import in python, or by subprocess but there isn't anything GDAL specific in that invocation.

Related Question

[GIS] Attempting to install pip package produces gdalversion is not defined error