Because GeoDjango takes advantage of the latest in the open source geospatial
software technology, recent versions of the libraries are necessary.
If binary packages aren’t available for your platform, installation from
source may be required. When compiling the libraries from source, please
follow the directions closely, especially if you’re a beginner.

PostGIS is recommended, because it is the most mature and feature-rich
open source spatial database.

The geospatial libraries required for a GeoDjango installation depends
on the spatial database used. The following lists the library requirements,
supported versions, and any notes for each of the supported database backends:

Like other Django contrib applications, you will only need to add
django.contrib.gis to INSTALLED_APPS in your settings.
This is the so that gis templates can be located – if not done, then
features such as the geographic admin or KML sitemaps will not function properly.

By far, the most common problem when installing GeoDjango is that the
external shared libraries (e.g., for GEOS and GDAL) cannot be located. [1]
Typically, the cause of this problem is that the operating system isn’t aware
of the directory where the libraries built from source were installed.

In general, the library path may be set on a per-user basis by setting
an environment variable, or by configuring the library path for the entire
system.

A user may set this environment variable to customize the library paths
they want to use. The typical library directory for software
built from source is /usr/local/lib. Thus, /usr/local/lib needs
to be included in the LD_LIBRARY_PATH variable. For example, the user
could place the following in their bash profile:

On GNU/Linux systems, there is typically a file in /etc/ld.so.conf, which may include
additional paths from files in another directory, such as /etc/ld.so.conf.d.
As the root user, add the custom library path (like /usr/local/lib) on a
new line in ld.so.conf. This is one example of how to do so:

$ sudo echo /usr/local/lib >> /etc/ld.so.conf
$ sudo ldconfig

For OpenSolaris users, the system library path may be modified using the
crle utility. Run crle with no options to see the current configuration
and use crle-l to set with the new library path. Be very careful when
modifying the system library path:

GeoDjango uses the find_library function (from the ctypes.util Python
module) to discover libraries. The find_library routine uses a program
called objdump (part of the binutils package) to verify a shared
library on GNU/Linux systems. Thus, if binutils is not installed on your
Linux system then Python’s ctypes may not be able to find your library even if
your library path is set correctly and geospatial libraries were built perfectly.

The binutils package may be installed on Debian and Ubuntu systems using the
following command:

Although OS X comes with Python installed, users can use framework
installers provided by the Python Software Foundation. An advantage to
using the installer is that OS X’s Python will remain “pristine” for internal
operating system use.

Примечание

You will need to modify the PATH environment variable in your
.profile file so that the new version of Python is used when
python is entered at the command-line:

Postgres.app is a standalone PostgreSQL server
that includes the PostGIS extension. You will also need to install gdal and
libgeoip with Homebrew.

After installing Postgres.app, add the following to your .bash_profile so
you can run the package’s programs from the command-line. Replace X.Y with
the version of PostgreSQL in the Postgres.app you installed:

exportPATH=$PATH:/Applications/Postgres.app/Contents/Versions/X.Y/bin

You can check if the path is set up correctly by typing whichpsql at a
terminal prompt.

Homebrew provides “recipes” for building binaries and packages from source.
It provides recipes for the GeoDjango prerequisites on Macintosh computers
running OS X. Because Homebrew still builds the software from source, the
Apple Developer Tools are required.

Proceed through the following sections sequentially in order to install
GeoDjango on Windows.

Примечание

These instructions assume that you are using 32-bit versions of
all programs. While 64-bit versions of Python and PostgreSQL 9.x
are available, 64-bit versions of spatial libraries, like
GEOS and GDAL, are not yet provided by the OSGeo4W installer.

First, download the latest Python 2.7 installer from the Python website.
Next, run the installer and keep the defaults – for example, keep
‘Install for all users’ checked and the installation path set as
C:\Python27.

Примечание

You may already have a version of Python installed in C:\python as ESRI
products sometimes install a copy there. You should still install a
fresh version of Python 2.7.

First, download the latest PostgreSQL 9.x installer from the
EnterpriseDB website. After downloading, simply run the installer,
follow the on-screen directions, and keep the default options unless
you know the consequences of changing them.

Примечание

The PostgreSQL installer creates both a new Windows user to be the
‘postgres service account’ and a postgres database superuser
You will be prompted once to set the password for both accounts –
make sure to remember it!

When the installer completes, it will ask to launch the Application Stack
Builder (ASB) on exit – keep this checked, as it is necessary to
install PostGIS.

Примечание

If installed successfully, the PostgreSQL server will run in the
background each time the system as started as a Windows service.
A PostgreSQL 9.x start menu group will created
and contains shortcuts for the ASB as well as the ‘SQL Shell’,
which will launch a psql command window.

After clicking next, you will be prompted to select your mirror, PostGIS
will be downloaded, and the PostGIS installer will begin. Select only the
default options during install (e.g., do not uncheck the option to create a
default PostGIS database).

Примечание

You will be prompted to enter your postgres database superuser
password in the ‘Database Connection Information’ dialog.

The psycopg2 Python module provides the interface between Python and the
PostgreSQL database. Download the latest Windows installer for your version
of Python and PostgreSQL and run using the default settings. [2]

The OSGeo4W installer makes it simple to install the PROJ.4, GDAL, and GEOS
libraries required by GeoDjango. First, download the OSGeo4W installer,
and run it. Select Express Web-GIS Install and click next.
In the ‘Select Packages’ list, ensure that GDAL is selected; MapServer and
Apache are also enabled by default, but are not required by GeoDjango and
may be unchecked safely. After clicking next, the packages will be
automatically downloaded and installed, after which you may exit the
installer.

In order to use GeoDjango, you will need to add your Python and OSGeo4W
directories to your Windows system Path, as well as create GDAL_DATA
and PROJ_LIB environment variables. The following set of commands,
executable with cmd.exe, will set this up:

For your convenience, these commands are available in the executable batch
script, geodjango_setup.bat.

Примечание

Administrator privileges are required to execute these commands.
To do this, right-click on geodjango_setup.bat and select
Run as administrator. You need to log out and log back in again
for the settings to take effect.

Примечание

If you customized the Python or OSGeo4W installation directories,
then you will need to modify the OSGEO4W_ROOT and/or PYTHON_ROOT
variables accordingly.