PostGIS adds geographic object support to PostgreSQL, turning it\ninto a spatial database. GEOS, PROJ and\nGDAL should be installed prior to building PostGIS. You\nmight also need additional libraries, see PostGIS requirements.
\nThe psycopg or psycopg2 module is required for use as the database\nadapter when using GeoDjango with PostGIS.
\nOn Debian/Ubuntu, you are advised to install the following packages:\npostgresql-x, postgresql-x-postgis-3, postgresql-server-dev-x,\nand python3-psycopg3 (x matching the PostgreSQL version you want to\ninstall). Alternately, you can build from source. Consult the\nplatform-specific instructions if you are on macOS or Windows.
PostGIS 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\n\nclass Migration(migrations.Migration):\n operations = [CreateExtension("postgis"), ...]\nIf you plan to use PostGIS raster functionality, you should also activate the\npostgis_raster extension. You can install the extension using the\nCreateExtension migration\noperation, or directly by running CREATE EXTENSION postgis_raster;.
GeoDjango 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 SQL Shell\n(). For example, to create\na geodjango spatial database and user, the following may be executed from\nthe SQL Shell as the postgres user:
postgres# CREATE USER geodjango PASSWORD 'my_passwd';\npostgres# CREATE DATABASE geodjango OWNER geodjango;\n