Flows, Time & Interactivity (2D + Time) - CS-GY 6313 - Fall 2026
2026-10-30
What happens when we apply static techniques to massive urban datasets?
This is one week of NYC taxi trips (about 3.5 million) drawn as points on a map.
What can you learn from this?
Nothing. It’s a “yellow blob.”

Learn to visualize urban dynamics—movement and time—using interactive, linked views
We’ll learn how to move from this “yellow blob” to meaningful insights about urban mobility patterns.
How do we make better decisions about urban development?
To understand a city, we must explore how these interact over space and time.
The Classic Framework for Movement Analysis
The Urban Challenge:
Understanding millions of these paths, all interacting simultaneously


Every new question is another trip around the loop.
❌ Cognitive overload - Generates overwhelming numbers of plots/tables
❌ Batch-oriented - No exploration, just predetermined queries
❌ Distances experts from data - Requires intermediary (data scientist)
❌ Cannot scale - Modern data volumes overwhelm traditional tools
❌ Result: The “yellow blob” problem
Even simple questions require generating dozens of individual plots, each manually programmed
This is tedious, slow, and limiting
❌ Tools can’t handle 170M trips
❌ Requires programming/database expertise
❌ Time-consuming and frustrating
❌ Distances experts from the data
❌ Hard to explore, compare, or follow up on patterns
Role: Presentation
Limitation: Cannot handle hundreds of millions of data points
Role: Exploration
Power: Query and filter to reveal patterns
“Overview first, Zoom and Filter, then Details-on-Demand”
— Ben Shneiderman (1996)

Start with the big picture (even if it’s a “yellow blob”)

Focus on items of interest

Get specifics when needed
Illustrations from a catalogue of driver-distraction measures (not TaxiVis); Shneiderman, B. (1996). The Eyes Have It. IEEE Symposium on Visual Languages.
Research shows that even a half-second delay dramatically impacts analysis quality.
Challenge: How do we make sense of this data?
One dataset shows weekly rhythm, holiday dips, storms and street events.
Daily taxi trips in 2011 and 2012 (top) and map snapshots of pickups and dropoffs (bottom)
Let users query data through direct manipulation of visualizations
Where?
When?
What?
Instead of writing SELECT * FROM trips WHERE..., you draw on a map

Ferreira, N., Poco, J., Vo, H. T., Freire, J., & Silva, C. T. (2013). Visual exploration of big spatio-temporal urban data: A study of New York City taxi trips. IEEE TVCG. doi:10.1109/TVCG.2013.226
“How do trips from Manhattan to JFK and LaGuardia differ on a Sunday vs. a Monday?”
Two linked TaxiVis windows: the same Manhattan-to-airport query for Sundays (left) and Mondays (right)

All three fundamental spatio-temporal query types:
“What taxis were in Midtown at rush hour?”
“Where were high-fare trips on New Year’s Eve?”
“When do trips to airports peak?”
We need multiple visualization strategies

Result: a readable sample at every zoom level



When to use: heat maps for overview and patterns, LOD for individual trips, neighborhood maps for comparing defined regions

Actions in one view are reflected in all other views
This creates a “dialogue” where you can ask questions by interacting with any visualization component, and all views update to answer your question.
“What is the temporal pattern for trips from JFK Airport?”


Draw regions on the map and the chart answers: one line per query, matched by color.
The linking works in both directions
This bidirectional dialogue enables exploratory analysis that would be impossible with static visualizations.
“Where are the trips in this hour of the day?”


Select recurring time periods: a pattern, not a single time slice.

Shaded here: September of 2011 and 2012, Tuesdays and Fridays, 9-11 AM. Other examples: all Mondays 8-10 AM, every Saturday night, weekday rush hours only.
This reveals periodic behavior: the heartbeat of the city.
Asking about movement between specific locations
Complex, requires knowing SQL and field names
Draw an arrow
Simple, visual, intuitive
This is what we mean by “visual query”—you draw your question, the system answers. You have already seen it: the blue and red arrows in the airport query.
The visualization is the interface.


Harlem (blue) sits more than an order of magnitude below Midtown, in pickups and in dropoffs.


Blue = Harlem. Tips per trip run higher but noisily (few trips); fare per mile is lower.

More pickups at LGA than JFK on most days
Train stations >> airports for pickups
Weekday pattern: train-station pickups roughly constant Mon-Thu, falling Friday to a low on Saturday
Rush hour problem: airport trips take much longer around 3-5 PM; fare per mile is higher within Manhattan
Maps for each Monday (a) and one line per Monday (b): two lines stand apart.
Nine May Mondays: maps (a) and trips per time (b)

Why? Lower Manhattan had a multi-day power outage. You can see it on the map.

Other urban data:
Same challenges: Scale, complexity, spatio-temporal nature
Cities are vertical, not just horizontal
We’ll extend these ideas to 3D urban visualization and the Urbane framework
Same principles apply: interactive, visual, scalable
The Problem:
The Solution:
The Result:
If you had access to TaxiVis, what would you explore?
Think about:
Discussion:
npm install @urban-toolkit/autkNext week: 3D & Immersive Urban Visualization
