Course Description
CTS4457 is the data visualisation course. The Statewide Course Numbering System titles it Data Visualization and defines it as a course in which "students will develop skills to efficiently and effectively display data, using a variety of tools that can be used to prepare and present the data in visually compelling manners. Data visualization tools have wide applicability in a wide variety of settings and environments in documentation and presentation." There is no statewide prerequisite.
Three Florida public institutions carry it, all at 3 credits:
| Institution | Its title | Credits |
|---|
| Santa Fe College | Data Visualization and Communication | 3 |
| St. Johns River State College | Data Visualization and Communication | 3 |
| University of West Florida | Data Visualization | 3 |
⚠ Two state colleges use an identical title including "and Communication", which is a good sign — matching titles at two institutions usually indicate a deliberately articulated course rather than independent coincidence. And "Communication" is the better title, because it names what the subject is actually for.
The intellectual content of data visualisation is easy to underestimate. Producing a chart is trivial; producing one that lets a reader see what is true, quickly and without being misled, is not. ⚠ The discipline rests on perceptual research — how accurately people judge position, length, angle, area and colour — and those findings are why some chart types are better than others for a given comparison. A course that teaches only tools has taught the easy half.
Learning Outcomes
Required Outcomes
- Identify the audience and the question a visualisation must answer before choosing any chart.
- Distinguish data types — categorical, ordinal, quantitative, temporal, geographic — and select encodings appropriate to each.
- Apply the perceptual hierarchy: position is judged more accurately than length, length than angle, angle than area, area than colour saturation — and choose encodings accordingly.
- Select an appropriate chart type for a stated comparison, and justify the choice.
- Use colour deliberately — sequential, diverging and categorical palettes — and apply colour-blind-safe choices.
- Design for accessibility: contrast, text alternatives, and not relying on colour alone to carry meaning.
- Prepare and shape data for visualisation, including reshaping, aggregation and handling missing values.
- Build charts in an industry tool and in a programming environment.
- Design an interactive dashboard with a clear hierarchy, coherent filtering and a defensible layout.
- ⚠ Identify misleading visualisations — truncated axes, dual axes, inappropriate area scaling, cherry-picked ranges — and explain precisely how each misleads.
- Annotate and title a chart so its message is explicit rather than left to the reader.
- Present a visualisation to an audience and defend its design decisions.
- Critique a visualisation constructively against stated principles.
Optional Outcomes
- Build geographic visualisations and choropleth maps, including the normalisation traps they carry.
- Build network and hierarchical visualisations.
- Produce narrative or scrollytelling data stories.
- Visualise uncertainty — error bars, intervals, distributions.
- Build custom visualisations with D3 or a comparable library.
- Address performance with large data sets, including sampling and aggregation.
- Apply an organisation's design system or branding to a dashboard.
Major Topics
Required Topics
- Purpose first — audience, question, and the difference between exploratory and explanatory visualisation.
- Data types and encodings — the marks and channels available, and matching them to data.
- Perception — the accuracy ranking of visual channels, pre-attentive attributes, Gestalt grouping, and why pie charts are weak for comparison.
- Chart selection — comparison, distribution, relationship, composition and change over time; the right default for each.
- Colour — palette types, colour-blind-safe choices, and colour as a carrier of meaning rather than decoration.
- Design principles — data-ink, clutter, small multiples, consistent scales, direct labelling.
- Data preparation — cleaning, reshaping, aggregating; ⚠ the part that takes most of the time.
- Tools — an industry platform (Tableau or Power BI) and a programming approach (Python or R).
- Dashboards — layout, hierarchy, interactivity, filtering, and avoiding the dashboard that shows everything and says nothing.
- Deception and ethics — how charts mislead, whether by intent or carelessness, and the practitioner's responsibility.
- Accessibility — contrast, alternatives, and inclusive design.
- Critique and presentation — giving and receiving criticism; presenting to a non-technical audience.
Optional Topics
- Geographic visualisation and mapping.
- Network and hierarchy visualisation.
- Narrative and data storytelling.
- Visualising uncertainty.
- Custom visualisation with D3.
- Large-data performance strategies.
- Design systems and branding.
Resources & Tools
- ⚠ Storytelling with Data by Cole Nussbaumer Knaflic is the most widely assigned text and is the best single book for the communication half of the subject.
- The Visual Display of Quantitative Information by Edward Tufte — the field's founding work, opinionated and worth arguing with.
- Fundamentals of Data Visualization by Claus Wilke is free online, is rigorous about perception, and is the best reference for "which chart and why".
- How Charts Lie by Alberto Cairo — ⚠ Cairo is at the University of Miami, making this a Florida-authored standard text, and it is the best treatment of the deception material.
- Tools: Tableau and Power BI both have free student licensing and are what employers ask for; Python (matplotlib, seaborn, plotly, Altair) and R (ggplot2) are free; D3.js for custom web work; Observable for sharing.
- Free palette and accessibility help: ColorBrewer for principled palettes, and any colour-blindness simulator — ⚠ roughly one man in twelve has a colour vision deficiency, which is a design constraint rather than an edge case.
- ⚠ Use real data, and Florida's is good: FDOT traffic counts, Department of Health surveillance data, Department of Education enrolment and outcomes, and the state's hurricane and coastal data sets. Real data is messy and has an audience who cares, which is what makes a project worth doing.
Career Pathways
- Data Analyst and Business Intelligence Analyst — ⚠ the direct destinations, and visualisation is frequently the skill that gets the interview, because it is the part of the work a hiring manager can evaluate at a glance.
- Data Scientist (SOC 15-2051) — communicating a result is half the job and the half most often done badly.
- Market Research Analyst (SOC 13-1161).
- Web and Digital Interface Designer (SOC 15-1255) for interactive and custom work.
- Journalist (SOC 27-3023) — data journalism is a real and growing speciality.
- Florida employers: healthcare systems, which report continuously to regulators and boards; Publix and the large retail operations; financial services in South Florida; the theme park and hospitality groups; state and county agencies, which publish public-facing dashboards; and the water management districts and environmental agencies, whose monitoring data is inherently visual.
- ⚠ A portfolio matters more than the transcript here, and this is one of the few technical courses whose coursework is directly portfolio material. Publish your projects — Tableau Public and Observable are free and are where hiring managers look.
Special Information
Offering Notes — offerings and hours, school by school
| Institution | Its title | Credits | Contact hours |
|---|
| Santa Fe College | Data Visualization and Communication | 3 | not published |
| St. Johns River State College | Data Visualization and Communication | 3 | not published |
| University of West Florida | Data Visualization | 3 | not published |
Two Florida College System institutions and one State University System institution, so statewide numbering guarantees transfer between them. ✅ All three carry it at 3 credits, and the only title difference is the addition of "and Communication".
⚠ Santa Fe and St. Johns River use an identical title, which usually indicates an articulated course rather than coincidence — and ⚠ the state-college-to-university path is exactly what this number's transfer guarantee is for. It is a 4000-level course carried at state colleges offering baccalaureate programmes, so confirm how it counts if you are moving into a different degree.
⚠ The 45 contact hours at the top of this guide are derived — the Florida convention for a 3-credit lecture course. No institution publishes an hour figure. ⚠ In practice much of the work is project production, so expect the real time commitment to exceed the scheduled hours.
⚠ "And Communication" is the more accurate title
The statewide definition ends with the phrase "in documentation and presentation" — it is about conveying findings, not about generating charts. The two state colleges' title says so explicitly.
⚠ Why it matters: a course weighted toward tools produces students who can build a dashboard and cannot say what it shows. A course weighted toward communication produces students who choose fewer charts and defend them. Employers value the second and interview for it — the standard interview task in this field is "here is a dataset, tell us something useful", which is a communication problem.
⚠⚠ The deception material is the ethical core of this course
Every technique that makes a chart clearer can make it mislead. ⚠ A truncated axis, a dual axis, an area scaled by radius rather than area, a cherry-picked date range — each is a design decision that changes what a reader concludes, and each appears routinely in published work.
Two points worth carrying out of the course. First, most misleading charts are not dishonest — they are produced by a default setting nobody questioned, which makes knowing the defaults a professional responsibility. Second, you will at some point be asked to produce a chart that puts a result in a better light. Knowing precisely where the line sits between emphasis and deception is what this part of the course is for, and it is the part that will matter to your reputation.
No prerequisite — and what that implies
⚠ The statewide record lists no prerequisite, which is unusual for a 4000-level course and tells you something: this course is reachable by students outside computing — business, health, communication, the sciences — and that is deliberate, since visualisation is needed everywhere data is.
⚠ It also means the room will contain a wide range of technical ability, and the course cannot assume programming. If you are a computing student, expect the tool work to feel gentle and the design and critique work to be where the difficulty is — and that is the part worth your attention, because it is the part that does not come naturally to engineers.
Position in the curriculum and workload
A 4000-level course pairing naturally with data warehousing and big data analytics; together they make a coherent analytics concentration.
Budget eight to ten hours a week. ⚠ Data preparation takes most of the time on every project, which is a surprise to students who expected a design course. Iteration takes the rest — a good visualisation is usually the fifth attempt, and students who submit the first are visibly submitting the first.
AI Integration
Data visualisation is a field where these tools genuinely help and where the thing they cannot do is the thing being assessed.
Genuinely useful: writing plotting code in matplotlib, ggplot2 or plotly, which is fiddly, poorly memorable and a legitimate use; explaining an unfamiliar tool's syntax; suggesting chart types for a described comparison as a starting point; generating alt text for accessibility, which is real and frequently skipped work; drafting the written narrative around a visualisation; and critiquing a chart you have made against stated principles, which is a surprisingly effective use.
⚠⚠ Where it fails:
- Generated charts default to the conventional rather than the appropriate. Asked to visualise a comparison, a model reaches for a bar chart or — worse — a pie chart, because those dominate its training data. ⚠ The perceptual reasoning this course teaches is precisely what it does not apply.
- No knowledge of the audience. The first question in this discipline is who is reading and what they need to decide, and a model has no access to either.
- It will not tell you the chart is misleading. Ask for a chart that makes a small difference look large and you will get one, competently. ⚠ The judgement about whether to produce it is yours alone.
- Fabricated data and statistics when asked for an example — which has no place in a visualisation, where the data is the claim.
⚠ The reflexive point worth noticing: generative tools are now built into Tableau and Power BI and will produce a dashboard from a prompt. That raises the value of the design and critique skills rather than lowering it — a generated dashboard still needs someone who can look at it and say that the axis is truncated, the palette fails for a colour-blind reader, and the chart answers a question nobody asked. That person is the one worth hiring, and this course is where they are made.
Academic integrity: read your syllabus. ⚠ Projects in this course are normally presented and critiqued, which exposes work a student cannot explain — and where you use AI assistance for code, the design decisions and the analysis must still be yours to defend.