Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
45 changes: 25 additions & 20 deletions 02_activities/assignments/assignment_2.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,27 +10,32 @@
- For each visualization (good and bad):
- Explain (with reference to material covered up to date, along with readings and other scholarly sources, as needed) why you classified that visualization the way you did.
```
Your answer...







Example: [Gapminder: Wealth & Health of Nations](https://www.gapminder.org/tools/#$chart-type=bubbles)

This interactive bubble chart by Gapminder effectively communicates the relationship between life expectancy and income per person across countries and over time. According to the principles discussed in the “05_customizing_our_plots” and “09_beyond_matplotlib” slides:

1. Clarity and Simplicity: The visualization uses clear axes, labels, and a legend, making it easy to interpret. The use of color and size encodes additional variables (region and population), as recommended in the slides for encoding multiple variables visually (see Seaborn scatterplot and relplot examples).
2. Interactivity: Users can filter, animate, and explore the data, which aligns with the benefits of dynamic visualizations discussed in “09_beyond_matplotlib.pdf” (e.g., supporting transparency, engagement, and exploration).
3. Accessibility: The chart uses distinguishable colors and provides tooltips, supporting accessibility and user engagement, as emphasized in the course materials.
4. Storytelling: The animation over time helps tell a compelling story about global development, which is a key goal of effective data visualization (see “telling a story” in the assignment rubric).

References: “05_customizing_our_plots.pdf” and “09_beyond_matplotlib.pdf” (course slides)
```

- How could this data visualization have been improved?
```
Your answer...






Example: 3D Pie Chart of Market Share (as seen in many business reports)

A 3D pie chart is often cited as a poor practice in data visualization, and this example demonstrates several issues:

1. Distortion and Misleading Perception: The 3D effect distorts the size of the slices, making it difficult to accurately compare values. This violates the principle of clarity and accurate mapping between data and visual elements (see “semantic mapping” in the slides).
2. Overuse of Color: Too many similar colors make it hard to distinguish between categories, which is discouraged in both “05_customizing_our_plots” and “09_beyond_matplotlib” (see the discussion on color palettes and accessibility).
3. Lack of Labels and Legends: Often, 3D pie charts omit clear labels or legends, forcing users to guess what each slice represents, which goes against the best practices for axis labeling and legends.
4. No Story or Context: The chart does not provide context or highlight key insights, failing to support data-driven storytelling.

References: “05_customizing_our_plots.pdf” and “09_beyond_matplotlib.pdf” (course slides)
```
- Word count should not exceed (as a maximum) 500 words for each visualization (i.e.
- Word count should not exceed (as a maximum) 500 words for each visualization (i.e.
300 words for your good example and 500 for your bad example)

### Why am I doing this assignment?:
Expand Down Expand Up @@ -59,9 +64,9 @@
* Open a private window in your browser. Copy and paste the link to your pull request into the address bar. Make sure you can see your pull request properly. This helps the technical facilitator and learning support staff review your submission easily.

Checklist:
- [ ] Create a branch called `assignment-2`.
- [ ] Ensure that the repository is public.
- [ ] Review [the PR description guidelines](https://github.com/UofT-DSI/onboarding/blob/main/onboarding_documents/submissions.md#guidelines-for-pull-request-descriptions) and adhere to them.
- [ ] Verify that the link is accessible in a private browser window.
- [x] Create a branch called `assignment-2`.
- [x] Ensure that the repository is public.
- [x] Review [the PR description guidelines](https://github.com/UofT-DSI/onboarding/blob/main/onboarding_documents/submissions.md#guidelines-for-pull-request-descriptions) and adhere to them.
- [x] Verify that the link is accessible in a private browser window.

If you encounter any difficulties or have questions, please don't hesitate to reach out to our team via our Slack. Our Technical Facilitators and Learning Support staff are here to help you navigate any challenges.