Skip to main content
Data Visualization and Interpretation

Data Visualization: Taxonomy and Tools

Published: 2026-08-11
Level: postgraduate
Audience: Postgraduate students learning data visualization and interpretation

Prerequisite Knowledge

This lecture builds on the following concepts from earlier lectures. If any feel unfamiliar, review the linked notes before proceeding.

Previously Covered in This Subject

  • Storytelling and the three-phase story structure — covered in Lecture 3
  • Chart taxonomy: dot plots, bar charts, and floating charts — covered in Lecture 3
  • The chart choice belongs to the audience — covered in Lecture 3
  • Clutter and pre-attentive attributes — covered in Lecture 2
  • Tableau foundations: sheets, filters, and exporting — covered in Lecture 1

Data Visualization: Taxonomy and Tools

4.1 Where We Are and Where We Are Going

4.1.1 The Plan for Today

Why this session exists: you already know which charts exist and how to tell a story with them. This session answers the next question: which graph do I actually reach for, and which tool do I build it in? By the end you should be able to look at a dataset, ask what relationship you want to show, and pick a sensible chart — then name the tool that can build it.

This session closes out the taxonomy topic and opens the door to the tools of the trade. The agenda runs like this: a quick recap of the last session (storytelling and the taxonomy of charts), a refresh of the fundamental building blocks — data types, relationships, and complexity — because they are not part of the course handout but they decide which graph you reach for, then a few short live demos comparing graphs on real data, a small quiz of four or five questions to lock it in, and finally, in the second half, a survey of what data visualization tools exist in the market today, including a look at the Gartner quadrant, which classifies tools as emerging, gaining popularity, or leaders.

The tools topic was pulled forward from the next session on purpose. The taxonomy material is light and nobody benefits from staring at slides for two hours, so the plan is: see the whole tool landscape today, go deeper into individual tools in the next session (desktop-based tools, online visualization tools, their libraries, and open source versus proprietary options), and from the sixth session onward, zoom into Tableau desktop with live demos and hands-on work.

Think of the arc this way: the taxonomy is the theory of choosing (which chart for which job), today is the market tour (what tools exist), and the coming sessions are the hands-on practice (building charts yourself). Each stage builds on the previous one, so the recap matters — the building blocks we refresh now are the ones every chart decision in the demos will lean on.

4.1.2 Recap: Storytelling and Chart Taxonomy

Last session we covered storytelling and its three sections. First comes the setup, where we start and give the context. Then the conflict, where the challenges are discussed. Then the agreement, where the story ends with actions and what we will do next. We also went through the do's and don'ts of storytelling.

Recap: storytelling gives your chart a structure (setup → conflict → agreement), and the taxonomy gives you a menu of charts. The two combine into the real skill: picking the right chart for the right moment of the story.

From there we started the taxonomy of data visualization — the approach of classifying and organizing different types of charts: in what scenario, which chart usually does better. There were chart suggestions for each scenario. We looked at a few charts in detail — the dot plot, the bar chart, and the floating chart (a floating chart is one not tied to an axis baseline; it floats). For each chart we noted the pros, the cons, and the scenarios where it fits. The course material for this section is available in the file section if you want to revisit it.

Two memory hooks for the recap:

  • Bar chart — a bar starts at zero on the axis, so its length encodes the value directly. If you want exact magnitudes, this is the workhorse.
  • Floating chart — a bar (or line segment) that does not start at zero; it stretches from a low value to a high value. Because it floats, it shows a range (like a project span from start date to end date) rather than a single total. The trade-off: you lose the zero baseline, so you lose quick absolute comparisons.

That contrast — length from a common baseline versus a floating range — is a preview of a theme running through the whole taxonomy: every chart choice trades some kind of precision for some kind of clarity, and the right pick depends on the message.

4.1.3 Getting Tableau Desktop

Before the recap began, there was a practical check on tool access. The institute has an analytics lab, and students can register there for a Tableau Desktop license. One student had already registered and received an email with a product key, though installation was still pending. The key opens the desktop version free for one year. When you launch the product (it arrives as a typical executable), it asks for the key, and for a year you can use all of the features on your own. The key expires after a year and can be renewed. If you are stuck, reach out to the batchmates who already have it.

Q: I have registered for the license and got an email with a product key, but I have not installed it yet. How does the installation work?

A: The product comes as a normal executable. The moment you launch it, it will ask for the key you received in the mail, and then for a year you can access everything yourself. My own key expired yesterday and I was able to renew it, so the renewal path works. If anyone in the batch needs help with the process, help them out — and share the details of how to get the key.

Practical notes worth keeping:

  • The license is free for one year from the moment you activate it, covering every feature of the desktop product.
  • When the year ends, the key expires and can be renewed — renewal was confirmed to work, so plan to renew rather than pay.
  • The class is a support network: if you cannot install or activate, ask batchmates who already did it. Do not sit stuck on a tool-access problem; it is a solved problem for half the batch.

This session's live demos all run inside Tableau Desktop, so having it installed before the next session means you can follow along hands-on instead of just watching.

4.1.4 What This Session Builds Toward

Keep the session map in mind as you read on: the first half (sections 4.2–4.12) rebuilds the decision framework — data types, relationships, complexity — and tests it with demos and a quiz. The second half (sections 4.13–4.14) tours the tool market and gives you criteria for choosing a tool. The quiz in section 4.12 is not a trap; it is the study material — each question's reasoning shows you exactly how the framework turns into a chart choice.

4.2 Data Types: The Four Building Blocks

4.2.1 Categorical Data

The question that starts every chart: before touching a tool, ask what kind of data sits on each axis. If the axis holds labels, the chart must treat them as labels; if it holds numbers, as numbers. Everything in this section is a way of making that first question fast to answer.

Categorical data is data made of distinct categories — labels rather than numbers. A chess game, for example, has moves with statuses; the statuses are labels, and then there are counts around those labels. "Small, medium, large" are labels. Movie genres are labels. Anything category-based with labels counts as categorical data.

In the reference literature this kind of data is often called categorical-nominal (nominal means "named"): the values name a group — country, gender, movie genre — and the names carry no number at all. Think of a dataset of movies: genre is categorical (Drama, Comedy, Sci-Fi), studio is categorical, but box office revenue is not.

Two properties matter. First, there is no required order — the sequence of the categories does not matter, so the data need not be sorted. A bar chart with "Comedy" on the left and "Drama" on the right tells the same story either way; sorting is a choice you make to help the eye, not a requirement of the data. Second, because the number of labels is usually small, categorical data is typically visualized with bar charts, pie charts, or heat maps. A pie chart can handle a small number of labels well.

Rule of thumb for categorical data: the chart's job is comparison of groups, not reading of values along a scale. A bar chart compares group sizes by bar length; a pie chart shows each group's share of a whole; a heat map colors each group by its value. All three assume a small number of groups.

There is a catch worth repeating: pie charts should be used sparingly when there are a lot of data points. Our brain struggles with angular formatting — it cannot easily compare magnitudes by looking at slice angles. A pie chart works when you are visualizing a whole: out of a hundred percent, how much of it belongs to each value. For anything with too much context, a bar chart or another graph serves better.

Pitfalls for categorical data:

  • Too many categories in a pie. Five slices are already hard to judge; ten slices turn into a guessing game. Count the labels first — if there are many, switch to a bar chart.
  • Assuming categories have an order. Sorting "small, medium, large" alphabetically (large, medium, small) would be fine for nominal data but wrong for data that is secretly ordinal — check whether the labels sit on a scale before sorting.
  • Encoding a label as a number by mistake. If a column stores "1" for male and "2" for female, the tool may treat it as numerical. Set the field's type to categorical before charting, or the axis becomes a meaningless number scale.

4.2.2 Numerical Data: Discrete and Continuous

Numerical data is data that can be measured — straightforward. The one level of detail worth keeping is that numerical data splits into two kinds. Discrete data is whole numbers — counts like the number of people or the number of cars. Continuous data can take any value within a range, including decimals — a share price or a temperature, for example.

A clean way to separate them: counts are discrete, measurements are continuous. You can have 3 people in a room or 4, but never 3.5 people; you can have a temperature of 21.7 °C or 21.73 °C. The reference material draws the same line with the terms interval-scale (dates, temperature — equal gaps, no true zero) and ratio-scale (prices, age, distance — has a meaningful zero, so ratios like "twice as old" make sense). The professor's discrete/continuous split is the everyday version of this distinction, and it is the one you will actually click in a tool.

This distinction is not just theory. In Tableau — and in any data visualization tool worth its name — when you select a numerical field you get the discrete and continuous options, and you decide in what form to show the value. You are telling the tool how to treat the field.

Why the tool asks you: the same numbers can be drawn two ways. Treat a date field as discrete and you get one bar (or point) per value — a stepped, separated look; treat it as continuous and the values flow along a scale — the smooth line you expect from a trend. You are not changing the data; you are choosing the visual treatment, and the tool respects your call.

Pitfall: forgetting to set the field type. A year column (2021, 2022, 2023) is often auto-detected as a number. If you want the time behavior — a continuous time axis, sensible yearly buckets — you must tell the tool it is a date. The auto-detection is a guess, not a decision; make the decision yourself.

4.2.3 Ordinal Data

Ordinal data looks like categorical data, but with a key difference: it has a sequence, an order — that is why it is called "ordinal." The order only makes sense when you sort the values. Surveys are the classic example: "strongly agree, agree, neutral, disagree, strongly disagree" sits on an underlying scale, and the sequence matters. Because the ordering matters, ordinal data is usually visualized with a bar chart or a box plot.

The reference taxonomy calls this categorical-ordinal, and the classic example is Olympic medals: gold, silver, bronze. They are labels (you cannot compute "gold + silver"), but their order is fixed — bronze is below silver, silver below gold. Likert-scale survey responses ("strongly agree" through "strongly disagree") work the same way.

Analogy: ordinal data is a queue that has a front and a back but no measuring tape. You know exactly who is first and who is last, and that A beats B, but you cannot say how much A beats B by — the gap between "agree" and "strongly agree" is not a measured distance. That is why ordinal values go on a bar chart (compare positions) or a box plot (show the spread of ordered responses), not on a scatter plot that assumes measured numbers.

The one practical trap: ordinal data looks categorical, so it is easy to treat it as nominal — and then the tool sorts the labels alphabetically, and your carefully ordered scale ("strongly agree" on the left, "strongly disagree" on the right) gets scrambled into "agree, disagree, neutral, strongly agree, strongly disagree." Keep the field's order explicit, and sort the axis in the intended sequence before presenting.

4.2.4 Time Series Data

Time series data is anything where each data point is associated with a specific time. Stock price data is the classical example. Tracking your website traffic by hour is another. Temperature recorded hour by hour or minute by minute — the way weather apps show a day's temperature — is a third.

For time series, line graphs usually work best, although heat maps are also used. Typically you will see a date-time value on the X axis to make the chart meaningful. Tableau automatically categorizes a date field into years and quarters, and you can opt for the exact date instead. The same data can be drawn as a bar chart, a line chart, or a year-wise heat map — the tool leaves the choice to you, and you choose based on what you want to show. When the data is too much, the line graph is the safer default, and you can always undo and try another form.

Worked example — one dataset, three charts. Take a year of daily website visits: 365 rows, each with a date and a visit count.

  • Line chart: date on the X axis, visits on the Y axis, points joined in order. Best when the goal is the shape of the trend — a rise through autumn, a spike in December, a dip in summer. Dense data is fine; the line summarizes.
  • Bar chart per month: aggregate the 365 days into 12 bars. Best when the goal is month-by-month comparison — "June had fewer visits than March."
  • Year-wise heat map: one row per year, columns per week or month, color intensity for visit volume. Best for spotting patterns across many periods at a glance — which weeks were consistently strong.

Same data, three messages, three charts. The data type (time series) narrows the family; the message picks the member.

Pitfall — the hidden fourth dimension: time is not just another axis; it creates ordering and continuity. Two common mistakes are (1) plotting time as a plain number field so the axis loses its time buckets, and (2) joining dates across gaps (a stock price for Monday next to Friday) so the line implies a weekend that never traded. When the data is sparse or irregular, decide deliberately whether the gaps matter — and if they do, the line graph needs the dates kept as true dates.

4.2.5 Why Data Types Matter

The whole idea of reviewing data types is that the data type, seen through the X axis and the Y axis, tells you which graph to choose. With time and experience this becomes second nature, but at the very least you should know fundamentally which type of graph goes with which data type. That is the entire point: categorical needs no sequence; numerical is countable and can be discrete or continuous; ordinal is categorical with sequenced labels; time series has time attached to every point.

The four building blocks in one table:

Data type What it is Typical charts Example
Categorical (nominal) Labels with no order Bar, pie, heat map Movie genre
Numerical Measurable values Bar, histogram, scatter Price, temperature
— discrete Whole-number counts Bar Number of cars
— continuous Any value in a range Line, histogram Share price
Ordinal Ordered labels Bar, box plot Survey responses
Time series Every point has a time Line, heat map Stock price by day

Exam note: the examinable core is the mapping — for each data type, name the charts that fit it. Section 4.12's quiz tests exactly this mapping in reverse (given a question, pick the chart).

Q: Is working with these simple charts just as straightforward in Power BI as it is in Tableau?

A: Yes, exactly the same way — straightforward. You can add labels and everything, just like here. Since there are Power BI champions in this class, we can also do a small Power BI demo in the next session for comparison, although our focus will be on Tableau going forward.

4.3 Relationships in Data Visualization

Once you know the data types, the next question is: what relationship are you trying to show? Four relationship families cover most chart decisions.

The question that drives this whole section: you rarely chart data just to show the data — you chart it to show a relationship. "Compare region A with region B," "show how sales changed," "show how marks are spread," "show how variables move together." Name the relationship first, and the chart family almost picks itself. This is the professor's framing for the entire taxonomy topic: what do you want the viewer to see?

The four families — comparing magnitudes, trends over time, distributions, and correlations with networks — are deliberately the same shape as the data-type building blocks from section 4.2: the data type tells you what you can plot, the relationship tells you what you should plot.

4.3.1 Comparing Magnitudes

The first relationship is comparing the magnitude — a quantitative comparison between data points. You compare sales figures between one region and another, or sales of one product against another. The focus is on the numbers themselves.

Bar charts work well here, and pie charts work too, but with a specific job: a pie chart is a whole-to-part view. If a budget is 1 million, a pie chart shows how that 1 million is broken up across the different items — proportional contribution. A stacked bar can do the same job. But when you need the exact magnitude, the bar chart wins, because it tells you the number directly while a pie chart does not give you the exact magnitude. Use pie charts for proportional contributions, not for exact magnitudes.

Why bars beat pies for magnitude: a bar encodes its value in length from a common baseline — the eye reads the endpoint against the axis and gets an exact number. A pie encodes its value in angle and area — the eye judges those poorly, so it can rank slices ("this one is biggest") but cannot read them ("this one is 12"). The reference literature ranks visual variables by interpretation accuracy, and position and length sit at the top while angle sits near the bottom. That ranking is the underlying reason for the professor's rule: bar for exact magnitudes, pie for proportions.

Worked example — a 1,000,000 budget split four ways:

Item Amount
Operations 400,000
Marketing 300,000
Salaries 200,000
Training 100,000
  • Pie chart: shows each item's share of the whole — Operations is 40% of the pie. Good for "here is how the 1 million breaks down." It does not help you read "400,000" from the slice.
  • Bar chart: the bar for Operations ends exactly at 400,000 on the axis, so the magnitude is read directly and pairs with other bars instantly.
  • Stacked bar: one bar divided into four segments, each segment's length showing its share — a hybrid: still proportional, but lengths are compared against a shared total.

Sense-check: both charts use the same numbers; the difference is which question the viewer can answer. If the question is "exactly how much?", choose the bar. If it is "what is the mix?", the pie (or stacked bar) is fair.

The second relationship is trends — changes or patterns over time, exactly the time series case from the data types. Line graphs are the standard choice. An area chart is a line chart with the space under the line shaded — useful for the same trend story. A scatter plot also looks at a relationship between two things, but it need not be date-wise; it compares two variables directly. Whenever you are showing trends, these are the visualizations to consider.

The line graph's job: the X axis carries time, the Y axis carries the value, and each point is joined to the next. The eye follows the slope between points — up means growth, down means decline — so a whole dataset collapses into one readable shape. The area chart adds shading under the line: same shape, stronger sense of quantity, and a color fill that emphasizes the volume of what changed. One caution from the reference material: an area chart fills the space under the line, so its Y axis should start at zero — otherwise the shaded area misleads.

The scatter plot belongs to the same neighborhood but does a different job: it compares two variables against each other (say, price against volume) with no time requirement, so each point is a pair of values. You will meet it again in the correlation family (section 4.3.4) — a reminder that chart families overlap, and the primary message decides the home.

4.3.3 Distributions

The third relationship is distribution — the spread of values. A typical example: marks in a class. There is a spread showing how many students scored at each level. You have seen this in every organization's year-end appraisal, where management builds a bell curve and places most people in the good or strong categories, with outliers and exceptional performances at the ends. That is a distribution.

The professor's analogy — the year-end appraisal bell curve: every appraisal season, management grades a workforce so that most people land in the middle band (good or strong), a few outstanding performers sit at the top, and a few underperformers sit at the bottom. The shape of that curve — a tall middle, thin tails — is a distribution. Whenever you ask "how are these values spread out?", you are asking about a distribution, and the chart must show spread, not individual totals.

For distributions you use histograms, box plots, or density plots. This relationship family is extremely common in data visualization.

The three distribution charts, briefly:

  • Histogram: bins the values on the X axis and counts how many fall in each bin on the Y axis — the shape of the spread appears directly.
  • Box plot: compresses the spread into five numbers — minimum, lower quartile, median, upper quartile, maximum — with outliers drawn as separate points. Compact, but it hides the fine shape.
  • Density plot: a smoothed curve of the histogram — the bell-curve shape without the bin edges.

All three answer "how are the values spread?"; they differ in how much detail of the shape they keep.

4.3.4 Correlations and Networks

The fourth relationship is correlation, and with it networks. The typical graphs are heat maps, correlation charts, and network diagrams, which show the connection between one point and another. These are not the most common charts, but they are not rare either — heat maps and correlation charts are quite common. From there, the choice depends on the data, the use case, and the business case.

A Sankey diagram belongs to this family. Sankey diagrams show flow: how things flow from one stage to another and what they ultimately lead to. A classic example is immigrant flow — how many people moved where over a period. Another is a soccer world cup: all the countries, then how the teams reached the last eleven, then the semi-finals, then the final — the whole tournament as a flow. A third example breaks a country's GDP down into how much went to healthcare and the other categories. Sankey diagrams are heavily used in supply chain contexts. They are not everyday charts, and your business case may never require one, but keep them in mind — whenever you are showing any relationship, these are the possible visualizations, and the correct one depends on the data and the use case.

How a Sankey diagram carries its meaning: the chart is drawn as stages left to right, and between the stages run bands whose width is proportional to the flow. A wide band means a big flow; a band that splits into several thinner bands shows the flow dividing. That is why the immigrant-flow example works: you see, at a glance, how many people flowed to each destination. And it is why the world cup works: 32 teams enter, the bands narrow as teams are eliminated, down to two finalists and one winner. The width is the data; the shape is the story.

Q: Has anyone worked with a network graph or a Sankey diagram before?

A: If you have not seen one, here is how it looks: it shows the flow from one stage to the next. The example on screen shows immigrant flow for the last month — how things flow and what they ultimately lead to. When a soccer world cup starts, every country enters, and the diagram shows how the countries reached the last eleven, then the semi-finals, then the final. Another example shows a country's GDP broken down into healthcare and other categories. These graphs are not very commonly used, but they are used — keep them in mind.

Pitfalls for the correlation/network family:

  • Reaching for a scatter plot to prove a trend. A scatter plot shows a relationship between two variables, not a change over time. If time is the point, the line graph is the tool (this exact trap is tested in the quiz, section 4.12).
  • Heat map without a legend. Heat maps encode values in color intensity; without a scale, the viewer cannot tell a big value from a small one. Always show what the color means.
  • Treating a network diagram as an everyday chart. Network diagrams are for exploring connections — they are complex to read, so they belong in analysis contexts, not in a one-slide summary for a general audience.

Recap — the four relationship families and their standard charts:

Relationship Question it answers Standard charts
Comparing magnitudes Which is bigger, and by how much? Bar, pie (whole-to-part), stacked bar
Trends over time How does this change over time? Line, area
Distributions How are the values spread? Histogram, box plot, density plot
Correlations & networks How do variables connect? Heat map, scatter, correlation charts, network diagrams, Sankey

Exam note: expect the quiz logic to name a scenario and ask for the family or the chart — e.g., "distribution of exam scores" → histogram; "sales across regions" → bar. Know each family's standard charts (this is the listed exam guidance for this section).

4.4 Complexity: Simple, Multi-variable, Interactive

The third dimension of the recap is the complexity of the visualization — three levels running from simple through multi-variable to interactive.

The framing question: once you know the data type and the relationship, a third dial controls the chart — how much do you show at once? A single clear message? Several variables interacting? A full dashboard the user explores? The same data can be shown at all three complexity levels; the level you pick must match the audience and the moment.

4.4.1 Simple Visualizations

Simple visualizations are quick and clear — they communicate a single message, sometimes just one number or one graph. Bar charts and line graphs are the workhorses here. They are great for showing trends and comparisons, and they are easy to understand because the audience has been seeing them since school; people do not have to think too much. From the stakeholder's point of view, these are the simple class.

What makes a visualization 'simple': one message, one or two variables, no interaction. A bar chart of sales by month, a line graph of revenue over the year — the viewer extracts the message in seconds, with zero instruction. This is the default level of complexity, and it covers most business charts in the wild.

4.4.2 Multi-variable Visualizations

Multi-variable visualizations come in whenever you compare two or more variables. This is a slightly deeper analysis than the simple class. These charts can reveal complex relationships — how different values change with the variables — and they require a little more interpretation from the audience. It is not like looking at a bar chart where you immediately see that sales were high this month and low that month. But these are still very commonly used.

What 'multi-variable' adds: a second (or third) variable brings a new visual channel. Classic moves: color one series by a category, size the points by a third value, or overlay two series on one plot — the stock-price-and-volume combo from section 4.6.2 is a live example. The gain is the relationship you can now see; the cost is interpretation effort — the viewer must read two encodings at once.

The rule of thumb: if the message is one comparison → simple. If the message is how two things interact → multi-variable. The moment the audience has to work to find the message, you have probably crossed a complexity level.

4.4.3 Interactive Visualizations

Interactive visualizations are what you have seen in dashboards: filters and criteria that let users pick and choose what they look at. Interactivity helps users explore hidden insights, and it helps stakeholders get familiar with the data faster.

What interactivity buys: the chart stops being a fixed message and becomes a workspace. A sales dashboard with a region filter lets each stakeholder answer their own question — "what does my region look like?" — without a new report being built. Interactivity also helps exploration: users can drag, drop, filter, and drill down until hidden patterns surface. The trade-off is design cost and the risk of overwhelming a first-time viewer, which is why interactivity belongs in dashboards and tools, not in every chart.

4.4.4 The "Start Simple" Principle

A guiding rule applies to any kind of data visualization: start simple. Do not load the chart with everything at once — start simple, keep adding the other stuff only if needed. Keep the communication clear. Support the data and the numbers with commentary — a chart of numbers without explanation does half the job. And give the interactivity, so users can pick and choose, drag and drop, and filter on their own.

Recap — the start-simple principle, in three moves:

  1. Start simple: one clear message, the plainest chart that carries it. A bar chart that works beats a multi-layer chart that impresses and confuses.
  2. Add only if needed: a second variable, a color, an interactive filter — each addition must earn its place by adding meaning the viewer could not get otherwise.
  3. Support the numbers with commentary: every chart you present needs its message said in words. A chart without explanation does half the job — the viewer must not be left to guess why it matters.

The complexity level ladder (simple → multi-variable → interactive) is not a ranking; it is a range of tools. Professionals default to simple and climb the ladder only when the question demands it.

Pitfalls:

  • Building the full dashboard first. Adding every variable and filter to a single chart overloads it; the eye cannot find the message, and the audience stops trying. Clutter is the enemy of communication.
  • Confusing 'more' with 'better'. Interactivity and extra series feel sophisticated but cost the audience attention. If a plain line graph answers the question, the plain line graph is the professional choice.
  • Silent charts. Numbers without commentary do half the job — the chart shows what happened, the presenter must say why it matters.

The complexity dial connects forward to section 4.5: the bar-versus-pie live comparison is deliberately a simple chart demo — the professor's point is that even at the simplest level, chart choice changes what the audience can extract.

4.5 Bar Chart versus Pie Chart: A Live Comparison

4.5.1 The Setup

The hook: the same two columns of numbers, rendered two ways, gave completely different reading experiences. One chart answered "how much, exactly?" in a glance; the other answered only "which is bigger?" This live comparison turns a rule — bars for magnitude, pies for proportion — into something you have seen with your own eyes.

To show why the bar chart beats the pie chart for magnitudes, we looked at a very basic dataset — just two columns — and rendered it both ways. No rocket science, but the contrast is instructive.

The setup in detail: the dataset is deliberately minimal — one column of categories (say, two sales regions) and one column of numbers (the sales figures). Two columns is enough to make the point because the difference between the charts is not in the data; it is in how each chart asks the eye to read the same number — from a bar's length against an axis, or from a slice's angle inside a circle.

4.5.2 What the Bar Chart Gives You

With the bar chart, you can read off the exact magnitude. You can even switch the labels on, and the chart tells you directly: the value here is five, the value there is seven. The magnitude is visible in the bar length, and the number is on the chart — no guessing.

Worked example — the two-column dataset:

Region Sales (in thousands)
North 5
South 7

As a bar chart: two bars on a common axis. The North bar ends at height 5 on the Y axis; the South bar ends at height 7. With labels switched on, the numbers "5" and "7" sit on the bars. Two readings happen in one glance: North is 5, South is 7, South is 2 more. The exact magnitudes are on the chart.

As a pie chart: one circle split into two slices — North takes 5/12 of the circle, South takes 7/12. The eye sees that South's slice is bigger, but "5" and "7" are nowhere to be found; the exact numbers have been converted into angles.

Sense-check: the data is identical in both charts — the difference is that the bar chart shows the magnitudes while the pie chart only implies them. That is the whole point of the demo.

4.5.3 What the Pie Chart Hides

With the pie chart, you struggle. Is that slice really 12? At first glance you cannot make out the exact count at all. The pie tells you that this size is bigger than that one — relational size — but beyond that, exact magnitude mapping is exactly what the pie chart cannot give you.

What the pie chart actually draws: each value becomes an angle, and the angle is proportional to the value's share of the total :

For North: . For South: . The chart converts your numbers into degrees — and human eyes are poor at converting degrees back into numbers. Judging "is this slice 150° or 170°?" is far harder than judging "does this bar reach 5 or 7?" The literature on visual variables reaches the same conclusion: length against a common baseline is read accurately; angle is not.

The professor's explanation (the brain-and-angles principle): the brain simply cannot extract exact numbers from angles. When you look at a slice, you get a size comparison — this slice is bigger than that one — but the exact count never surfaces. That is not a flaw in the demo; it is how human perception works, which is why the rule follows: pie for proportions, bar for exact magnitudes.

Pitfall — many slices make it worse: the demo used just two or three values, and even then the exact counts were unreadable. With many slices, the pie loses even the rough ranking — adjacent slices blur, labels collide, and the viewer cannot say whether a slice is really 12. The professor's warning: pie charts should be used sparingly when there are a lot of data points; with many slices the pie cannot give exact counts. Switch to a bar chart (or a stacked bar for the whole-to-part story).

4.5.4 The Takeaway

So the rule holds: pie charts help with proportional contribution, while bar charts are better for precise comparison. When it comes to comparing magnitude, bar charts are preferred because the comparison is easy and exact. This is the same point that came up in the data-types recap — the brain simply cannot extract exact numbers from angles, and even a quick glance at a bar chart gives you the magnitude, with or without labels.

Recap: the same numbers, two charts — the bar chart gives exact magnitudes (length against a common axis), the pie chart gives proportional shares (angles inside a whole). When the question is how much? → bar chart. When the question is what share? → pie chart. And when the pie would carry many slices, the bar chart is the safer choice.

This is one of the rare data visualization rules that holds across every domain — it is the same reasoning financial analysts apply when comparing quarterly revenue and the same reasoning supply-chain teams apply when comparing warehouse volumes. The chart does not change the number; it changes how accurately the audience can read the number.

4.7 Histograms for Distributions

4.7.1 The Histogram Walkthrough

The hook: a histogram answers "how are the values spread?" in one glance — but it is easy to mistake it for a bar chart. The difference is not cosmetic: a bar chart compares named categories, while a histogram counts how many values fall into each interval of a number scale. The demo made that visible.

The distribution demo used a sample of grades. Select the test score field and choose the histogram option, and Tableau shows the distribution automatically — how many students scored in each category. The tool creates the bins on its own; the course material covers in detail how bins are created and what you can tune. A histogram is a fast, easily understandable way to showcase bins and the values that fall into them.

Worked example — histogram of test scores:

Setup: one field — test scores for a class (say, 30 students, scores from 40 to 100). Select the field and choose the histogram option.

What the tool does: Tableau slices the score range into intervals (bins) — for example 40–49, 50–59, 60–69, 70–79, 80–89, 90–100 — and counts how many students land in each bin. The result is a column per bin: bin on the X axis, student count on the Y axis.

Reading the shape: most students land in the middle bins (60–79), fewer at the tails (40–49 and 90–100). That is the distribution of the class — a bell-like spread with the typical student in the middle.

What you can tune: the tool creates the bins automatically, but the bin width is yours to control — wider bins smooth the shape, narrower bins show more detail. The course material covers bin creation and tuning in detail.

Sense-check: the histogram shows how many students scored in each category — it is a distribution chart (relationship family 4.3.3), not a comparison of named categories. The Y axis counts occurrences; that is what makes it a histogram and not a bar chart.

Histogram versus bar chart — the two visual tells:

  • Bar chart: X axis = categories (labels), Y axis = the value of each category. Gaps between the bars are normal; the categories are separate things.
  • Histogram: X axis = a continuous number scale cut into intervals, Y axis = how many values fall into each interval. The bars touch — no gaps — because the intervals are adjacent parts of one scale.

The professor's demo sits squarely on the histogram side: "how many students scored in each category" is a count of occurrences per interval, the defining job of a histogram.

4.7.2 Histogram versus Box Plot

Both histogram and box plot reveal distribution. The box plot shows quartiles — the top quartile and the rest — but for keeping it simple, the histogram is the better choice for the distribution of any parameter. That distinction came up again in the quiz below.

What the box plot compresses: the box plot reduces the whole spread to five numbers — minimum, lower quartile (25th percentile), median, upper quartile (75th percentile), and maximum — with outliers flagged as separate points. That is powerful for compact comparison (side-by-side box plots across groups), but the fine shape of the distribution is gone: a bimodal spread (two humps) and a flat spread can produce the same box.

Why the histogram wins for 'simple': the histogram keeps the full shape — every bin is visible, every dip and peak — so the viewer sees the distribution as it is. For any single parameter, the professor's guidance is direct: to keep it simple, the histogram is the better choice; reach for the box plot when you must compare many distributions compactly.

Pitfalls:

  • Confusing histogram with bar chart. If the X axis holds labeled categories, it is a bar chart; if it holds number intervals with touching bars, it is a histogram. Mixing them up misleads the audience about what the chart counts.
  • Bin width left on auto without a look. Automatic bins are a starting point; if the bins are too wide, real shape disappears; too narrow, the chart turns to noise. Tune the bin width and look at the shape twice.
  • Claiming 'the class is mostly good' from a tiny sample. A histogram describes the sample you fed it; distributions from small samples wobble. Let the shape speak, but respect what the sample can support.

Recap: the histogram is the fast, simple way to show a distribution — bins on the X axis, counts on the Y axis, shape at a glance. The box plot is the compact alternative built from quartiles, useful for side-by-side comparison but weaker at revealing the true shape. For the distribution of any single parameter, the histogram is the better choice — and the quiz in section 4.12.2 tests exactly this reasoning.

4.8 There Is No Single Correct Taxonomy

4.8.1 The Chart Choice Belongs to the Audience

A summary point, repeated because it matters: there is no single correct taxonomy for data visualization. We choose what is better for the situation — specifically, what the audience wants to see. If the audience wants detail, we choose one graph; if the audience is more high-level, we choose a very different one. There is no fundamental formula.

The hook: unlike a theorem in science, data visualization has no one right answer. Two analysts handed the same dataset can honestly produce different charts — one a dense scatter matrix for a technical team, one a single headline number for an executive. The chart choice belongs to the audience: what they need to see decides the graph.

Why there is no fundamental formula: every chart trades something for something. The bar chart trades space for exactness; the pie chart trades exactness for the whole-to-part picture; the heat map trades precision for pattern; the radial chart (section 4.10) trades readability for compactness. Since the trades differ, the best chart is a function of the situation — the data, the message, and above all the audience — not a fixed lookup table.

The practical consequence: when you select a chart for a stakeholder, ask what they will do with it. An executive scanning for direction needs a simple trend line; an analyst hunting for outliers needs a distribution; a regulator checking compliance needs exact numbers. Same data, different audiences, different charts — all correct.

4.8.2 The Fundamentals That Actually Move the Needle

What carries you is clarity on the fundamentals. That means controlling cluttering — not overloading the chart — understanding pre-attentive attributes (the visual properties the eye processes before conscious attention), knowing how to use color, and knowing how to use fonts. If these fundamentals are in place and you support them with the right graph selection, your data visualization and presentation skills will genuinely help your audience understand.

These small things are usually neglected. People do not give importance to them, but that is exactly the difference between a visualization that communicates and one that confuses — and learning to apply the right concepts, the right approaches, and the right chart selections is the whole purpose of the topic.

Pre-attentive attributes, defined: pre-attentive attributes (visual properties the eye processes before conscious attention) are the features your brain detects in a fraction of a second, without deliberate effort — size, color hue, color intensity, position, shape, orientation, line length, and line width. The classic demonstration: count the 3s in a block of random digits (slow and effortful), then repeat the task with every 3 colored (instant). The color did the counting for you, pre-attentively.

How they decide your chart's fate: the bar chart works pre-attentively because it encodes value in line length — a long bar is automatically read as a big value. The pie chart's angles are not pre-attentively quantifiable, which is exactly why exact magnitudes vanish in pies (section 4.5). When you design, choose encodings that match the attribute's strength: length and position for quantity, hue and shape for category.

Pitfalls — the fundamentals that are usually neglected:

  • Cluttering the chart. Every extra element — gridlines, borders, labels, legend boxes — takes brain power from the audience. Remove anything that does not add information; the reference advice is blunt: clutter is the enemy. A chart of numbers without commentary also does half the job — say the message in words.
  • Color used as decoration, not meaning. Color is the strongest pre-attentive cue, so it should be reserved for the message: highlight the series that matters, color the outlier, keep the rest neutral. Color everything and you color nothing.
  • Fonts treated as an afterthought. A readable font at a readable size is a requirement, not a style choice — small, ornate type silently destroys comprehension in a presentation.
  • Neglecting these because they are 'small.' These small things are usually neglected, but they are exactly the difference between a visualization that communicates and one that confuses. The audience's attention is finite; the fundamentals decide whether you spend it well.

Recap: there is no single correct taxonomy — the chart choice belongs to the audience and the situation. What carries you is the fundamentals: control cluttering, use pre-attentive attributes deliberately (length and position for quantity, hue and shape for category), use color and fonts with intent. Get those right and the right graph selection does the rest.

Real-world connection: this is the difference between dashboard designers whose work ships to executives and those whose work gets ignored — analytics teams that master these fundamentals produce dashboards that change decisions, because the decision-maker sees the message before they even think about the chart.

4.9 Geospatial Data Visualization

4.9.1 How Automatic Mapping Works

Geospatial data — data tied to places — is another case where the tool does the heavy lifting. Tableau is intelligent enough to map geospatial data on its own. Some datasets ship with Tableau; the demo used the world indicators dataset. When a field is geospatial, it carries a globe icon — that icon is the signal that the tool recognizes the field as location data.

The hook: in the old days, drawing a map meant joining your data to coordinates yourself. In Tableau, the moment a field is recognized as location data, the map draws itself — the tool matches standard place names against its own built-in database of coordinates and places every point for you.

How the recognition works: Tableau carries a built-in database of place names and their latitude/longitude coordinates. When you load a field like country, state, or city, the tool checks its database, finds a match for each value, and uses the stored coordinates to plot the point. The globe icon on the field tells you the recognition succeeded. The map is not an image you find — it is a chart the tool draws from your data plus its reference data.

4.9.2 The Walkthrough

Place the country field on the view and the tool draws the map automatically. Then you can ask for any parameter: show GDP and the map fills in the GDP numbers for each country; color by birth rate and the map immediately shows which countries have higher birth rates — Africa stands out at a glance. The tool has its own built-in database: the moment you enter a standard place name, it matches the name, looks up the coordinates, and places the point on the map. We do not have to do any of that complexity ourselves.

Worked example — world indicators map:

Setup: the world indicators dataset (a demo dataset that ships with Tableau). Drag the country field onto the view — the map of the world appears automatically, one point per country.

Story 1 — GDP: drag the GDP measure onto the map. The map fills in the GDP numbers for each country — the values sit on their locations, so a glance at the globe shows which countries dominate economically.

Story 2 — birth rate by color: switch the encoded field to birth rate and let the tool color the countries by its value. The map immediately shows which countries have higher birth rates — Africa stands out at a glance because its countries render in the strongest color.

Mechanics behind the scenes: the tool matches each standard country name, looks up the coordinates in its built-in database, and places the point on the map. We never touched latitude or longitude — the tool did that complexity for us.

Sense-check: the same dataset supports two different geospatial stories — exact values (GDP as numbers) and comparative values (birth rate as color). The map is the canvas; the measure and the encoding are the message.

4.9.3 Data Preparation: Use Standard Names

The one thing we must take care of is the data itself: the country, city, or state names must be the standard names — no abbreviations, no full stops. As long as the naming is standard, the tool's intelligence handles the rest. You can also switch on the labels option and the map shows the name of every location plotted.

Pitfalls:

  • Abbreviations and full stops break the match. "USA" or "U.S.A." may not resolve; the built-in database expects the standard name — the tool matches standard place names to coordinates, so the data must carry them. Clean the names before you load the data.
  • Typo = missing point. A misspelled city silently fails to plot — the map just lacks that point, with no error message. Scan for missing points after the map draws.
  • Wrong field type. If the tool does not show the globe icon, the field was not recognized as location data — check the field's type and the names before charting.

4.9.4 What to Expect with Country-Level and State-Level Data

Because the demo dataset was global, the map covered the whole globe. Had the data been India-only with different states, the map would have shown only India and created all the states within it, letting you compare state-wise data. We will see those demos in the subsequent sessions.

State-level mapping, the same logic one level down: the built-in database holds states as well as countries. Give the tool country-plus-state data (India with its states, for example) and the map zooms to India and draws all the states within it — the same name-matching and coordinate-lookup that plotted the world map now plots the states, and you can compare state-wise values the same way you compared countries.

Q: Does Power BI have a similar map feature, and how does it work?

A: Yes — Power BI has a map feature where you just click and drag, and based on the data (region-wise or whatever dimension you have) it draws the map, similar to what we just saw in Tableau.

Q: Does the raw data need to have some kind of key in it for the map to work?

A: When you clean the data in Power Query, the data should carry the right data types and nomenclature. As long as those nomenclatures are used, the tool is intelligent enough — it has its own longitude and latitude parameters — so it can create these maps. If the data goes one level down, say to states, the map already shows those as well. These things have become very straightforward these days.

Recap: geospatial visualization is the tool's job — standard place names in, automatic map out. The tool matches names against its built-in coordinate database, draws the map, and lets you encode any measure (GDP as values, birth rate as color) on top. Your only responsibility is clean, standard names; the same logic scales from world maps down to state-level maps.

Real-world connection: this is how logistics dashboards plot delivery hubs, how healthcare dashboards map outbreak spread by region, and how retail chains review state-wise sales — in every case the analyst's job is preparing standard location names, and the tool's job is drawing the map.

4.10 Radial (Polar) Charts

4.10.1 What They Are

A radial chart — also known as a polar chart — uses a circular axis instead of the typical X-Y axes. You see these more and more in reports and presentations these days, so it is worth knowing them. In one glance you can read the value and the comparison across all series.

The hook: instead of stretching along two straight axes, a radial chart wraps its values around a circle — each category gets a spoke from the center, and the value is the spoke's length. The same numbers that need a wide bar chart fit into one compact circle.

How to read one: think of the chart as a wheel. The hub is the zero point; each category has a spoke; the spoke's length (or the area it covers) is the value; the ring it sits on places it relative to the others. In one glance you can read the value and the comparison across all series — every spoke is compared against the same center, so the longest spoke is the biggest value.

4.10.2 The Strengths

First, space: the radial chart takes less room. In one space, the example chart showed five values — a bar chart would have needed far more room for the same information, even though the values are just percentages. Second, appearance: these charts are visually appealing, more attractive and engaging than a plain bar chart. Third, you can show the relationship between the series with it. For these reasons the radial chart is getting very popular, and you will see it in a lot of presentations.

Worked example — five values in one circle:

Setup: five categories (say, five expense heads), each with a percentage share of a budget — 10%, 20%, 15%, 35%, 20%.

As a radial chart: one circle, five spokes from the hub. The 35% head sticks out farthest; the 10% head barely clears the hub. All five values, plus the full comparison across them, sit inside the circle.

As a bar chart: the same five values need a panel at least five bars wide, with each bar read against the axis — roughly three to four times the horizontal space for the same information.

The catch in the demo: the values were just percentages, and even so the exact numbers did not jump out — the chart gave the shape of the comparison (which head dominates, how the rest stack up) rather than the numbers.

Sense-check: the radial chart wins on space and engagement, and the bar chart wins on exactness — which is exactly the trade the professor highlighted.

The geometry behind the space saving: a bar chart spends most of its area on the axis and the gaps between bars; a radial chart packs the same comparisons around a center, so the shape is dense. One honest caution from the reference material: segments on the outer rings end up slightly larger (because of arc length) than equal segments on inner rings — the eye can over-weight distant values, so the radial chart is for shape and rank, not for exact judgment.

4.10.3 The Limitations

The challenges are real. You cannot compare precise values — a bar graph lets you see exactly how the bars move against the axis, but with a radial chart it is difficult to pin down exact numbers. You cannot show big datasets, or the chart becomes too hard to read. And it is not yet familiar to the average audience — the chart is still gaining popularity, unlike the bar graph people have seen since school. If you use one, expect to explain it with your commentary.

Pitfalls:

  • Expecting exact numbers from a radial chart. Values are read from spoke lengths against a circular scale — the eye cannot pin down exact figures the way it reads a bar against a straight axis. If exactness matters, a bar chart is the tool.
  • Stuffing in a big dataset. Too many spokes and the circle becomes a tangled wheel — the chart collapses into noise. Radial charts fit a handful of series, not hundreds of categories.
  • Assuming the audience knows the chart. Radial charts are still gaining popularity; unlike the bar graph people have seen since school, they need an introduction. Use one and expect to explain it with your commentary.
  • Overweighting outer rings. Equal values look bigger on the outer rings (arc length again) — design with room to spare and label the values if the numbers matter.

Recap: the radial (polar) chart wraps values around a circular axis instead of straight X-Y axes — compact, engaging, good for comparing a few series at a glance. It sacrifices exact value reading, cannot scale to big datasets, and needs audience explanation. Choose it for presentations where space and appeal matter; keep the bar chart for precise comparison.

Real-world connection: radial charts are the look of modern analytics dashboards and annual reports — performance scorecards (a finance team scoring each department on the same wheel) and fitness apps (activity by hour of the day, riding the 24-hour circle) both rely on this format. A note from the reference material: radial charts work well for time when the sequence is continuous, like a 24-hour clock.

4.11 Glyph Charts

4.11.1 What They Are

A glyph chart represents data points with symbolic shapes — these symbolic markers are the glyphs. Glyph charts are useful for multivariate data and usually show the relationships between the variables. There are hundreds of chart types out there; you do not need to pressure yourself to know all of them, but this one is worth recognizing.

The hook: a glyph is a data point drawn as a symbol — and the symbol's parts can each carry a different variable. One shape, many values packed inside it. That is why glyph charts exist: they squeeze several variables into one compact mark.

What makes it a glyph chart: each data point is represented by a symbolic shape whose physical features encode values. The classic textbook example is a flower: each petal is one variable, and the petal's size is that variable's value — so a whole multivariate observation becomes a single flower. The same idea works with squares, diamonds, crosses, or stars (section 4.11.2). Because several encodings live in one shape, glyph charts usually show relationships between the variables — and they are at their best with multivariate data.

There are hundreds of chart types out there; you do not need to pressure yourself to know all of them, but this one is worth recognizing.

4.11.2 Customizing Symbols in Tableau

In Tableau you can choose the shape for each series: a square, a diamond, a cross, a star — whatever communicates best. You select the shape per series, so one series is drawn with crosses and another with stars. All of this is available inside the tool. Personally, I have not used glyph charts much, but we can look at them in subsequent sessions. Do not get biased toward one particular chart; even theoretical knowledge of the alternatives is good enough.

Worked example — shaping the series in Tableau:

Setup: a chart with several series (say, three product lines across regions).

The move: open the marks/shape control and pick a shape for each series — one series drawn with crosses, another with stars, a third with diamonds. The shape then acts as a categorical marker: viewers can tell the series apart without reading a legend line.

What this buys: shape becomes a pre-attentive attribute (section 4.8) — the eye separates the series before conscious thought. The same trick extends the symbol with size (a quantitative value) and color (another category), packing several variables into each mark.

Honest caveat from the demo: even the professor has not used glyph charts much — they are a recognized-but-rare tool. The point of the demo is not "use glyphs everywhere" but "the tool can do this, and knowing the option exists is half the skill."

Sense-check: one mark, multiple encodings (shape for series, size for value, color for category) — a glyph in miniature.

4.11.3 When They Help

Glyph charts fit when you have a lot of information to present in a compact space. Looking at too much data at once overwhelms the audience; glyph charts help you engage the end user better. They highlight relationships, they are flexible, and you can show different kinds of pictures and icons.

When glyphs earn their place: when a single compact space must carry many data points, each with several variables, and the audience should explore rather than read exact numbers. The flower glyph is a good mental model: you cannot read "petal 3 = 4.2" precisely, but you can instantly see which flowers are big all around and which are lopsided — the hierarchy (big, medium, small) is visible even when exact magnitudes are not.

4.11.4 The Limitations

The disadvantages are significant. There is a learning curve — if the radial chart is not popular, the glyph chart is the next level of unfamiliar. These graphs are not used very commonly, so they require more effort to interpret. You cannot pinpoint the accuracy or the position of the data, and with too much data there will be potential overlaps — the glyphs have a very limited set of positions, so there are scalability issues: as the data grows, interpretation gets harder. They are also not easy to design — the other graphs took seconds to build, but glyph charts take more effort because symbols, color, and size all interact. If you are not careful, you will make interpretation harder for the end user. And there is an accessibility problem: people with color blindness, or people not well versed in reading such charts, may find them a real challenge.

Pitfalls:

  • The learning curve. Glyph charts sit one level of unfamiliarity beyond radial charts — if the audience does not know the chart, it costs them effort, and most audiences will not know this one.
  • No pinpointing. You cannot pinpoint the accuracy or position of the data; glyphs communicate shape and hierarchy, not exact values.
  • Overlaps at scale. Glyphs have a limited set of positions — as the data grows, marks collide and interpretation gets harder. Scalability is the hard ceiling.
  • Design cost. The other charts took seconds to build; glyph charts take more effort because symbols, color, and size all interact — sloppy design makes interpretation harder for the end user.
  • Accessibility. People with color blindness, or people not well versed in reading such charts, find them a real challenge — shape plus color plus size is a lot to decode at once.

Recap: a glyph chart represents data points with symbolic shapes — flexible, compact, good for multivariate relationships, and capable of engaging an audience that has a lot of information to digest. But it is unfamiliar, imprecise, hard to design, and risky at scale and for color-blind viewers. Know it, respect it, and reach for it rarely — even theoretical knowledge of the alternatives is good enough.

Real-world connection: glyph-like designs appear in the OECD Better Life Index (the flower glyph in the reference material) and in modern sports analytics, where player 'radar' and glyph profiles summarize many performance variables in one compact shape — always for exploration, never for exact reporting.

4.12 Chart Selection Quiz

Four or five questions closed out the taxonomy topic, done together in class — no right or wrong pressure. Each question and its reasoning follows, because the reasoning is the study material.

How to study this section: the quiz answers are not the point — the reasoning is. Every question below shows the same three-step logic: (1) name the relationship being asked about, (2) reject the charts that serve other relationships, (3) pick the chart that serves this one. Learn that logic and any chart-selection question answers itself.

4.12.1 Best Chart for Comparing Sales across Regions

Q: Which type of chart is best suited for comparing sales figures across different regions?

A: A bar chart. We are comparing exact magnitudes across regions — a cross-comparison — and the bar chart makes that comparison easy. A line graph will not do: line is mostly for time series, and here we are not tracking one series over time. A scatter plot will not do either: we are not doing a correlation analysis. Because we are comparing magnitudes, the bar chart is the better choice.

The reasoning in three steps: the question is a magnitude comparison across categories (regions), so the bar chart family applies. The line graph is rejected because it is mostly for time series — no time axis exists here. The scatter plot is rejected because it is for correlation — no two-variable relationship is being examined. One relationship family, one correct family member.

4.12.2 Best Visualization for the Distribution of Exam Scores

Q: What visualization best reveals the distribution of exam scores?

A: A histogram. We are showing a distribution, so the histogram is the straightforward choice. A box plot could also work — it shows the quartiles, the top quartile included — but to keep it simple, the histogram is the better choice for the distribution of any parameter.

The reasoning in three steps: the word "distribution" names the relationship family directly, and the histogram is that family's straightforward chart. The box plot is the legitimate alternative — it shows quartiles — but it compresses the shape, so for a single parameter the histogram stays the better choice (the same point from section 4.7.2).

4.12.3 Time Series Plot versus Line Graph

Q: When would you use a time series plot instead of a line graph?

A: When you are showing a single variable over frequent intervals — that is the case where the time series is the better tool. Share price, market value, that kind of data. Multiple variables over time can be challenging. A correlation is not what we are showing here, and we are not showing specific discrete data points. Between the two options that mentioned "over time," the one about a single variable over frequent intervals is the right answer.

The reasoning in three steps: the question is a terminology contrast — "time series plot" versus "line graph" sound alike, so the exam needs the precise distinction: a time series plot is for a single variable over frequent intervals (share price, market value). Multiple variables over time are challenging. Correlation and discrete data points are both outside this question. The precise condition — single variable, frequent intervals — is the deciding detail.

4.12.4 Heat Maps Are Only for Categorical Data

Q: True or false: a heat map can only be used for categorical data.

A: False. We just saw a year-wise stock price heat map comparing 2021 and 2022 — the 2021 sum versus the 2022 sum per period. That is numerical time series data rendered as a heat map, and it was equally good. A heat map does not have to be limited to categorical data; depending on the value, it works for numerical data too.

This question carries a misconception correction: the claim "heat map only for categorical data" sounds plausible because heat maps often color categories, but the year-wise stock price demo (section 4.6.2) proved the claim false — numerical time series data renders just as well as a heat map. The trigger is the phrase "only for categorical data"; the resolution is that heat maps work for numerical and time series data too. Remember it as: the heat map's job is value-by-color; the data type is up to you.

Q: True or false: a scatter plot is always better than a line graph for showing trends.

A: False. Line graphs are generally better for the overall trend, while scatter plots show individual data points. If your goal is the trend, the line graph is the tool.

This question carries a second misconception correction: "scatter always beats line for trends" sounds reasonable because scatter plots are sophisticated, but the correction is the reverse — a line graph shows the overall trend better, while a scatter plot shows individual data points. The word "always" is the giveaway: the scatter plot is the right tool for point-level relationships, the line graph for trends. If your goal is the trend, the line graph is the tool.

Exam note: the quiz logic is the model for exam questions. Bar chart for comparing magnitudes across regions (line is for time series, scatter for correlation). Histogram for distributions (box plot as the alternative that shows quartiles). Time series for a single variable over frequent intervals. Heat maps work for numerical and time series data, not only categorical. Line graphs beat scatter plots for overall trends. Study the reasoning, not the answers.

4.13 Data Visualization Tools in the Market

4.13.1 The Gartner Quadrant

Ask ten people for the top tools and you will get different lists — there is no one definition of the top five or top ten. What gives a more structured view is the Gartner quadrant: Gartner evaluates the data visualization tools every year and classifies them — which tool is emerging, which is gaining popularity, which is the leader — and publishes the classification as a quadrant.

The hook: "best tool" questions have no objective answer — ask ten people, get ten lists. The Gartner quadrant exists to replace those lists with a structured yearly classification, and it is the map this whole tool tour follows.

How to read the quadrant: Gartner positions tools on two axes — completeness of vision and ability to execute — and the resulting quadrants divide tools into classes: leaders (strong on both), challengers (execute well, narrower vision), visionaries, and niche players. The professor's plain-language version maps to the same idea: which tool is emerging, which is gaining popularity, which is the leader. The classification changes every year as tools move between quadrants.

In the current quadrant, Microsoft, Salesforce, and the Tableau–Qlik pair sit in the leaders section, while other tools keep moving from one quadrant to another. This is the frame for the tour that follows. There is no sequence in the tour — Tableau first does not make it number one; the order is random.

4.13.2 Tableau

Tableau is a very powerful and very versatile data visualization tool — you have already seen a glimpse of it in the demos in this session. It is drag-and-drop driven: simple sheets, dashboards, and storylines all become easy to build. Beginners can use it, and with experience you build even the more complex reports.

A key feature beyond drag and drop is calculated fields: you write your own formulas inside the tool — "if this is greater than that, then…" — so the analysis is not limited to the fields that come with the data. On pricing, Tableau offers a free personal edition — Tableau Public, the web version — and paid plans for enterprise needs, plus student plans and corporate plans, so different users get different options.

Why calculated fields matter: a calculated field is a formula you define in the tool itself — conditional logic like "if this is greater than that, then…", arithmetic on existing fields, or date math. It converts the tool from a viewer of your columns into a place where analysis happens: the dashboard is no longer limited to the fields that come with the data.

4.13.3 Microsoft Power BI

Power BI is very popular and integrates seamlessly with Microsoft products and services. For organizations already on the Microsoft ecosystem — Excel and the rest — Power BI slots right in, which is a clear plus for those companies.

The pricing model was discussed in class because it surprises people. The desktop version — Power BI Desktop — is free for everyone. It includes Power Query, the data preparation tool, just like the one inside Excel. But when you want to collaborate with the team, share with leadership, or present dashboards to others, you need Power BI Service, and that is paid — that is where the cost comes in. Individual usage is allowed for free; sharing and circulation is what triggers the paid plans.

Q: Does Microsoft have a paid plan for Power BI, and is it for the enterprise version?

A: Yes — Power BI Desktop is free for everyone, but Power BI Service is paid. The service is where collaboration, sharing, and presenting dashboards to the team and leadership happen, and where a lot of the data cleaning and data mining work gets done. Power BI Desktop has Power Query, just like Excel, and that part is free. The cost comes in when you move to the service for circulation and team use.

Q: In the Gartner quadrant, Microsoft is first — but is that for Power BI only?

A: Good catch — it is for both Excel and Power BI together, not Power BI on its own. Many companies still use Excel for data visualization, so Excel belongs in that category too, and that is why the Microsoft position in the quadrant is wider than just Power BI.

Power BI is very powerful, with a lot of features and drag-and-drop options, and organizations already in the Microsoft ecosystem gain from that alignment. Corporate-wise, Power BI probably has a slight edge; but both tools are equally popular and very widely used.

4.13.4 Looker Studio (formerly Google Data Studio)

Looker Studio — formerly Google Data Studio — is a free and easy-to-use tool from Google. You can create basic reports and dashboards with it, and it is usually used for quick data exploration and visualization. It may not be as popular as the more mature tools, but it is widely used — you see posts and news about it in the media constantly.

When exploring it, you find you can connect Google Sheets and do almost everything the bigger tools do — but it is not as flexible or as powerful as Power BI or Tableau. For early-stage visualization and data exploration it is a good fit. And with the brand backing of Google, more features will keep coming as the competition drives it forward.

4.13.5 Grafana

Grafana is an open source platform, mostly preferred for time series data. It supports DevOps and infrastructure monitoring, and it comes with plenty of charts and plugins. It is quite powerful for its niche, though when it comes to the vast feature options and the range of data sources, it is not as versatile or as widely supported as the bigger commercial tools. It is one of the emerging open source tools — good to know about, and worth keeping an eye on. The links to these tools' websites are provided in the course material so you can explore them yourself.

4.13.6 Qlik (Qlik Sense)

While the tools so far are purely visualization tools, some tools combine a BI platform and a data analytics platform — they give much more than simple drag and drop. Qlik is one of those. Qlik Sense is a self-service BI platform: you explore and analyze data without needing technical expertise, and it offers drag and drop — but it is more than drag and drop.

Qlik is a mature product with many offerings: Qlik Cloud for cloud data integration, and Qlik Compose for data lakes and data warehouses. Qlik Sense itself also comes as an on-premises solution for highly regulated industries. That breadth is exactly why Qlik sits in the Gartner leader category.

4.13.7 Sisense

Sisense is another BI platform, quite common. It does in-memory analytics and handles very large datasets, with a very user-friendly interface and a lot of data connectors. It provides APIs and SDKs, so you can integrate its dashboards with your own data sources and write your own functions. It supports many industries and covers cloud, data connectors, and data visualization. It is a mature product and it appears in the Gartner quadrant.

4.13.8 Domo

Domo is a cloud-based BI platform with a lot of visualization options — BI, analytics, and a data foundation among its features. It is fast gaining popularity: cloud-based tools are getting easier to use, and with Domo you simply drag and drop. It is an emerging tool that can do almost everything — dashboards, reports, and very polished visualizations. There are a few versions (the details and pricing were not covered in depth), so it likely offers a basic version with enterprise options on top.

4.13.9 Infogram

Some tools are specialized, and Infogram is one of them: it is mainly used for creating infographics — where you combine graphics and information. It is very easy to use, with ready-made templates. In the live look at the tool, you pick a template, drag and drop your content, and place a line graph from the left-hand panel — you can create reports in minutes.

It has a collection of designer templates, supports animation and interactive charts with very little effort, and can produce infographics, reports, slides, dashboards, and even maps. It can integrate with social media. A lot of players are emerging in this space, and Infogram is a good one to familiarize yourself with.

4.13.10 ChartBlocks

ChartBlocks lets you create interactive charts with a lot of customization, and you can embed the charts in websites and other applications. It is gaining popularity, with templates and drag-and-drop that make it easier to use than the big platforms. It is not as powerful or mature as Power BI or Tableau, but for small-scale needs — when your requirement does not involve very complex financial models and heavy graphs — these tools offer good, easy options. It will have paid options of its own, but the pricing plan was not covered in depth.

4.13.11 Flourish

Flourish is built for data storytelling: you create interactive data stories with a lot of templates. It is mainly for storytelling — it may not have all the analytical machinery of the big BI tools — but the story-building is excellent. You drag and drop to make bar charts, magic charts, animated 3D graphs, survey data, interactive timelines that change with time automatically, and story maps.

The demo walked through a real story: population by country, then zooming into urban population, then into Asia and Europe, then ordering highest to lowest. The story navigates, the graphs animate with real data — for example, how different countries' GDP moved across the years, with the year changing on screen and the countries moving in the rankings. The example ran until 2016; had the data run until 2014, India would have been on top. Color palettes and visualizations are all handled in an easy, drag-and-drop manner. This is the style of real-time data infographic you see all over social media.

Recap — the tool landscape at a glance:

Tool Type Standout use Position
Tableau Drag-and-drop visualization Dashboards, storylines, calculated fields Leader (with Qlik)
Power BI Microsoft BI stack Microsoft-ecosystem companies; free Desktop + paid Service Leader (with Excel)
Looker Studio Free Google tool Quick exploration on Google Sheets data Widely used
Grafana Open source DevOps and infrastructure monitoring on time series Emerging
Qlik Sense Self-service BI platform Non-technical analysts; cloud + on-premises Leader
Sisense BI platform In-memory analytics on very large datasets Gartner quadrant
Domo Cloud BI Dashboards and polished visualizations Gaining popularity
Infogram Infographics Templates, reports, social media visuals Emerging
ChartBlocks Embedded charts Interactive charts in websites Gaining popularity
Flourish Data storytelling Animated interactive stories Storytelling niche

Exam note: be able to place the main tools — Gartner leaders are Microsoft (Excel and Power BI together), Salesforce, and the Tableau–Qlik pair — and to say what each emerging tool (Looker Studio, Grafana, Sisense, Domo, Infogram, ChartBlocks, Flourish) is mainly used for.

4.14 Choosing a Visualization Tool

4.14.1 The Selection Criteria

Every tool in the market has something going for it — that is why it is in the market. The choice depends on three things: your needs, your budget, and your expertise. One will naturally choose the tool they already have expertise in. Combining all three, you pick the tool that suits you — and that is exactly how a professional selects a tool for a business case.

The hook: every tool in the market has something going for it — otherwise it would not be in the market. The reason tool comparisons never end is that the right pick is personal: it depends on your needs, your budget, and your expertise. That is the professional selection method, and it is the same three inputs for a one-person project or an enterprise BI decision.

The three selection criteria, unpacked:

  • Needs: what will you actually do? Dashboards for leadership? Deep exploration of a large dataset? Storytelling for social media? Infographics for marketing? Each need points at a different family from section 4.13 — a BI platform for enterprise analysis, Flourish for stories, Infogram for infographics.
  • Budget: where does the cost sit? Tableau has a free personal edition (Tableau Public) and paid enterprise plans; Power BI is free as Desktop but paid as Service; Looker Studio is free; Grafana is open source. The budget decides how far up that ladder you can go.
  • Expertise: one will naturally choose the tool they already have expertise in — a trained Tableau analyst stays with Tableau, an Excel shop slides into Power BI. Expertise is a legitimate criterion, not a bias: the best tool is the one you can use well.

Combining all three, you pick the tool that suits you — that is exactly how a professional selects a tool for a business case.

The tour makes one point: our view is often limited to one or two tools, but look at what exists in industry. Marketing companies and many others need jazzy, powerful visuals, and there are many players emerging in that space.

Recap: the tool choice depends on needs, budget, and expertise — in that order. The market tour's wider lesson: our view is often limited to one or two tools, but industry runs on a much wider landscape — from enterprise BI platforms to storytelling tools — and knowing the landscape keeps you from defaulting to the first tool you learned.

4.14.2 What Comes Next

The theory phase is done — you have learned the fundamentals. The next session goes deeper into the tools: desktop-based tools, online visualization tools, their libraries, and open source versus proprietary options, plus the architectures behind them. From the sixth session onward, the focus is Tableau desktop with live demos and hands-on work. Whatever form you need, the instruction is to take what you have learned here and use it — you have the fundamentals now, and the tools are the vehicle.

Where the course goes from here: this session gave the theory (taxonomy, data types, relationships, chart choice) and the landscape (the tool market). The next session goes deeper into the tools themselves — desktop-based tools, online visualization tools, their libraries, and open source versus proprietary options, plus the architectures behind them. From the sixth session onward, Tableau desktop takes the stage with live demos and hands-on work. The theory is the driver; the tools are the vehicle.

Pitfall — expertise as a cage: choosing only the tool you already know can lock you out of better options — the professor's tour exists precisely to widen that view. Learn the landscape, then let needs and budget lead; treat expertise as one input among three, not the only one.

4.15 End-of-Session Discussion

4.15.1 Plans for Quizzes

Q: Are there any plans for quizzes in this subject? Other subjects are giving us quizzes already.

A: I will check the timing and publish a plan, and I will let you know in advance — quizzes will not come as a surprise. I will publish something based on what we have learned, and share the plan with you in advance.

The answer sets a clear contract for the rest of the course: quizzes are coming, they will be based on what has been learned in class, and the plan will be published in advance. Nothing will arrive unannounced.

4.15.2 Feedback on Ambiguous Quiz Questions

A student raised a fair point about multiple-choice quizzes in general: some questions are ambiguous — both options can be correct. When both options are correct but the answer key marks only one, students lose marks even though their answer was right.

Q: In the quiz today, the second question had two correct answers. I went with the last option and it was marked wrong — the quiz said the first option was correct. But you yourself said both are correct. We should not lose marks like that.

A: You are right. There should not be this kind of ambiguity — especially in a topic like data visualization, which is not like science or a theorem with one single right answer. In the exam I will make sure there are no ambiguous questions: I will come up with responses that are quite clear, with no ambiguity. Where there is potential for multiple correct answers, students should not lose marks when they say "both are correct." I will work out how to avoid this kind of confusion.

The exchange closed with the acknowledgement that ambiguity in chart-selection questions is a real problem — the same reasoning that runs through the whole taxonomy topic: with charts, several answers can legitimately be right depending on the scenario, so questions and answers must be phrased to respect that.

Why chart questions are especially prone to ambiguity: in a theorem-based subject, one answer is provably correct. In data visualization, the chart choice depends on the situation and the audience (section 4.8) — so a multiple-choice question can genuinely have two defensible options, like histogram versus box plot for a distribution. That is why the quiz feedback matters: the question design must respect the subject's nature, and the answer key must accept legitimate alternatives.

Recap — the two commitments from this session's discussion:

  1. Quizzes will be announced in advance — the plan is published before anything is published, based on what has been learned in class.
  2. Exam questions will be unambiguous — no ambiguous multiple-choice questions; where multiple answers are legitimately correct, students should not lose marks when they say "both are correct."

Exam note: this is the guidance for the subject's assessment design — expect clear, single-interpretation questions, and expect chart-selection reasoning (section 4.12) to be the model they follow.

Exam Guidance Summary

  • Quiz plan: Quizzes will be announced and the plan shared in advance — nothing will come as a surprise. The quizzes will be based on what has been learned in class. (Exam note: expect quiz questions modeled on the chart-selection reasoning from section 4.12.)
  • Exam question quality: The exam will avoid ambiguous multiple-choice questions. Answers will be clear and unambiguous — especially important in data visualization, which does not have a single right answer like a theorem. If a question genuinely has two correct options, "both are correct" should not cost marks.
  • Chart-selection reasoning to study: the quiz logic is the model. Bar chart for comparing magnitudes across categories (line is for time series, scatter for correlation). Histogram for distributions (box plot as the alternative that shows quartiles). Time series for a single variable over frequent intervals. Heat maps work for numerical and time series data, not only categorical. Line graphs beat scatter plots for overall trends.
  • Conceptual foundations: know the four data types (categorical, numerical with discrete/continuous, ordinal, time series), the four relationship families (magnitude, trends, distribution, correlation/network), and the three complexity levels (simple, multi-variable, interactive) — these drive every chart choice.
  • Chart knowledge: for each chart in the taxonomy — bar, pie, line, area, heat map, histogram, box plot, scatter, Sankey, radial, glyph — know what it is for, its strengths, its limits, and when to pick it (the bar-versus-pie rule, the histogram-versus-box-plot rule, and the audience rule from section 4.8 are the most likely to appear).
  • Tool landscape: be able to place the main tools — the Gartner quadrant leaders are Microsoft (Excel and Power BI together), Salesforce, and Tableau–Qlik; know what the emerging tools (Looker Studio, Grafana, Sisense, Domo, Infogram, ChartBlocks, Flourish) are mainly used for.
  • Data types → charts mapping (study aid):
Data type Charts that fit
Categorical Bar, pie, heat map
Numerical Bar, line, histogram, scatter
Ordinal Bar, box plot
Time series Line, area, heat map

Key Industry Applications

  • Gartner quadrant: used across the industry to evaluate BI and visualization platforms; current leaders are Microsoft, Salesforce, and Tableau–Qlik. Real-world: companies use this quadrant to shortlist tools for their BI stack.
  • Microsoft ecosystem: Power BI Desktop (free, with Power Query for data preparation) plus Power BI Service (paid, for sharing and collaboration) — the standard stack for organizations on Microsoft. Excel remains a widely used data visualization tool, which is why Microsoft's leader position in the quadrant covers both.
  • Tableau: dashboards, storylines, and calculated fields in analytics teams; Tableau Public serves as the free personal edition; one-year free licenses available through academic analytics labs.
  • Looker Studio (Google Data Studio): free quick exploration and reporting on Google Sheets data, popular in media and small teams.
  • Grafana: open source monitoring and dashboards for DevOps and infrastructure teams, optimized for time series data.
  • Qlik: Qlik Sense self-service BI for non-technical analysts; Qlik Cloud and Qlik Compose for data integration and data warehouses; on-premises Qlik Sense for highly regulated industries.
  • Sisense: in-memory analytics on very large datasets, with APIs and SDKs for embedding dashboards into products.
  • Domo: cloud BI for dashboards and reports, gaining ground in enterprises.
  • Infogram: infographics, reports, and slides with designer templates, integrated with social media — used by marketing teams.
  • ChartBlocks: embeddable interactive charts for websites and applications.
  • Flourish: animated, data-driven stories (population and GDP rankings over the years) — the format you see in social media and news infographics.
  • Domain charts: Sankey diagrams in supply chains and flow analysis (immigration flows, tournament progressions, budget breakdowns); heat maps and correlation charts for relationship analysis; bell-curve distributions in performance appraisal systems; geospatial maps for logistics, healthcare outbreaks, and state-wise retail reviews.
  • Chart-choice skill in practice: the bar-versus-pie and line-versus-scatter rules are the same decisions financial analysts make comparing quarterly revenue, supply-chain teams make comparing warehouse volumes, and dashboard designers make for executive review — the professional difference is reading the exact magnitude correctly, not just picking a chart.

DVI Lecture 4 notes · Data Visualization: Taxonomy and Tools

Data Visualization and Interpretation· postgraduate· 2026-08-11

Sections Breakdown

14.1 Where We Are and Where We Are Going

Session roadmap: recap of storytelling and the chart taxonomy, the plan for the demos and quiz, and getting Tableau Desktop.

24.2 Data Types: The Four Building Blocks

The four data types that drive chart choice: categorical, numerical, ordinal, and time series.

34.3 Relationships in Data Visualization

Four relationship families: comparing magnitudes, trends over time, distributions, and correlations with networks.

44.4 Complexity: Simple, Multi-variable, Interactive

Three complexity levels: simple, multi-variable, and interactive, governed by the start-simple principle.

54.5 Bar Chart versus Pie Chart: A Live Comparison

A live bar-versus-pie comparison: exact magnitudes from bar length versus approximate shares from slice angles.

64.6 Line Charts, Area Charts, and Heat Maps for Trends

Line charts, area charts, and heat maps for trends, demonstrated on stock price data.

74.7 Histograms for Distributions

Histograms for distributions: bins, counts, and the histogram-versus-box-plot trade-off.

84.8 There Is No Single Correct Taxonomy

There is no single correct taxonomy: the audience decides, and fundamentals like pre-attentive attributes matter.

94.9 Geospatial Data Visualization

Geospatial data visualization: automatic mapping, standard place names, and the world indicators demo.

104.10 Radial (Polar) Charts

Radial (polar) charts: strengths, limitations, and when they work.

114.11 Glyph Charts

Glyph charts: symbolic shapes, Tableau customization, and their accessibility limits.

124.12 Chart Selection Quiz

Chart selection quiz: five questions with full reasoning on choosing the right chart.

134.13 Data Visualization Tools in the Market

The data visualization tools market: the Gartner quadrant and tours of Tableau, Power BI, Looker Studio, Grafana, Qlik, and more.

144.14 Choosing a Visualization Tool

Choosing a visualization tool: needs, budget, and expertise.

154.15 End-of-Session Discussion

End-of-session discussion: quiz plans and feedback on ambiguous questions.

16Exam Guidance Summary

Assessment commitments and study targets for the session.

17Key Industry Applications

Real-world uses of the tools and chart-choice rules covered.

Postgraduate students learning data visualization and interpretation

Exam Revision Notes

Below is the distilled, exam-ready core. Every entry comes from the full explanation above. Use this section for rapid review; return to the main notes when a point needs more context.

Where We Are and Where We Are Going

Must-know: Session roadmap: taxonomy recap, building blocks (data types, relationships, complexity), demos, quiz, then tool market tour with the Gartner quadrant; Tableau Desktop licensed free for one year and renewable.

⚠️ Top pitfall: Treating the recap as skippable — the building blocks are not in the course handout but they drive every chart choice in the demos and quiz.

Self-check: What are the three sections of a story told in data visualization?

Connects to: 4.2 Data Types: The Four Building Blocks, 4.3 Relationships in Data Visualization, 4.4 Complexity: Simple, Multi-variable, Interactive, 4.13 Data Visualization Tools in the Market

Data Types: The Four Building Blocks

Must-know: Four data types — categorical (labels, no sequence; bar/pie/heat map), numerical (discrete whole-number counts vs continuous measurements; bar/line/histogram), ordinal (ordered labels; bar/box plot), time series (time attached to every point; line/heat map).

⚠️ Top pitfall: Treating ordinal data as nominal so the axis sorts labels alphabetically and scrambles the intended scale; also forgetting to set date fields as dates so the time axis is lost.

Self-check: Why is survey response data (strongly agree ... strongly disagree) not plain categorical data?

Connects to: 4.3 Relationships in Data Visualization, 4.12 Chart Selection Quiz

Relationships in Data Visualization

Must-know: Four relationship families: comparing magnitude (bar wins for exact values; pie for proportions), trends over time (line, area), distributions (histogram, box plot, density), correlations and networks (heat map, scatter, Sankey, network diagrams).

⚠️ Top pitfall: Using a scatter plot to show a trend (scatter shows relationship between two variables, not change over time) and reading exact magnitudes from pie slices.

Self-check: Which chart family answers: how are the marks in a class spread out?

Connects to: 4.2 Data Types: The Four Building Blocks, 4.5 Bar Chart versus Pie Chart: A Live Comparison, 4.6 Line Charts, Area Charts, and Heat Maps for Trends, 4.7 Histograms for Distributions, 4.12 Chart Selection Quiz

Complexity: Simple, Multi-variable, Interactive

Must-know: Three complexity levels: simple (single message; bar/line), multi-variable (two or more variables; more interpretation), interactive (dashboards, filters, exploration). Start simple, add only if needed, support numbers with commentary.

⚠️ Top pitfall: Loading the chart with everything at once — every added variable and filter raises cognitive load and hides the message; charts without commentary do half the job.

Self-check: At which complexity level would a bar chart of monthly sales alone sit?

Connects to: 4.5 Bar Chart versus Pie Chart: A Live Comparison, 4.8 There Is No Single Correct Taxonomy

Bar Chart versus Pie Chart: A Live Comparison

Must-know: Bars encode values as length against a common baseline (exact reading); pies encode values as angles ((v/T) x 360 degrees) which support only relative comparison. Use pie for proportional contribution, bar for exact magnitudes.

⚠️ Top pitfall: Using a pie chart to communicate exact counts — with many slices even rough ranking fails; the brain cannot extract exact numbers from angles.

Self-check: A budget item is 400,000 of a 1,000,000 total. What angle does its pie slice occupy, and why is that hard to read as a number?

Connects to: 4.2 Data Types: The Four Building Blocks, 4.3 Relationships in Data Visualization, 4.12 Chart Selection Quiz

Line Charts, Area Charts, and Heat Maps for Trends

Must-know: Trade date in columns + close price as value draws a line automatically; toggle to exact date for real granularity; line for trends (safer default), area chart as shaded variant, heat map for small yearly comparisons; dual-axis views allow line + volume bars with per-chart properties.

⚠️ Top pitfall: Leaving the default year/quarter aggregation on when the message needs daily detail; area charts without a zero baseline; heat maps without a color legend.

Self-check: When would you keep the year/quarter aggregation instead of switching to exact date?

Connects to: 4.3 Relationships in Data Visualization, 4.12 Chart Selection Quiz

Histograms for Distributions

Must-know: Histogram: number intervals (bins) on X, occurrence counts on Y, bars touching; shows distribution shape; bins are auto-created but tunable. Box plot: five-number summary with quartiles; compact but hides shape. For a single parameter's distribution, the histogram is the simpler choice.

⚠️ Top pitfall: Confusing a histogram with a bar chart (categories vs number intervals); leaving bin width on auto without checking the resulting shape.

Self-check: What distinguishes a histogram from a bar chart visually?

Connects to: 4.3 Relationships in Data Visualization, 4.12 Chart Selection Quiz

There Is No Single Correct Taxonomy

Must-know: No single correct taxonomy: the audience's needs decide the chart. Fundamentals: control cluttering, understand pre-attentive attributes (size, hue, position, shape, line length), use color and fonts deliberately — these are the difference between charts that communicate and charts that confuse.

⚠️ Top pitfall: Treating the fundamentals as small: cluttered charts, decorative color, and neglected fonts are the usual reason a visualization confuses instead of communicating.

Self-check: Why can a bar chart's value be read pre-attentively while a pie slice's cannot?

Connects to: 4.5 Bar Chart versus Pie Chart: A Live Comparison, 4.4 Complexity: Simple, Multi-variable, Interactive, 4.10 Radial (Polar) Charts

Geospatial Data Visualization

Must-know: Geospatial fields carry a globe icon; the tool matches standard place names against its built-in coordinate database and draws the map automatically; encode measures on top (GDP as values, birth rate as color); data must use standard names with no abbreviations or full stops.

⚠️ Top pitfall: Using abbreviations or non-standard names (e.g. USA, U.S.A.) so the tool cannot match the place; misspelled names silently drop points with no error.

Self-check: What does the globe icon on a field signal in Tableau?

Connects to: 4.2 Data Types: The Four Building Blocks, 4.3 Relationships in Data Visualization

Radial (Polar) Charts

Must-know: Radial chart = circular axis instead of X-Y; compact and engaging for a few series; cannot read precise values; does not scale to large datasets; unfamiliar to most audiences so it needs commentary.

⚠️ Top pitfall: Using a radial chart where exact magnitudes matter, or loading it with too many spokes — the chart becomes unreadable; outer-ring values also appear larger than equal inner-ring values.

Self-check: Why can you not read exact values from a radial chart?

Connects to: 4.5 Bar Chart versus Pie Chart: A Live Comparison, 4.8 There Is No Single Correct Taxonomy

Glyph Charts

Must-know: Glyph charts encode data points as symbolic shapes; shape per series in Tableau (square, diamond, cross, star); they fit multivariate data and compact spaces; they fail on precision, scale, design ease, and accessibility — people with color blindness find them a real challenge.

⚠️ Top pitfall: Using glyph charts for exact reporting or large datasets — positions are limited so marks overlap, interpretation gets harder as data grows, and the audience must learn the chart first.

Self-check: What makes a glyph chart different from a plain scatter plot?

Connects to: 4.8 There Is No Single Correct Taxonomy, 4.10 Radial (Polar) Charts

Chart Selection Quiz

Must-know: Bar chart for magnitude comparison across categories; histogram for distributions (box plot shows quartiles but histogram is simpler); time series plot for a single variable over frequent intervals; heat maps work for numerical/time series data; line graphs beat scatter plots for overall trends.

⚠️ Top pitfall: Answering by chart familiarity instead of relationship: a scatter plot is not 'always better' — for trends the line graph is the tool; 'always' and 'only' claims in chart questions are usually false.

Self-check: Why is a bar chart preferred over a line graph for comparing sales across regions?

Connects to: 4.2 Data Types: The Four Building Blocks, 4.3 Relationships in Data Visualization, 4.5 Bar Chart versus Pie Chart: A Live Comparison, 4.6 Line Charts, Area Charts, and Heat Maps for Trends, 4.7 Histograms for Distributions

Data Visualization Tools in the Market

Must-know: Gartner leaders: Microsoft (Excel and Power BI together), Salesforce, Tableau-Qlik. Power BI Desktop is free (Power Query included); Power BI Service is paid for sharing and collaboration. Know each tool's main use: Tableau dashboards, Looker Studio free Google exploration, Grafana open source time series monitoring, Qlik self-service BI, Sisense in-memory analytics, Domo cloud BI, Infogram infographics, ChartBlocks embeddable charts, Flourish storytelling.

⚠️ Top pitfall: Reading Microsoft's leader position as Power BI only — it covers Excel and Power BI together because many companies still visualize in Excel.

Self-check: Where does the paid cost of Power BI come from?

Connects to: 4.1 Where We Are and Where We Are Going, 4.14 Choosing a Visualization Tool

Choosing a Visualization Tool

Must-know: Tool choice depends on needs, budget, and expertise; every tool in the market has something going for it, so selection is situational; the theory phase is done, tools are the vehicle, and Tableau desktop hands-on begins from the sixth session.

⚠️ Top pitfall: Letting expertise alone decide the tool — the market tour exists to widen a view that is often limited to one or two tools.

Self-check: What three criteria drive a professional tool selection?

Connects to: 4.13 Data Visualization Tools in the Market, 4.1 Where We Are and Where We Are Going

End-of-Session Discussion

Must-know: Quizzes are announced in advance with the plan published before anything is published; exam questions will be clear and unambiguous — data visualization is not a theorem subject, so where multiple answers are correct, 'both are correct' should not cost marks.

⚠️ Top pitfall: Assuming one right answer per chart question — in data visualization several answers can legitimately be right depending on scenario and audience, so questions and answer keys must respect that.

Self-check: What did the student's feedback commit the exam design to?

Connects to: 4.8 There Is No Single Correct Taxonomy, 4.12 Chart Selection Quiz

Exam Guidance Summary

Must-know: Chart-selection reasoning is the quiz model: bar for magnitude comparison, histogram for distributions, time series for a single variable over frequent intervals, heat maps work for numerical data, line graphs beat scatter plots for overall trends; Gartner leaders are Microsoft (Excel + Power BI), Salesforce, Tableau-Qlik.

⚠️ Top pitfall: Expecting every chart question to have exactly one objectively correct answer — chart choice is situational, so exam questions will be phrased to avoid ambiguity.

Self-check: What are the four relationship families that drive chart choice?

Connects to: 4.2 Data Types: The Four Building Blocks, 4.3 Relationships in Data Visualization, 4.12 Chart Selection Quiz, 4.13 Data Visualization Tools in the Market, 4.15 End-of-Session Discussion

Key Industry Applications

Must-know: Each tool's industry niche (Gartner for BI stack shortlisting, Grafana for DevOps monitoring, Flourish for media stories, Sankey for supply chains, geospatial maps for logistics and healthcare) and that the chart-choice rules apply in everyday analyst decisions.

⚠️ Top pitfall: Treating chart choice as an academic exercise — in industry the same bar-versus-pie and line-versus-scatter decisions happen daily in financial, supply-chain, and dashboard work.

Self-check: Which tool is optimized for time series monitoring in DevOps?

Connects to: 4.3 Relationships in Data Visualization, 4.9 Geospatial Data Visualization, 4.13 Data Visualization Tools in the Market

Was this lecture useful?

Loading comments…
🤖

BitsNotes AI Assistant

Subject Notes Assistant

Configure AI Chat

Choose how to access the chatbot
Have your own API key?

Switch to "Bring Your Own Key" tab above for unlimited access with any OpenAI-compatible provider.

🔑 Enter API key above to fetch live models from provider, or enter model name manually.
OpenAI-Compatible API Support

Choose any provider preset (Gemini, DeepSeek, Kimi, GLM, MiniMax, Qwen, OpenAI, Groq, Ollama, etc.) or enter a custom endpoint URL.

Security & Privacy First

Your API key is sent directly from your browser to your specified provider. BitsNotes servers never store or see your key.