This buildpack overwrites Heroku's default .bundle/config to set BUNDLE_BUILD__RGEO to Heroku's build directory.
Create this .buildpacks file in the root of your project.
https://github.com/camsys/heroku-buildpack-vendorbinaries.git https://github.com/camsys/heroku-buildpack-rgeo-prep.git https://github.com/heroku/heroku-buildpack-ruby.git
Create this .vendor_urls file in the root of your project.
https://s3-us-west-2.amazonaws.com/heroku.buildpack.binaries/libjpeg-9a.tar.gz https://s3-us-west-2.amazonaws.com/heroku.buildpack.binaries/gdal-1.10.1-1.tar.gz https://s3-us-west-2.amazonaws.com/heroku.buildpack.binaries/geos-3.4.1.tar.gz https://s3-us-west-2.amazonaws.com/heroku.buildpack.binaries/proj-4.8.0-1.tar.gz
Add these files to git.
Now, set up your heroku configuration.
heroku config:set BUILDPACK_URL=https://github.com/trailheadlabs/heroku-buildpack-multi.git LD_LIBRARY_PATH=/app/lib heroku config:set GDAL_BIN=/app/bin heroku config:set GDAL_DATA=/app/share/gdal
If you haven't already set up your heroku database for postgis, you need to run the following steps. You currently must have a production level database to enable postgis.
Since postgis uses different settings in the database.yml, you need to modify the DATABASE_URL variable. Run the following command and extract the nessecary components out of it:
$ heroku config:get DATABASE_URL postgres://<username>:<password>@<host>:<port>/<database>
With those variables, run the following command
$ heroku config:set DATABASE_URL="postgis://<username>:<password>@<host>:<port>/<database>?postgis_extension=true&search_schema_path=public,postgis"
$ heroku pg:psql => CREATE EXTENSION postgis;
git push heroku master
Verify it worked
heroku run bash ~> bundle exec rails c >> RGeo::Geos.supported? => true >> RGeo::CoordSys::Proj4.supported? => true
If both of these are true, you should be ready to go.
In order to get ogr2ogr geojson to shapefile conversion to work I had to build a custom version of the libjpeg binaries.
I started with the libjpgeg 9a source tarball and built that as per the normal heroku binary vendoring process.
The major hack is that after make installing the binaries I had to create a symbolic link in the lib directory for libjpeg.so.62 to work. Then I tarred that up and put it on S3 for vendor_urls.
We found the heroku repo plugin to be useful during the debugging process :
Running the following commands let us clear out the buildpacks so that we could ensure any changes we made would be used in the next deploy:
heroku repo:purge_cache heroku repo:reset
This is really just a fork for use in Camsys applications of :
This solution draws from many people's research including
Copy the snippet above into CLI.