Trip Planner Sub-projects

This is a initial attempt at defining the "parts" that make up the trip planner. Please feel free to  make suggestions about this list or modify it. You can (optionally, of course) identify the sub-projects you are interested in working on and add yourself to the ProjectMembers page.

Organization

  • In general, organizing the project
  • Defining project goals
  • Helping people get involved (helping them figure out where they fit in and how to fit them in)
  • Facilitating communication between project members

Core Library

  • Writing Python code to implement back end services
  • Testing the back end services

Web

  • Writing Python code to connect the back end to the user interface
  • Writing JavaScript code to make the UI more interactive
  • Possibly writing HTML & CSS to implement the UI design

UI Design

  • Designing the user interface
  • Possibly writing HTML & CSS to implement the UI design
  • Possibly writing JavaScript code to make the UI more interactive
  • Testing the user interface

System Administration

  • Finding suitable hosting
  • Deploying/installing the trip planner
  • Doing backups
  • Setting up and supporting sites and services, such as Trac and Subversion

Data/GIS

  • "Data wrangling"
  • Updating and maintaining datasets
  • The type of stuff Jack works on
    • Integrating data layers
    • Adding new segments
    • Creating a routeable network

Data Import

  • Importing flat datasources (i.e., shapefiles) into normalized relational databases
  • Building adjacency matrices for routing from the imported data

Database

  • Setting up and managing PostgreSQL and PostGIS
  • Making backups