GeoDjango uses and/or provides interfaces for the following open source\ngeospatial libraries:
\nProgram | \nDescription | \nRequired | \nSupported Versions | \n
|---|---|---|---|
| \n | Geometry Engine Open Source | \nYes | \n3.14, 3.13, 3.12, 3.11, 3.10 | \n
| \n | Cartographic Projections library | \nYes (PostgreSQL and SQLite only) | \n9.x, 8.x, 7.x, 6.x | \n
| \n | Geospatial Data Abstraction Library | \nYes | \n3.13, 3.12, 3.11, 3.10, 3.9, 3.8, 3.7, 3.6, 3.5, 3.4, 3.3 | \n
| \n | IP-based geolocation library | \nNo | \n2 | \n
| \n | Spatial extensions for PostgreSQL | \nYes (PostgreSQL only) | \n3.6, 3.5, 3.4, 3.3, 3.2 | \n
| \n | Spatial extensions for SQLite | \nYes (SQLite only) | \n5.1, 5.0, 4.3 | \n
Note that older or more recent versions of these libraries may also work\ntotally fine with GeoDjango. Your mileage may vary.
\n\nOn Debian/Ubuntu, you are advised to install the following packages which will\ninstall, directly or by dependency, the required geospatial libraries:
\n$ sudo apt-get install binutils libproj-dev gdal-bin\nPlease also consult platform-specific instructions if you are on macOS\nor Windows.
\nWhen installing from source on UNIX and GNU/Linux systems, please follow\nthe installation instructions carefully, and install the libraries in the\ngiven order. If using MySQL or Oracle as the spatial database, only GEOS\nis required.
\n\n\nGEOS is a C++ library for performing geometric operations, and is the default\ninternal geometry representation used by GeoDjango (it’s behind the «lazy»\ngeometries). Specifically, the C API library is called (e.g., libgeos_c.so)\ndirectly from Python using ctypes.
First, download GEOS from the GEOS website and untar the source archive:
\n$ wget https://download.osgeo.org/geos/geos-X.Y.Z.tar.bz2\n$ tar xjf geos-X.Y.Z.tar.bz2\nThen step into the GEOS directory, create a build folder, and step into\nit:
$ cd geos-X.Y.Z\n$ mkdir build\n$ cd build\nThen build and install the package:
\n$ cmake -DCMAKE_BUILD_TYPE=Release ..\n$ cmake --build .\n$ sudo cmake --build . --target install\nWhen GeoDjango can’t find GEOS, this error is raised:
\nImportError: Could not find the GEOS library (tried "geos_c"). Try setting GEOS_LIBRARY_PATH in your settings.\nThe most common solution is to properly configure your Library environment settings or\nset GEOS_LIBRARY_PATH in your settings.
\nIf using a binary package of GEOS (e.g., on Ubuntu), you may need to\nInstall binutils.
\nGEOS_LIBRARY_PATHLink to this heading#If your GEOS library is in a non-standard location, or you don’t want to\nmodify the system’s library path then the GEOS_LIBRARY_PATH\nsetting may be added to your Django settings file with the full path to the\nGEOS C library. For example:
GEOS_LIBRARY_PATH = '/home/bob/local/lib/libgeos_c.so'\nPROJ is a library for converting geospatial data to different coordinate\nreference systems.
\nFirst, download the PROJ source code:
\n$ wget https://download.osgeo.org/proj/proj-X.Y.Z.tar.gz\n… and datum shifting files (download proj-datumgrid-X.Y.tar.gz for\nPROJ < 7.x) [1]:
$ wget https://download.osgeo.org/proj/proj-data-X.Y.tar.gz\nNext, untar the source code archive, and extract the datum shifting files in\nthe data subdirectory. This must be done prior to configuration:
$ tar xzf proj-X.Y.Z.tar.gz\n$ cd proj-X.Y.Z/data\n$ tar xzf ../../proj-data-X.Y.tar.gz\n$ cd ../..\nFor PROJ 9.x and greater, releases only support builds using CMake (see\nPROJ RFC-7).
To build with CMake ensure your system meets the build requirements.\nThen create a build folder in the PROJ directory, and step into it:
$ cd proj-X.Y.Z\n$ mkdir build\n$ cd build\nFinally, configure, make and install PROJ:
\n$ cmake ..\n$ cmake --build .\n$ sudo cmake --build . --target install\nGDAL is an excellent open source geospatial library that has support for\nreading most vector and raster spatial data formats. Currently, GeoDjango only\nsupports GDAL’s vector data capabilities [2].\nGEOS and PROJ should be installed prior to building GDAL.
\nFirst download the latest GDAL release version and untar the archive:
\n$ wget https://download.osgeo.org/gdal/X.Y.Z/gdal-X.Y.Z.tar.gz\n$ tar xzf gdal-X.Y.Z.tar.gz\nFor GDAL 3.6.x and greater, releases only support builds using CMake. To\nbuild with CMake create a build folder in the GDAL directory, and step\ninto it:
$ cd gdal-X.Y.Z\n$ mkdir build\n$ cd build\nFinally, configure, make and install GDAL:
\n$ cmake -DCMAKE_BUILD_TYPE=Release ..\n$ cmake --build .\n$ sudo cmake --build . --target install\nIf you have any problems, please see the troubleshooting section below for\nsuggestions and solutions.
\nWhen GeoDjango can’t find the GDAL library, configure your Library environment settings\nor set GDAL_LIBRARY_PATH in your settings.
\nGDAL_LIBRARY_PATHLink to this heading#If your GDAL library is in a non-standard location, or you don’t want to\nmodify the system’s library path then the GDAL_LIBRARY_PATH\nsetting may be added to your Django settings file with the full path to\nthe GDAL library. For example:
GDAL_LIBRARY_PATH = '/home/sue/local/lib/libgdal.so'\nFootnotes
\n\n