The Geo buildpack is deprecated. This is no longer officially supported, but feel free to fork it to make it work on the most recent stacks.
This is a Scalingo buildpack that installs the Geo/GIS libraries GDAL, GEOS and PROJ.
It can be used to get GeoDjango or RGeo running on Scalingo.
PostgreSQL includes several extensions. PostGIS is an extension to handle geospatial data. After adding a PostgreSQL database to your application, you can enable the PostGIS extension with:
$ scalingo --app my-app pgsql-console
> CREATE EXTENSION postgis;
Next step is to install the libraries Django requires to manipulate these data.
These libraries are proj, geos and gdal. Considering that they are not used commonly, they are not included in our default environment so you need to install them at deployment time.
To deploy an application with these libraries you need to use an additional buildpack along with the default Python buildpack.
Reminder: a buildpack is a piece of software able to detect and install dependencies of a given technology. More information about Scalingo's buildpacks.
Create a .buildpacks
file at the root of your project with the following content to make use of the multi buildpack:
https://github.com/Scalingo/geo-buildpack
https://github.com/Scalingo/python-buildpack
git add .buildpacks
git commit -m "Use geo-buildpack as long as python-buildpack"
git push scalingo master
Then you'll see in your deployment output:
=====> Downloading Buildpack: https://github.com/Scalingo/geo-buildpack.git
=====> Detected Framework: geos/gdal/proj
Using geos version: 3.4.2
Using gdal version: 1.11.1
Using proj version: 4.8.0_1
...
The buildpack will install the following version by default:
GDAL - 2.4.0
GEOS - 3.7.2
PROJ - 5.2.0
You can change the version of each library that will be installed by setting the
GDAL_VERSION
, GEOS_VERSION
or PROJ_VERSION
config variables.