MestnyiGeroi
Giga Poster
Waiting in lines is a huge part of any coaster enthusiast's experience, and learning to manage (or at least second-guess) the patterns of queues is an absolute must. We study the calendar well in picking a day we think will limit the crowds, and some of you use apps for certain parks to alert you to current wait times. And of course there are those evil fastpasses ...
However, in general I find there is a strange dearth of fixed information about queue times, and I've even found that some enthusiasts don't want to talk about it for some strange reason.
So what's my question? Does there exist a database out there that records the average wait times per park and/or per ride? I have not been able to find it, and I think that parks suppress this information (I'm not getting conspiratorial; I just think it's something they don't like to advertise). But even if the parks don't do it, what is to stop enthusiasts from building a database, with people logging their wait times in order to get at averages?
I think it would be interesting in general to know, for example, which park or ride is the king of the wait. But I also think it would be very useful for people to know before first-time visits. It would quickly tell people in advance how to manage their time, and, most crucially, how many hours or DAYS they will need to reasonably cover everything at a park.
(Forum newbie disclaimer: I'm sure lines have been discussed here before in some way; please excuse me if my question is re-inventing the wheel.)
However, in general I find there is a strange dearth of fixed information about queue times, and I've even found that some enthusiasts don't want to talk about it for some strange reason.
So what's my question? Does there exist a database out there that records the average wait times per park and/or per ride? I have not been able to find it, and I think that parks suppress this information (I'm not getting conspiratorial; I just think it's something they don't like to advertise). But even if the parks don't do it, what is to stop enthusiasts from building a database, with people logging their wait times in order to get at averages?
I think it would be interesting in general to know, for example, which park or ride is the king of the wait. But I also think it would be very useful for people to know before first-time visits. It would quickly tell people in advance how to manage their time, and, most crucially, how many hours or DAYS they will need to reasonably cover everything at a park.
(Forum newbie disclaimer: I'm sure lines have been discussed here before in some way; please excuse me if my question is re-inventing the wheel.)