Rock-n-RollerCoaster average posted wait times by day. Each graph is a year, x-axis is the day of the year.
Things you can see:
Touringplans & @lentesta published historical wait-time data for select rides. The data is in .csv format and includes posted wait times and actual measured wait times. The rides they have data on are:
More graphs:
For Soarin, you can see waits down pretty dramatically in 2017/8. When did the 3rd bay open? The straight magenta section is my holding the data when the ride was closed. That was a design decision in the program. I could just as easily zero it out, but for shorter down-times, it makes the data noisier.
My first graphs were pretty noisy day-to-day, and it became hard to see what was going on. I played with number of days to average, and settled on 7. You see some variation for specific weekend days, but you definitely see long weekends in there.
To do’s: Thicker lines & bigger fonts. Make a subroutine program so that I can run all of the files at once in a batch. Fix the program to accommodate new rides. Paramaterize the averaging over # of days function.
Has anyone else looked at this data? What else would you want to see done with it? This was my entry into Python programming, something I have had on my to-do list for 4+ years. My programming skills are weak as is my knowledge of Python syntax. With fun datasets like these, I am a lot more motivated to play with it.
Things you can see:
- Wait times for much of 2018 were high, especially early in the year
- Early in the year has gotten longer lines than the summer
- You can see that August has been slow for a while, with little change
- September and October have gotten longer waits.
- It's easy to spot President's day weekend and spring break times, as well as Thanksgiving.
Touringplans & @lentesta published historical wait-time data for select rides. The data is in .csv format and includes posted wait times and actual measured wait times. The rides they have data on are:
- Alien Swirling Saucers (Disney's Hollywood Studios )
- Avatar Flight of Passage (Disney's Animal Kingdom)
- DINOSAUR (Disney's Animal Kingdom)
- Expedition Everest (Disney's Animal Kingdom)
- Kilimanjaro Safaris (Disney's Animal Kingdom)
- Na'vi River Journey (Disney's Animal Kingdom)
- Pirates of the Caribbean (Magic Kingdom)
- Rock 'n' Roller Coaster (Disney's Hollywood Studios)
- Seven Dwarfs Mine Train (Magic Kingdom)
- Slinky Dog Dash (Disney's Hollywood Studios)
- Soarin' (Epcot)
- Spaceship Earth (Epcot)
- Splash Mountain (Magic Kingdom)
- Toy Story Mania! (Disney's Hollywood Studios)
More graphs:
For Soarin, you can see waits down pretty dramatically in 2017/8. When did the 3rd bay open? The straight magenta section is my holding the data when the ride was closed. That was a design decision in the program. I could just as easily zero it out, but for shorter down-times, it makes the data noisier.
My first graphs were pretty noisy day-to-day, and it became hard to see what was going on. I played with number of days to average, and settled on 7. You see some variation for specific weekend days, but you definitely see long weekends in there.
To do’s: Thicker lines & bigger fonts. Make a subroutine program so that I can run all of the files at once in a batch. Fix the program to accommodate new rides. Paramaterize the averaging over # of days function.
Has anyone else looked at this data? What else would you want to see done with it? This was my entry into Python programming, something I have had on my to-do list for 4+ years. My programming skills are weak as is my knowledge of Python syntax. With fun datasets like these, I am a lot more motivated to play with it.