

Results in 0Traceback (most recent call last):įile "/usr/local/bin/gdal_merge.py", line 172, in raster_copy_with_mask First, I install according to the above comment. Unfortunately the GeoTIFFs I'm using are too large to share, but I'm pretty sure the below error could be reproduced with any two images.


Type "help", "copyright", "credits" or "license" for more information.Ĭorrect, I'm using GDAL for raster processing (satellite images, in my case). Kelvins-MacBook-Pro-899:~ kelvin$ python3.6 For instance, 2.7 and 3.7 both give a "ModuleNotFoundError: No module named 'osgeo'" error, but 3.6 works. I have found that sometimes only one version of Python can correctly import gdal without any dramas. Python setup.py build_ext -gdal-config /usr/local/Cellar/gdal/HEAD-41888_2/bin/gdal-configĭo an 'ls /usr/local/Cellar/gdal/' if you need to get the revision number. Python setup.py build_ext -I/Library/Frameworks/amework/Versions/2.3/Headers -L/Library/Frameworks/amework/Versions/2.3/unix/lib -gdal-config /Library/Frameworks/amework/Versions/2.3/unix/bin/gdal-configĪlternatively, install GDAL via brew, then do similar to the above. Via GDAL Framework / QGISįirst, you can install the GDAL Framework via QGIS (or get it directly), and then do. ~/.bash_login, ~/.bash_profile, ~/.cshrc, ~/.profile, ~/.tcshrc, and/or ~/.zprofile.I've found two ways to install the GDAL Python bindings on Mac. Depending on which shell you use, any of the following files may have been modified: If necessary, edit your shell profile file(s) to remove adding /Library/Frameworks/amework/Versions/2.7 to your PATH environment file.

Ls -l /usr/local/bin | grep './Library/Frameworks/amework/Versions/2.7' | awk '' | tr -d | xargs rm Remove the symbolic links in /usr/local/bin that point to this Python version see ls -l /usr/local/bin | grep './Library/Frameworks/amework/Versions/2.7' and then run the following command to remove all the links: cd /usr/local/bin/ Remove the Python 2.7 applications directory Sudo rm -rf /Library/Frameworks/amework/Versions/2.7 Remove the third-party Python 2.7 framework Basically, all you need to do is the following: NOTE: The steps listed here do not affect the Apple-supplied system Python 2.7 they only remove a third-party Python framework like those installed by installers.ĭo not attempt to remove any Apple-supplied system Python which are in /System/Library and /usr/bin.
