PostGIS adds geographic object support to PostgreSQL, turning it\ninto a spatial database. GEOS, PROJ.4 and\nGDAL should be installed prior to building PostGIS. You\nmight also need additional libraries, see PostGIS requirements.
\nThe psycopg2 module is required for use as the database adapter when using\nGeoDjango with PostGIS.
\nOn Debian/Ubuntu, you are advised to install the following packages:\npostgresql-x.x, postgresql-x.x-postgis, postgresql-server-dev-x.x,\npython-psycopg2 (x.x matching the PostgreSQL version you want to install).\nAlternately, you can build from source. Consult the platform-specific\ninstructions if you are on macOS or Windows.
\nPostGIS 2 includes an extension for PostgreSQL that’s used to enable spatial\nfunctionality:
\n$ createdb <db name>\n$ psql <db name>\n> CREATE EXTENSION postgis;\nThe database user must be a superuser in order to run\nCREATE EXTENSION postgis;. The command is run during the migrate\nprocess. An alternative is to use a migration operation in your project:
from django.contrib.postgres.operations import CreateExtension\nfrom django.db import migrations\n\nclass Migration(migrations.Migration):\n\n operations = [\n CreateExtension('postgis'),\n ...\n ]\nGeoDjango does not currently leverage any PostGIS topology functionality.\nIf you plan to use those features at some point, you can also install the\npostgis_topology extension by issuing CREATE EXTENSION\npostgis_topology;.
To administer the database, you can either use the pgAdmin III program\n() or the\nSQL Shell ().\nFor example, to create a geodjango spatial database and user, the following\nmay be executed from the SQL Shell as the postgres user:
postgres# CREATE USER geodjango PASSWORD 'my_passwd';\npostgres# CREATE DATABASE geodjango OWNER geodjango;\n