Walt Disney World Trip/Time Optimizer

Project 1 process book · Maria Brooks and Thomas Dong · CSE 4507

1. Background and Motivation

Being from Florida, amusement parks have always been in my backyard, and I grew up having season passes to Universal Studios and Busch Gardens. I noticed that even when I visited during the “off season,” it could still be shockingly busy. This motivated us to create a Walt Disney World Trip/Time Optimizer that uses historical data instead of anecdotal advice such as “visit in September” or “avoid holidays and weekends.”

Our goal is to build a tool that allows users to figure out when the best time for them to go to Disney is based on historic wait times, crowd levels, and their own availability. By turning years of historical data into an interactive planning tool, we hope to improve the trip-planning process and demonstrate the practical value of data visualization.

2. Project Objectives

Guiding Question: How can historical Walt Disney World wait-time data be used to determine the optimal time and strategy for visiting Walt Disney World while minimizing wait times and maximizing ride experiences?

Our visualization is intended to answer:

3. Project Benefits

4. Data

Our data comes from the Walt Disney World Wait Times and Crowd Calendar dataset on Kaggle. It contains approximately 11 years of historical Walt Disney World data, including ride wait times, park crowd levels, park operating hours, date-based information, attraction information, and park identifiers for all four Walt Disney World parks.

The dataset documentation states that it was scraped from Queue-Times.com. The original CSV files used in this project are preserved in the repository’s archive/ folder. In other words, “raw files” refers to the unmodified source CSV files before our cleaning and metric-generation steps; it does not refer to a second data source.

5. Dataset Limitations

6. Data Cleaning

The reproducible cleaning and metric-generation code is in scripts/clean_data.py.

7. Handling Dataset Limitations

8. Derived Metrics

9. Exploratory Data Analysis

Before building the final visualizations, we looked at the cleaned data and derived summaries to find patterns in crowd levels. This helped us decide which comparisons and recommendations would be most useful to visitors.

These findings come from derived_monthly_park_summary.csv, derived_weekday_park_summary.csv, derived_season_park_summary.csv, and derived_event_impact.csv. We use relative crowd values because they make comparisons across years more meaningful. The results also helped us focus the prototype on park selection, monthly patterns, and lower-crowd recommendations. The weekday, season, and event comparisons are areas we can expand in a later version of the tool.

10. Visualization Design

The original proposal identified the following visualization ideas and features:

Interactive crowd calendar heatmap Park comparison dashboard Ride demand explorer Personalized visit recommendations Crowd forecasting Predicted total wait time Day itinerary generator

Original designs from the project proposal

Original project proposal design 1 Original project proposal design 2 Original project proposal design 3 Original project proposal design 4 Original project proposal design 5

The original sketches were created by Thomas and are above.

11. Implementation and Interaction

The prototype uses park and month selections to update the crowd summary, monthly chart, attraction rankings, and recommendation table. The map section uses a shared date picker to show historical crowd levels for all four parks. Users can also select a ride marker or ride button to view its historical posted-wait profile.

Project dashboard showing park and month controls, summary cards, and the monthly crowd chart
The main dashboard gives an overview of the selected park and its historical crowd patterns.
Magic Kingdom dashboard filtered to September with recommendation results
After selecting Magic Kingdom and September, the summary cards and recommendations update for that selection.
Interactive park maps showing historical crowd information
The park maps show historical crowd levels and the locations of tracked attractions.
Park map with a selected ride and its historical ride profile
Selecting a ride focuses its location and displays its historical posted wait summary.

12. Project 1 Update

For Project 1, our data acquisition and data structures are complete, and we have a working visualization prototype. The current prototype includes park and month filters, a monthly crowd chart, top attraction posted-wait rankings, and ranked recommendation options.

The prototype also includes four maps for Magic Kingdom, EPCOT, Hollywood Studios, and Animal Kingdom. A shared historical date picker updates the park-wide relative crowd colors across all four maps. Selecting any of the 24 ride markers or ride buttons focuses its location and displays a profile with historical average posted wait, average annual maximum posted wait, and years observed.

The cleaned dataset contains 12,651 park-day records across all four parks, covering 2015–2019 and 2022–2025. The map colors represent historical daily crowd levels relative to each park’s annual average. Ride profiles summarize multiple years of data and do not show live waits or waits for the selected date. The next iteration will add the full crowd-calendar heatmap and more personalized weighting for a visitor’s priorities.

Open the working visualization prototype →

13. Must-Have and Optional Features

Must-Have Features

Optional Features

14. Evaluation and Findings

Our analysis shows that lower-crowd visits are not the same for every park. September had the lowest average relative crowd for all four parks in our data, while March had the highest. Fall was the lowest-crowd season for Animal Kingdom, Hollywood Studios, and Magic Kingdom, while summer was lowest for EPCOT. These results support using park and month selections instead of giving visitors one recommendation for all four parks.

The prototype helps users compare monthly crowd patterns, review ranked recommendations, see top attractions by posted wait, and explore historical crowd levels on the park maps. The relative crowd scale also makes the results easier to compare across years than the original crowd percentage. Together, these views answer our main question about when visitors may find lower-crowd conditions.

There are still limits to what the tool can predict. The data contains posted waits rather than actual waits, attraction coverage changes over time, and 2020–2021 and partial 2026 data were excluded. Event labels are also incomplete, so event comparisons should be treated as patterns rather than predictions. The current recommendations use historical crowd and stability scores, not a guarantee of future conditions.

In a future version, we would add the full crowd-calendar heatmap, weekday and season filters, more direct park comparisons, and personalized recommendations based on a visitor's priorities. These additions would make the tool more useful for planning a specific trip while keeping the current historical results as its foundation.

15. AI-Use Disclosure

AI tools were used to assist with data-cleaning code, validation checks, derived statistics, and styling. We selected the cleaning rules, reviewed the outputs, interpreted the limitations, and we remain responsible for the final analysis and conclusions.