The dataset tracks daily ticket pricing, ticket availability, and tickets sold for every future booking date by individual park from cedarfair.com. We are only track daily pass ticket sales. This dataset provides differentiated insights for three main reasons:
Collection Start Schedule | Tolerance | Earliest Collection Date | Source |
---|---|---|---|
30 1,2,3,4,20 * * * | 12 (all parks are not always open) | 2023-05-26 | cedarfair.com |
Column Name | Description | Type | Mode |
---|---|---|---|
park | Name of the park | string | REQUIRED |
inventoryDate | Booking date on calendar | Date | REQUIRED |
capacity | Capacity of the park | number | REQUIRED |
ticketsAvailable | Tickets available at the park on the given date | number | REQUIRED |
ticketsSold | Tickets sold at the park; capacity - ticketsAvailable | number | REQUIRED |
eventID | ID for the ticket event | string | REQUIRED |
ticketID | ID for the ticket | string | REQUIRED |
ticketName | Name of the ticket | string | REQUIRED |
priceID | ID for the price | string | REQUIRED |
price | Price of the ticket | number | REQUIRED |
tax | Tax of the ticket | number | REQUIRED |
dateCollected | The date that the data was snapshotted. This is not necessarily the date in which the data was collected, i.e. this could be from archive. | timestamp | REQUIRED |
dateRepresented | The date that the data in this row represents. This is not necessarily the date the data was collected. | timestamp | REQUIRED |
attemptID | The attemptID of the task that produced this row | string | REQUIRED |
invocationID | Also known as run ID. The invocationID is associated with a write to BQ. This corresponds to the id of a successful run_feed message | string | REQUIRED |
taskID | The unique identifier of the task that produced this row. Can be from a chain or write task. | string | REQUIRED |
We are collecting the data multiple times a day towards the end of the day to get as close to the number of tickets sold as possible.
The feed fails on certain dates due to changes in the website. If using the data for backtesting, you can backfill the missing dates through various methodologies. One methodology is to use the last available tickets sold number and incrementing it using increases in tickets sold from surrounding dates that are not impacted from missing data. Another methodology is to run a week over week calculation and applying the WoW % change from surrounding dates.
There are many different ticket names. To standardize comparisons, we recommend using the “2023 SINGLE DAY ADMISSION” tickets.
Not all parks are open on all days; in fact several parks are fully closed during non-peak months.