Final Project

Project Overview

Objective

The objective of the final project is for you to work with your instructor to find a community based data visualization research project. The project work entails:

  • technical deliverables back to the community (maps, posters, data-layers, web pages etc.);
  • a theoretical essay (referenced with course-based theoretical material) to hand in with the technical community deliverables to your instructor, and
  • a presentation to the class (and if applicable to the community) of your work.

Examples of previous community projects are listed below.

Due

Nov. 29 in class time: Presentation of project is scheduled for the last class. I will extend class time from 12-6 to fit all projects and students in, and I will split the class in half, and have students sign up for the first or second half. For SEEDS projects, or other community based projects, your community partners can come to this class for the presentation.

Wed Dec. 14 1:00 in main office (office closes at 2): where applicable, paper copies of technical deliverables and paper copy of theoretical essay are due to my box in the main office.  Interactive maps, executive summary, and code can be emailed or posted to your blog site.

Grade

35% of your final mark encompassing the three components of the project:

  1. presentation, (10% of the mark out of 35)
  2. technical geospatial data visualization, (60% of the mark out of 35)
  3. Write-up (30% of the mark out of 35)

Late penalty: 1% /day, weekends = 1% (one mark off your mark out of 35)

Project Details

  1. Picking a Community

Ultimately, you should find a community to work with, however this is not mandatory.  Some of these projects are in groups, some are done individually. Once you have a project idea, you are expected to review the project idea with your instructor and the instructor will guide you as to the legitimacy of the project, scope of the project, expectations for the project, and if the project merits group work or individual work.

  1. Working with communities

When working with a community partner, whether in a group or alone, here are some steps for follow:

a) Review any information you have on the community. Get to know your community.

b) Set up an initial meeting with the community partner. At the meeting discuss:

Deliverables:

  • What does the community want:  paper, digital, interactive, big, small?
  • An infographic or map?
  • Do they need an 8.5×11″ black and white map to photocopy cheaply?
  • A brochure folded, double sided?
  • A colour map? A poster (either 11×17 or, we have a big plotter in geog)
  • A web based static map? An interactive map? Google ap map?
  • Or what combination of the above.
  • What other visuals could you create – photographs, graphs?
  • digital files: what format?
  • maintenance and updating: how is the community partner going to be able to update the deliverable – if necessary.

Budget:

  • Can they pay for printing if a poster is required? or a brochure?

Data:

  • What data does the community have, what is the format of the data
  • Is the data digital, paper maps, tables of coordinates.
  • How much of the data are you given versus have to create through field work
  • What other sources of data can you think of that may be useful for the project (for example, openstreetmap, DMTI base data, National Topographic Series data, world datasets from ESRI, etc.

Expectations:

  • What is reasonable for you to do for a school project (ie be careful with your commitments)
  • Make sure you review your project and deliverables with your instructor.

3.  Process

Set up how you will communicate with the community partner for input during the mapping process. For example:

  • an initial meeting to review deliverables and and data, e-mail.
  • email communication re progress
  • a meeting to review drafts of deliverables
  • email of progress
  • final meeting to hand off deliverables, or present deliverable to community

4. Deliverables for Project (Marking)

  • Technical Work (one per group)

You may use any technical software for mapping GIS work.

If you are doing a group project, only one copy of the technical deliverable has to be handed in.  All members of the group will receive the same grade on the technical aspects of this project. If you are writing code, you must include your code and supporting documentation embedded in your code.

(You will include information on your data on your blog site in your project summary: where did you acquire your data, how did your parse, filter, mine your data – similar to the metadata you did for your infographics)

  • Write-up (individual, one per student, for Sally, optional to post on blog site)

Approximately 3,000 words, double spaced paper discussing your project and geospatial data visualization pipeline design decisions, focusing on the representation and interaction decisions. Your discussions must draw from the lecture material and readings throughout the term, and from the course textbooks (Cairo and Tufte and general cartography texts all on reserve in the GIC)  as well as research articles that you find relevant to your particular topic when you discuss your mapping process and design decisions.
The paper must be properly referenced.
EVERY student, even in the group projects, must hand in an individual essay which is your own work. These will be individually graded for group projects and members of the same group will not receive the same mark.
If you worked with a community partner, you include in this section a brief discussion or reflective learning about working with a community partner.

You have to present your project in lecture time, during the last week of classes. Your allotted time is 10 minutes. Plan for speaking for 5-7 minutes with time for some questions. Group projects have longer time – plan for 5 minutes times the number of students, add 3 min per person for questions at the end.

For your presentations, describe your project: your community partner or idea/audience; your deliverables, and how you achieved this – data, software, cartographic considerations. If you have specific questions for feedback, let us know.

  • Executive Summary/Project Summary (group work)

This is for your portfolio/blog site, and for your community partner, that will accompany and explain your technical project. The executive summary should be approximately 500-1000 words, or be 1-2 pages double spaced.

Generally, describe your project, and summarize the process/methodology (community partner meetings, geospatial data pipeline steps…), discuss any design decisions, and any limitations of your project. The project or executive summary will be similar to what you will present to the class.

  • Other

In some discussions with community partners, there were other deliverables outlined – mostly your technical datasets (AI files, ArcGIS shapefiles zipped, code). The deliverables are for you and your community partner to clarify but please where applicable ensure you deliver to your community any datasets that will allow them to build on this project in the future.

Examples of Community projects 

2016 Community Based Reserach Projects

UBC SEEDS projects

2014 Community Based Research Projects

  • UBC sponsored Special Olympics – series of maps

2013 Community Based Research Projects

  • Grouse Mountain: snowshoe map
  • Neighbourhood group: traffic calming
  • LadySport running map
  • City of Victoria Heritage Trust with 200 level Civil Engineering Class (Hayley, Anson Lau, Andrew, Hannah Guo)

2012 Community Based Research Projects

  • Stanley Park Ecological Society
  • Red Cross Mapping Project
  • Barnston Island Mapping with Metro
    Vancouver
  • South Vancouver Food Security
  • Department of History UBC: Selden Map (Tim Brooks)
  • Carbon Emmissions and Climate Change (Simon Donner)