Reflection: Data Visualization Dos and Don’ts

The Minard Map: Why is it considered such a landmark visualization?

My first look at the Charles Minard’s Flow Map of Napoleon’s Russian Campaign of 1812 had me a bit confused. After reading the description and taking a closer look at the labels, it began to make more sense—but that took some time. This visual is unique in how it represents geographical location, population of troops during the campaign (those leaving and coming), as well as temperature over time. The way that this map combines so many (and such varied) elements makes it a uniquely powerful visual. But the maps complexity and dependence on its description can make it a bit more time-consuming for viewers. I can see how the visual is unique and powerful, but for me, it took more than a couple of minutes to understand whats going on in the image. I would argue that intuitiveness and understandability are also crucial parts to data visualization, and Minard’s map slightly lacks those aspects. I could see how with more modern technology and perhaps some larger, clearer labels, the map could be more easy understandable on first glance.

Data Visualization and Digital Humanities

As I continue to look at data visuals and begin to make them, I want to keep in mind the importance of conveying information with the argument that it makes in mind. The way that we portray data often has a point of view behind it, and I want to make sure that I am keeping my visuals honest while also putting forth the argument that I want my viewers to grasp. I also really liked Lin’s points about how a lack of data can also have a significant importance, so keeping in mind that just because there is no data on something doesn’t mean I shouldn’t point that out. Lastly, I liked Lin’s emphasis on making data visuals as intuitive and clear as possible. As Tufte points out, staying away from redundancies in how you represent different dimensions of data keeps things cleaner.

3 thoughts on “Reflection: Data Visualization Dos and Don’ts

  1. I like how you pointed out the importance of data visualization graphics being intuitive. I also felt like the visual contained a lot of information, but at first glance it was difficult to understand what was being presented. I feel like an important aspect of data visualization is grabbing the viewer’s attention and transmitting a message quickly- the coded version of the graphic helps do this a little better.

  2. I agree with your point that intuitiveness and understandability are the most crucial part of data visualization, since the purpose of graphs is to convey information. I also feel like better design helps to grasp the attention of the viewers, making them look at the graphs longer and potentially better understand the message contained.

  3. I too was confused initially on this map and agree that being quickly intuitive is important for visualizations. Especially in papers or long blog posts, most viewers might look briefly at a graphic and get scared away if it is right away difficult to understand. Trying to balance the information and creative aspect of the map while keeping it intuitive is tough but important

Comments are closed.

css.php