We generally do not recommend comparing counts season to season in Studio. Each seasonal model is built as a high-fidelity snapshot of how people move in a region at a given point in time, rather than as a comparison tool for measuring change between seasons. Differences you see between two seasons may reflect changes in our modeling and data rather than real-world change.

Each season incorporates the most current and accurate data and validation available at the time it is built. See our Release Notes in the Help Center for the latest updates to our models and products.

As our input data, ground truth sources, and methodology evolve, a newer season benefits from refinements that an older season was never reprocessed to include. Seasonal data is best used for existing conditions analysis, a high-fidelity picture of how people move in a region at a given point in time, not as a comparison tool for measuring change over time.

There may be some directional insights to be gained by looking at specific network links or other granular data, where a large, consistent shift is unlikely to be an artifact of model changes alone. Even then, many factors influence how the data shifts year over year and season to season, including underlying population and travel behavior, seasonal patterns, and the modeling changes described above. Treat any cross-season read as directional context, not a precise measurement of change.

For comparison over time, please use Replica's Daily data sets, which can be accessed via Replica Labs. While less comprehensive and detailed than our seasonal models, Replica's daily data applies a consistent methodology across the full time range, so changes you observe are more likely to reflect real-world change rather than differences in how each period was modeled.

For Safety Hub subscribers, the Before-After application enables easy comparison of traffic, speeds, and driver behavior across time for specific corridors.

Read our detailed Seasonal Data Methodology here.