As of this day, this is probably the only and fastest way of installing it.
Based from the GDAL and PROJ build requirements, here is the full list of required packages to install:
- C++11 -
cppversion7.3.1 - PROJ 6 -
projversion6.1.1- SQLite3 -
sqlite3version3.7.17 - libtiff - version
4.0 - cmake - version
3.13.1
- SQLite3 -
Installation of these packages are covered in the sections below. However, before you proceed with the installation, make sure you are already logged in to your EC2 Amazon Linux 2 via SSH. After logging in, you just need to issue some statements in the command-line.
Luckilly, we don't have to install everything from source. At least some can be installed through yum.
sudo yum install gcc-c++.x86_64 cpp.x86_64 sqlite-devel.x86_64 libtiff.x86_64 cmake3.x86_64 -yInstallation from source, currently there's no other way but this.
cd /tmp
wget https://download.osgeo.org/proj/proj-6.1.1.tar.gz
tar -xvf proj-6.1.1.tar.gz
cd proj-6.1.1
./configure
sudo make
sudo make installBe careful not to install PROJ version 6.2.0 or newer because the one from the yum packages is only SQLite version 3.7.17. Installing PROJ version 6.2.0 would require installing SQLite version 3.11 which you may need to install from source and not with yum.
Installation from source, currently there's no other way but this.
cd /tmp
wget https://github.com/OSGeo/gdal/releases/download/v3.2.1/gdal-3.2.1.tar.gz
tar -xvf gdal-3.2.1.tar.gz
cd gdal-3.2.1
./configure --with-proj=/usr/local --with-python
sudo make
sudo make install
which gdalinfo; gdalinfo --versionIt should show something like
/usr/local/bin/gdalinfo
GDAL 3.2.1, released 2020/12/29
Did I miss something? Are you having some troubles with the installed GDAL? Write them down as comments below. Let's help our selves and others at the same time.
Difficult question -- a simple answer is that it sort of depends on the context, or the intended audience. I think GDAL developers eventually resorted to providing a simple base package with few dependencies and few supported formats, then let people (or repackagers) add on what they want.
One approach would be to look at what some of the big package managers do, and provide a similar set. Another approach would be to ask on the GDAL developers mailing list, but I suspect you would get a similar roundabout answer like mine. That developers list is very active, and has a lot of user exposure, so you might get some good feedback there.
A down side of supporting lots of formats is a lot of dependencies for your own users to have to install. This is accommodated in part by instructing users how to customize their builds. In reality that is what this thread is about. Pardon my ramblings, I do not have a pat answer for this.