In general, GeoDjango installation requires:
\n\nDetails for each of the requirements and installation instructions\nare provided in the sections below. In addition, platform-specific\ninstructions are available for:
\n\n\nBecause GeoDjango is included with Django, please refer to Django's\ninstallation instructions for details on\nhow to install.
\nPostgreSQL (with PostGIS), MySQL, Oracle, and SQLite (with SpatiaLite) are the\nspatial databases currently supported.
\n\nThe geospatial libraries required for a GeoDjango installation depends\non the spatial database used. The following lists the library requirements,\nsupported versions, and any notes for each of the supported database backends:
\nデータベース | \nLibrary Requirements | \nSupported Versions | \nNotes | \n
|---|---|---|---|
PostgreSQL | \nGEOS, GDAL, PROJ, PostGIS | \n10+ | \nRequires PostGIS. | \n
MySQL | \nGEOS, GDAL | \n5.7+ | \n\n |
Oracle | \nGEOS, GDAL | \n19+ | \nXE not supported. | \n
SQLite | \nGEOS, GDAL, PROJ, SpatiaLite | \n3.9.0+ | \nRequires SpatiaLite 4.3+ | \n
See also this comparison matrix on the OSGeo Wiki for\nPostgreSQL/PostGIS/GEOS/GDAL possible combinations.
\nDATABASES configurationLink to this heading#Set the ENGINE setting to one of the spatial\nbackends.
django.contrib.gis to INSTALLED_APPSLink to this heading#Like other Django contrib applications, you will only need to add\ndjango.contrib.gis to INSTALLED_APPS in your settings.\nThis is so that the gis templates can be located -- if not done, then\nfeatures such as the geographic admin or KML sitemaps will not function properly.
If you can't find the solution to your problem here then participate in the\ncommunity! You can:
\nJoin the #django-geo IRC channel on Libera.Chat. Please be patient and\npolite -- while you may not get an immediate response, someone will attempt\nto answer your question as soon as they see it.
Ask your question on the GeoDjango forum.
File a ticket on the Django trac if you think there's a bug. Make\nsure to provide a complete description of the problem, versions used,\nand specify the component as "GIS".
By far, the most common problem when installing GeoDjango is that the\nexternal shared libraries (e.g., for GEOS and GDAL) cannot be located. [1]\nTypically, the cause of this problem is that the operating system isn't aware\nof the directory where the libraries built from source were installed.
\nIn general, the library path may be set on a per-user basis by setting\nan environment variable, or by configuring the library path for the entire\nsystem.
\nLD_LIBRARY_PATH environment variableLink to this heading#A user may set this environment variable to customize the library paths\nthey want to use. The typical library directory for software\nbuilt from source is /usr/local/lib. Thus, /usr/local/lib needs\nto be included in the LD_LIBRARY_PATH variable. For example, the user\ncould place the following in their bash profile:
export LD_LIBRARY_PATH=/usr/local/lib\nOn GNU/Linux systems, there is typically a file in /etc/ld.so.conf, which may include\nadditional paths from files in another directory, such as /etc/ld.so.conf.d.\nAs the root user, add the custom library path (like /usr/local/lib) on a\nnew line in ld.so.conf. This is one example of how to do so:
$ sudo echo /usr/local/lib >> /etc/ld.so.conf\n$ sudo ldconfig\nFor OpenSolaris users, the system library path may be modified using the\ncrle utility. Run crle with no options to see the current configuration\nand use crle -l to set with the new library path. Be very careful when\nmodifying the system library path:
# crle -l $OLD_PATH:/usr/local/lib\nbinutilsLink to this heading#GeoDjango uses the find_library function (from the ctypes.util Python\nmodule) to discover libraries. The find_library routine uses a program\ncalled objdump (part of the binutils package) to verify a shared\nlibrary on GNU/Linux systems. Thus, if binutils is not installed on your\nLinux system then Python's ctypes may not be able to find your library even if\nyour library path is set correctly and geospatial libraries were built perfectly.
The binutils package may be installed on Debian and Ubuntu systems using the\nfollowing command:
$ sudo apt-get install binutils\nSimilarly, on Red Hat and CentOS systems:
\n$ sudo yum install binutils\nBecause of the variety of packaging systems available for macOS, users have\nseveral different options for installing GeoDjango. These options are:
\nPostgres.app (easiest and recommended)
This section also includes instructions for installing an upgraded version\nof Python from packages provided by the Python Software\nFoundation, however, this is not required.
\nAlthough macOS comes with Python installed, users can use framework\ninstallers provided by the Python Software Foundation. An advantage to\nusing the installer is that macOS's Python will remain "pristine" for internal\noperating system use.
\n\nPostgres.app is a standalone PostgreSQL server\nthat includes the PostGIS extension. You will also need to install gdal and\nlibgeoip with Homebrew.
After installing Postgres.app, add the following to your .bash_profile so\nyou can run the package's programs from the command-line. Replace X.Y with\nthe version of PostgreSQL in the Postgres.app you installed:
export PATH=$PATH:/Applications/Postgres.app/Contents/Versions/X.Y/bin\nYou can check if the path is set up correctly by typing which psql at a\nterminal prompt.
Homebrew provides "recipes" for building binaries and packages from source.\nIt provides recipes for the GeoDjango prerequisites on Macintosh computers\nrunning macOS. Because Homebrew still builds the software from source, Xcode\nis required.
\nSummary:
\n$ brew install postgresql\n$ brew install postgis\n$ brew install gdal\n$ brew install libgeoip\nWilliam Kyngesburye provides a number of geospatial library binary packages\nthat help to get GeoDjango installed on macOS without compiling them from\nsource. However, Xcode is still necessary for compiling the Python database\nadapters psycopg2 (for PostGIS).
\n\nDownload the framework packages for:
\nUnixImageIO
PROJ
GEOS
SQLite3 (includes the SpatiaLite library)
GDAL
Install the packages in the order they are listed above, as the GDAL and SQLite\npackages require the packages listed before them.
\nAfterward, you can also install the KyngChaos binary packages for PostgreSQL\nand PostGIS.
\nAfter installing the binary packages, you'll want to add the following to\nyour .profile to be able to run the package programs from the command-line:
export PATH=/Library/Frameworks/UnixImageIO.framework/Programs:$PATH\nexport PATH=/Library/Frameworks/PROJ.framework/Programs:$PATH\nexport PATH=/Library/Frameworks/GEOS.framework/Programs:$PATH\nexport PATH=/Library/Frameworks/SQLite3.framework/Programs:$PATH\nexport PATH=/Library/Frameworks/GDAL.framework/Programs:$PATH\nexport PATH=/usr/local/pgsql/bin:$PATH\nAfter you've installed the KyngChaos binaries and modified your PATH, as\ndescribed above, psycopg2 may be installed using the following command:
$ python -m pip install psycopg2\nKurt Schwehr has been gracious enough to create GeoDjango packages for users\nof the Fink package system. Different packages are available (starting\nwith django-gis), depending on which version of Python you want to use.
MacPorts may be used to install GeoDjango prerequisites on computers\nrunning macOS. Because MacPorts still builds the software from source,\nXcode is required.
\nSummary:
\n$ sudo port install postgresql13-server\n$ sudo port install geos\n$ sudo port install proj6\n$ sudo port install postgis3\n$ sudo port install gdal\n$ sudo port install libgeoip\nProceed through the following sections sequentially in order to install\nGeoDjango on Windows. In this tutorial we will install 64 bit versions of each\napplication.
\nInstall a 64 bit version of Python. See Install Python\nfor further information.
\nDownload the latest PostgreSQL 12.x installer from the\nEnterpriseDB website. After downloading, run the installer, follow the\non-screen directions, and keep the default options unless you know the\nconsequences of changing them.
\n\nWhen the installer completes, it will ask to "Launch Stack Builder at exit?" --\nkeep this checked, as it is necessary to install PostGIS.
\n\nFrom within the Stack Builder (to run outside of the installer,\n), select\n from the drop down\nmenu and click next. Expand the\n menu tree and select\n.
\nAfter clicking next, you will be prompted to confirm the selected package and\n"Download directory". Click next again, this will download PostGIS and you will\nbe asked to click next to begin the PostGIS installer. Select the default\noptions during install. The install process includes three Yes/No dialog boxes,\nthe default option for all three is "No".
\nThe OSGeo4W installer helps to install the PROJ, GDAL, and GEOS libraries\nrequired by GeoDjango. First, download the OSGeo4W installer (64bit), and\nrun it. Select and click next. In the\n'Select Packages' list, ensure that GDAL is selected; MapServer is also enabled\nby default, but is not required by GeoDjango and may be unchecked safely. After\nclicking next and accepting the license agreements, the packages will be\nautomatically downloaded and installed, after which you may exit the installer.
\nIn order to use GeoDjango, you will need to add your OSGeo4W\ndirectories to your Windows system Path, as well as create GDAL_DATA\nand PROJ_LIB environment variables. The following set of commands,\nexecutable with cmd.exe, will set this up. Restart your device\nonce this is complete for new environment variables to be recognized:
set OSGEO4W_ROOT=C:\\OSGeo4W64\nset GDAL_DATA=%OSGEO4W_ROOT%\\share\\gdal\nset PROJ_LIB=%OSGEO4W_ROOT%\\share\\proj\nset PATH=%PATH%;%OSGEO4W_ROOT%\\bin\nreg ADD "HKLM\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Environment" /v Path /t REG_EXPAND_SZ /f /d "%PATH%"\nreg ADD "HKLM\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Environment" /v GDAL_DATA /t REG_EXPAND_SZ /f /d "%GDAL_DATA%"\nreg ADD "HKLM\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Environment" /v PROJ_LIB /t REG_EXPAND_SZ /f /d "%PROJ_LIB%"\ninstall Django on your system. It is\nrecommended that you create a virtual environment for each project you create.
\nThe psycopg2 Python module provides the interface between Python and the\nPostgreSQL database. psycopg2 can be installed via pip within your Python\nvirtual environment:
...\\> py -m pip install psycopg2\nFootnotes
\n\n