Project 3

You Spin Me Round (Rough Draft)

Project alpha version due 4/9/18 at 8:59 pm Chicago time
Project final version due 4/30/18 at 8:59 pm Chicago time

Project 3 will be the second group project and the focus here will be on visualizing data with a strong geographic component, in particular tornadoes in Illinois.

You can keep your group from Project 2 or form new groups. Send Andy an email once you know your group for project 3 (even if it is the same as for project 2).
I will create groups for people that do not form groups on their own. Again the standard group size will be 3 or 4 people per group.
 
As with Project 2 you should very quickly set up a web page for your new group project and send the URL to andy. Each Friday of the project each team member should post on the project web site an overview of what he/she did on the project that week.




The data for this project is available from
http://www.spc.noaa.gov/wcm/index.html#data

with a description here
http://www.spc.noaa.gov/wcm/data/SPC_severe_database_description.pdf

The data is about 7MB total for the entire US for the last 65 years covering about 62,000 tornadoes for the entire US over that period, but only about 2,500 in IL

The data we are going to focus on includes:
    date
    time
    state
    magnitude
    injuries
    fatalities
    loss
    start lat + lon
    end lat  + lon
    length
    width



In this project we are going to take a look at data about ???


For a C you need to create a useful, responsive interactive visualization focusing on Illinois


For a B you need to add:


For an A you need to add:


Graduate Students need to add:


As with all the projects your app will be evaluated running full screen with touch interaction on the classroom wall.


For this project we may host your solution using Shinyapps.io or we may set up a local server - more information on this to come.



There are two deadlines for this project. By the first deadline you should have implemented the initial screen layout of your application and have the basic functionality allowing the user to perform an example of the various 'C' functionality. This will make sure that your group is on track and that you can focus on making a good interface and set of visualizations, not just functional ones. Personally, I think you should have the entire C functionality done at that point if you are going for an A on the project as a whole. You should make this version of the interface available on your group project page.

As part of the final turn in you should create a set of web pages that describe your work on the project. This should include:

all of which should have plenty of screenshots with meaningful captions. Web pages like this can be very helpful later on in helping you build up a portfolio of your work when you start looking for a job so please put some effort into it.

Be sure to document any external libraries or tools that you make use of - give credit where credit is due.

You should also create a 2-3 minute YouTube video showing the use of your application including narration with decent audio quality. That video should be in a very obvious place on your main project web page. The easiest way to do this is to use a screen-capture tool while interacting with your application, though you will most likely find its useful to do some editing afterwards to tighten the video up. Its also a good idea to have a video like this available as a backup during your presentation just in case of gremlins.
You may want to shoot this video on the wall itself.

The web page including screen snapshots and video need to be done by the deadline so be sure to leave enough time to get that work done.

I will be linking your web page to the course notes so please send me a nice 1920 x 1080 jpg image of your visualization for the web. This should be named p2.<someone_in_your_groups_last_name>.jpg. 



When the project is done, each person in the group should also send Andy a private email with no one else CC'd ranking your coworkers on the project on a scale from 1 (low) to 5 (high) in terms of how good a coworker they were on the project. If you never want to work with them again, give them a 1. If this person would be a first choice for a partner on a future project then give them a 5. If they did what was expected but nothing particularly good or bad then give them a 3. By default your score should be 3 unless you have a particular reason to increase or decrease the number. Please confine your responses to 1, 2, 3, 4, 5 and no 1/3ds or .5s please. Each person's score on the project will be based on the overall score for the group modified by these rankings.



Each group will show their visualization to the class and describe its features. This allows everyone to see a variety of solutions to the problem, and a variety of implementations. Rehearse your presentation ... several times. All team members are expected to participate equally in that presentation.


last revision 1/16/18