Skip to content
A GeoDjango app to return Cascadia quake risk and resilience factors based on location
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

Earthquake Preparedness Web Interactive

The project will explore traditional and qualitative scoring assessments of “risk/resiliency factors” associated with regional crisis preparedness and demonstrate how actionable steps in community engagement can create a different portrait of resiliency. Stories will engage examples of communities in distinct regions across Oregon facing knowable challenges in the event of a major earthquake.


Django Web Framework

  • PostgresSQL
    • PostgresSQL in Django requires psycopg2 (but maybe we end up bypassing this or something with PostGIS?)

GeoDjango Dependencies

Note about Python Command Usage

Commands indicated are always just python but on some systems you might need to use python3 in order to use a specific python version. If so, other commands such as pip have a pip3 equivalent.

Use whichever base command is appropriate for your environment.

Configure Dev Environment

Set up a virtual environment so that you can freely install python modules without worrying about overwriting globally installed versions. It's easy!

  1. pip install virtualenv
  2. Move to the project directory (e.g. /Applications/MAMP/htdocs/cascadia).
  3. virtualenv venv –no-site-packages (doesn't need to be venv, just remember what you pick)
  4. Wait for things to happen.
  5. source venv/bin/activate (type deactivate to leave)
  6. pip install -r requirements.txt to automatically install whatever we have in our requirements.txt.
  • If you are in python3+, the wsgi install will fail. But that's okay, because you won't need it in python3. Just remove it from your local copy of the text file.

"World" App

Included is an app called World that was used to initially figure out how GeoDjango works. "Real" work will probably be taking place in another app written slightly better and with all of the datasets modelled better.

Written using:

  • Postgres version: 9.4
  • Python version: 3.4

Installing App

This assumes 'python' is the command configured to run the correct python version.

Set up the "secret key" used by Django to secure forms.

Set up the database

Note: This assumes you've got Postgres with PostGIS installed, which can be a challenge on its own!

  1. Clone repo.
  2. Create a Postgres database on the Postgres server.
  3. Set up an environment variable DATABASE_URL that will be used by the Djando Database URL app to load our databse.
  • example on Mac/Linux: export DATABASE_URL="postgres://USER:PASSWORD@HOST:PORT/NAME"
  1. Run python migrate to initialize the database's structure.
  2. Unzip the and into world/data
  3. Start a python shell with python shell
  4. Type from world import load and then to import the shapefile data into the DB
  5. Type exit() to exit the shell.

Environmental Variable Permanence

On Linux/Mac, as soon as you close your shell you lose those nice complicated database urls. Save them to your .bash_profile or equivalent.

Create a user and visit the admin screen to verify

  1. python createsuperuser
  2. python runserver (or configure another webserver) and visit http://server.ip/admin and log in with new user.
  3. Should see a list of content. Don't try to edit any DOGAMI data directly; those shapes are so complex with so many points that it's a guaranteed browser crash/freeze.

Use foreman to run the server Heroku-style

  • foreman start
    • Any errors that pop up are probably from missing modules or missing environmental variables. Read the errors!

Just check to see some very simple checking if a point falls within a shape in the DB

  1. Visit http://server.ip/zonecheck
You can’t perform that action at this time.