GuidesKB Articles
Guides
  1. Getting Started

Traffic Analytics API returns data for non-existent DST hour (02:00–03:00), is this an error?

Symptoms / Triggers

  • Data returned for 02:00–03:00 on Daylight Saving Time (DST) transition day

  • Timestamps exist for hours that did not occur locally

  • Full 24-hour dataset even on DST change days

  • Suspected incorrect or inconsistent time data

  • Questions about handling DST transitions in API results

Quick Answer

This is not an error. When gap-filling is enabled, the Traffic Analytics API returns a complete 24-hour dataset, including estimated values for missing DST hours based on historical traffic patterns.

Why This Happens

  • API returns data in 24-hour local time format

  • During DST transition, some hours do not exist locally

  • System still includes these hours to maintain consistency

  • Non-existent hours are populated with valid estimated data

How Gap-Filling Works

  • Missing DST hour is filled using historical patterns

  • Ensures continuous time series without gaps

  • Keeps a consistent 24-hour dataset across all days

Is This a Service Issue?

  • No, this is expected behavior

  • Gap-filling ensures data completeness

  • Not a defect in the API

How to Avoid Data for Non-Existent Hours

Option 1 – Split requests:

  • 00:00 – 02:00

  • 03:00 – 23:59

Option 2 – Post-process:

  • Request full dataset

  • Remove 02:00–03:00 entries programmatically

Summary

  • DST can remove local time intervals

  • API still returns 24-hour data

  • Missing hours are filled using historical data

  • Behavior is expected and correct

  • Can be handled via request design or filtering

Applies To

  • Traffic Analytics API

  • Speed Data responses

  • DST transitions

  • Gap-filling enabled queries

Tags

  • daylight saving time traffic api

  • dst missing hour data

  • traffic analytics wrong timestamp

  • non existent hour api data

  • dst transition time series

  • gap filling traffic data