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.
\n\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).\nPlease also consult platform-specific instructions if you are on Mac OS X\nor Windows.
\nFirst download the source archive, and extract:
\n$ wget http://download.osgeo.org/postgis/source/postgis-2.1.5.tar.gz\n$ tar xzf postgis-2.1.5.tar.gz\n$ cd postgis-2.1.5\nNext, configure, make and install PostGIS:
\n$ ./configure\nFinally, make and install:
\n$ make\n$ sudo make install\n$ cd ..\nPostGIS 2 includes an extension for Postgres 9.1+ that can be used to enable\nspatial functionality:
\n$ createdb <db name>\n$ psql <db name>\n> CREATE EXTENSION postgis;\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;.
If you have an earlier version of PostGIS or PostgreSQL, the CREATE\nEXTENSION isn’t available and you need to create the spatial database\nusing the following instructions.
\nCreating a spatial database with PostGIS is different than normal because\nadditional SQL must be loaded to enable spatial functionality. Because of\nthe steps in this process, it’s better to create a database template that\ncan be reused later.
\nFirst, you need to be able to execute the commands as a privileged database\nuser. For example, you can use the following to become the postgres user:
$ sudo su - postgres\nOnce you’re a database super user, then you may execute the following commands\nto create a PostGIS spatial database template:
\n$ POSTGIS_SQL_PATH=`pg_config --sharedir`/contrib/postgis-2.0\n# Creating the template spatial database.\n$ createdb -E UTF8 template_postgis\n$ createlang -d template_postgis plpgsql # Adding PLPGSQL language support.\n# Allows non-superusers the ability to create from this template\n$ psql -d postgres -c "UPDATE pg_database SET datistemplate='true' WHERE datname='template_postgis';"\n# Loading the PostGIS SQL routines\n$ psql -d template_postgis -f $POSTGIS_SQL_PATH/postgis.sql\n$ psql -d template_postgis -f $POSTGIS_SQL_PATH/spatial_ref_sys.sql\n# Enabling users to alter spatial tables.\n$ psql -d template_postgis -c "GRANT ALL ON geometry_columns TO PUBLIC;"\n$ psql -d template_postgis -c "GRANT ALL ON geography_columns TO PUBLIC;"\n$ psql -d template_postgis -c "GRANT ALL ON spatial_ref_sys TO PUBLIC;"\nThese commands may be placed in a shell script for later use; for convenience\nthe following scripts are available:
\nPostGIS version | \nBash shell script | \n
|---|---|
1.5 | \n\n |
Debian/Ubuntu | \n\n |
Afterwards, you may create a spatial database by simply specifying\ntemplate_postgis as the template to use (via the -T option):
$ createdb -T template_postgis <db name>\nWhen the PostgreSQL cluster uses a non-UTF8 encoding, the\ncreate_template_postgis-*.sh script will fail when executing\ncreatedb:
createdb: database creation failed: ERROR: new encoding (UTF8) is incompatible\n with the encoding of the template database (SQL_ASCII)\nThe current workaround is to re-create the cluster using UTF8 (back up any\ndatabases before dropping the cluster).
\nTo 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 TEMPLATE template_postgis ENCODING 'utf8';\n