dssg/plenario

Name: plenario

Owner: Data Science for Social Good

Description: RESTful API for geospatial and time aggregation across multiple open datasets.

Created: 2015-07-10 14:42:51.0

Updated: 2015-11-25 03:13:12.0

Pushed: 2015-06-22 15:05:52.0

Homepage: http://plenar.io

Size: 30116

Language: JavaScript

GitHub Committers

UserMost Recent Commit# Commits

Other Committers

UserEmailMost Recent Commit# Commits

README

Plenar.io

RESTful API for geospatial and time aggregation across multiple open datasets.

This project is funded by the NSF Computer and Information Science and Engineering (CISE) Directorate through a grant to the Urban Center for Computation and Data (UrbanCCD) at the Computation Institute of the University of Chicago and Argonne National Laboratory. It is being implemented by DataMade and UrbanCCD.

For more details, see the presentation slides from Exploring Open Civic Data Through Time and Space given in June 2014.

Running locally
clone git@github.com:UrbanCCD-UChicago/plenario.git

Install support libraries for Python:

lenario
install -r requirements.txt

Create a PostgreSQL database for Plenario. (If you aren't already running PostgreSQL, we recommend installing version 9.3 or later.)

tedb plenario_dev

Make sure your local database has the PostGIS extension:

 plenario_dev
ario_test=# CREATE EXTENSION postgis;

Create your own settings.py file:

lenario/settings.py.example plenario/settings.py

You will want to change, at the minimum, the following settings.py fields:

If you want your datasets hosted on an S3 bucket, edit the fields AWS_ACCESS_KEY, AWS_SECRET_KEY, and S3_BUCKET. Otherwise, datasets will be downloaded locally to the directory in the DATA_DIR field.

Additionally, create your own celery_settings.py file:

lenario/celery_settings.py.example plenario/celery_settings.py

You probably do not need to change any values in celery_settings.py, unless you are running redis remotely (see BROKER_URL).

Before running the server, Redis and Celery also need to be running.

Initialize the plenario database by running python init_db.py.

Finally, run the server:

on runserver.py

Once the server is running, navigate to http://localhost:5001/ . From the homepage, click 'Login' to log in with the username and password from settings.py. Once logged in, go to 'Add a dataset' under the 'Admin' menu to add your own datasets.

Running with Docker

Additionally, we support installing Plenario using Docker containers. Because of the variety of PostgreSQL/Docker configuration options, there are two containers needed for Plenario. One is a Plenario web server Docker container, which we provide a Dockerfile for. The other is a PostgreSQL+PostGIS database Docker container. We recommend using helmi03/docker-postgis. Please read carefully about persisting data to the database.

  1. Boot a PostGIS/PostgreSQL setup. See above.
  2. Alter settings in settings.py.docker.
  3. Run docker build .
  4. Run docker run
  5. Congrats! Plenario should now be running in the container.

Data

New datasets are actively being added to the Plenario API. We keep track of them in this Google Doc.

Dependencies

We used the following open source tools:

Team
UrbanCCD
DataMade
Join Our Community

Join our community to hear about platform updates, new features and discuss the potential uses of Plenario. We want to start a conversation with you, the users, about what Plenario can do for you - whether you're a city manager, an app developer, a researcher, or a citizen interested in exploring open data.

Join our Google Group

Errors / Bugs

If something is not behaving intuitively, it is a bug, and should be reported. Report it here: https://github.com/UrbanCCD-UChicago/plenario/issues

Note on Patches/Pull Requests
Copyright

Copyright (c) 2014 University of Chicago and DataMade. Released under the MIT License.


This work is supported by the National Institutes of Health's National Center for Advancing Translational Sciences, Grant Number U24TR002306. This work is solely the responsibility of the creators and does not necessarily represent the official views of the National Institutes of Health.