josh/SixFlagsSuperCalendar
1
0
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects Releases Wiki Activity

Switch from Queue Times to Six Flags API directly #18

New Issue
Open
opened 2026-04-05 17:49:24 -04:00 by josh · 5 comments
josh commented 2026-04-05 17:49:24 -04:00
Owner
Copy Link
Copy Source

IT'S HUNTING SEASON BABY

https://d18car1k0ff81h.cloudfront.net/wait-times/park/906

IT'S HUNTING SEASON BABY https://d18car1k0ff81h.cloudfront.net/wait-times/park/906
josh commented 2026-04-05 17:50:57 -04:00
Author
Owner
Copy Link
Copy Source

Returns
isFastLane
regularWaitTime
fastLaneWaitTime

Returns isFastLane regularWaitTime fastLaneWaitTime
josh commented 2026-04-05 17:54:09 -04:00
Author
Owner
Copy Link
Copy Source

If a ride is closed, then it will be entirely missing from this output. But we can cross reference / utilize the output from the operating-hours endpoint for the park that day.

If a ride is closed, then it will be entirely missing from this output. But we can cross reference / utilize the output from the operating-hours endpoint for the park that day.
josh commented 2026-04-05 18:02:50 -04:00
Author
Owner
Copy Link
Copy Source

With this we can add a fast lane toggle to instead show those wait times instead, and when the toggle is on we should make it so just fast lane rides are visible. Similar to coaster mode.

With this we can add a fast lane toggle to instead show those wait times instead, and when the toggle is on we should make it so just fast lane rides are visible. Similar to coaster mode.
josh commented 2026-05-31 11:52:06 -04:00
Author
Owner
Copy Link
Copy Source

Closed rides are not necessarily kept from the output. Perhaps rides that start the day closed, and we will cross that bridge when we get there, but I noticed something important. There is a field createdDateTime that is attached to a ride's regularWaittime and fastlaneWaittime

I have noticed that when the ride is open, the regular wait time has the createdDateTime that contains the last time it was updated
Rides that are marked as closed on Queue Times appear to not have this field set for regular wait time on the Six Flags API side.

For Fast Lane's this becomes a little bit more complicated. Most parks are not very popular and do not regularly update their Fast Lane waiting time (because there is not really a reason to). Though for parks that do set it above the 0 minutes, you will see the dateTime field filled for the fastLaneWaitTime

If it's 0 or a walk on, and marked without the field that does not necessarily mean that the Fast Lane is closed. Just appears to be unset by the park ergo marking it as a Walk On

Example API responses
https://d18car1k0ff81h.cloudfront.net/wait-times/park/1

Gemini (marked closed by Queue Times at the time)

{"id":199,"name":"Gemini","isFastLane":true,"regularWaittime":{"createdDateTime":"","waitTime":0},"fastlaneWaittime":{"createdDateTime":"","waitTime":0},"fimsId":"RIDE-001-00199"}

Maverick (marked open at 60 minutes wait by QT)

{"id":183,"name":"Maverick","isFastLane":true,"regularWaittime":{"createdDateTime":"May 31, 2026 11:34:37","waitTime":60},"fastlaneWaittime":{"createdDateTime":"May 31, 2026 11:34:30","waitTime":10},"fimsId":"RIDE-001-00183"}
Closed rides are not necessarily kept from the output. Perhaps rides that start the day closed, and we will cross that bridge when we get there, but I noticed something important. There is a field `createdDateTime` that is attached to a ride's `regularWaittime` and `fastlaneWaittime` I have noticed that when the ride is open, the regular wait time has the createdDateTime that contains the last time it was updated Rides that are marked as closed on Queue Times appear to not have this field set for regular wait time on the Six Flags API side. For Fast Lane's this becomes a little bit more complicated. Most parks are not very popular and do not regularly update their Fast Lane waiting time (because there is not really a reason to). Though for parks that do set it above the 0 minutes, you will see the dateTime field filled for the fastLaneWaitTime If it's 0 or a walk on, and marked without the field that does not necessarily mean that the Fast Lane is closed. Just appears to be unset by the park ergo marking it as a Walk On Example API responses https://d18car1k0ff81h.cloudfront.net/wait-times/park/1 Gemini (marked closed by Queue Times at the time) ```json {"id":199,"name":"Gemini","isFastLane":true,"regularWaittime":{"createdDateTime":"","waitTime":0},"fastlaneWaittime":{"createdDateTime":"","waitTime":0},"fimsId":"RIDE-001-00199"} ``` Maverick (marked open at 60 minutes wait by QT) ```json {"id":183,"name":"Maverick","isFastLane":true,"regularWaittime":{"createdDateTime":"May 31, 2026 11:34:37","waitTime":60},"fastlaneWaittime":{"createdDateTime":"May 31, 2026 11:34:30","waitTime":10},"fimsId":"RIDE-001-00183"} ```
josh commented 2026-05-31 12:13:11 -04:00
Author
Owner
Copy Link
Copy Source

image.png

super tornado has hit the United States

![image.png](/attachments/4f001045-caf2-4674-bb7f-5568c7d82858) super tornado has hit the United States
image.png
165 KiB
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
josh (Josh Wright)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: josh/SixFlagsSuperCalendar#18
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?