Picture Mapper

Picture mapper is an application for storing and viewing pictures from all over the world

Registered users can upload their pictures along with the location they were taken and add them to a global interactive map featuring users photos from around the world

Project Layout

This project uses the project layout from the Two Scoops of Django best practices guide. To create a project using this template use the following startproject command:

$ django-admin.py startproject --template=https://github.com/twoscoops/django-twoscoops-project/zipball/master --extension=py,rst,html <project_name>

To Install Picture Mapper

1. Clone the repo (https://github.com/ptink/picture_mapper.git)
2. Create a virtual environment (https://pypi.python.org/pypi/virtualenv)

3. Install dependencies:- $ pip install -r requirements.txt (Windows users: for installing Pillow activate the virtualenv and use $ easy_install Pillow This is because pip does not support eggs (https://github.com/python-imaging/Pillow#windows))

   1. The /requirements/ folder contains requirements.txt files for different environments (local, production etc).
   2. By default, requirements.txt points to local.txt, the requirements for local environments

   3. To install requirements for a different environment either -

      1. Use pip install on that specific file e.g. $ pip install -r production.txt
      2. Modify requirements.txt to point to the desired requirements file

Use the python binary in the virtual environment for the following.

4. Run syncdb:- $ python manage.py syncdb
5. Run south migrate:- $ python manage.py migrate
6. Collect static files:- $ python manage.py collectstatic

7. Point the app to the correct settings file by either -

   1. Using the runserver settings command line argument e.g. $ python manage.py runserver 127.0.0.1:8000 --settings=picture_mapper.settings.local

   2. Creating a settings.py symlink to the correct settings file -

      1. Windows cmd - $ mklink .\settings.py .\local.py
      2. Linux Terminal - $ ln -s local.py settings.py

Project Dependencies

django-south (http://south.readthedocs.org/en/latest/)

Used for database migrations

Pillow (https://github.com/python-imaging/Pillow)

Drop in replacement for PIL which is required by Django's ImageField.

django-easy-maps (https://github.com/kmike/django-easy-maps)

Useful app for embedding google maps into a page

geopy (https://github.com/geopy/geopy)

Required by django-easy-maps, python geocoding toolbox

django-braces (http://django-braces.readthedocs.org/en/v1.2.2/)

Useful when using class based views, patches several holes

django-registration (https://bitbucket.org/ubernostrum/django-registration/)

Simple drop-in registration app

django-registration-bootstrap (https://pypi.python.org/pypi/django-registration-bootstrap)

Bootstrap versions of the django-registration templates. The site presentation uses bootstrap for it's speed of creation/responsiveness so this saved some time

django-crispy-forms (https://github.com/maraujop/django-crispy-forms)

required by django-registration-bootstrap. Also very useful for configuring forms

Notes

The SECRET_KEY in /settings/base.py is for local and testing use ONLY. In a production setting you should override this (and any other sensitive settings information) using environment variables

The image Exif-parsing feature (used to automatically get the lat/lng of the selected image) is pretty crude crude currently. It only works on mime-type image/jpeg and hasn't been thoroughly tested.

The global map doesn't currently have different marker colours for each user, which can make tracking down pictures difficult. Unfortunately it appears to be non-trivial to change the colour of a marker (need to use separate icons for each) so put it on the back burner for now.

There are currently no tests. This came down to a time issue, But I will be adding themas I go along.

The geodjango module provides a lot of functionality for storing/querying geographical data, and would have been good to use to allow for more complex features to be added to the app later on, but time constraints and the requirement for setting up a 'postGIS' or 'spatialite' db made it unrealistic for this project.