System
Colorado Traffic Tracker turns live road speeds and CDOT reports into a clear view of current and past conditions on I-25 and I-70. It keeps history, handles imperfect source data, and explains when information may be delayed.
How it works
Read current speeds from TomTom and road reports from CDOT.
Keep the tracked miles, place speeds on precise road markers, and follow incidents over time.
Show off current conditions alongside historical averages and offer truthful answers if data is delayed.
A closer look
Each stage has one job. Follow either traffic speeds or road incidents from its source to the screen.
Defines the tracked parts of I-25 and I-70 instead of depending on a provider to describe the roads.
Shows how traffic is moving now, alongside the speed drivers could expect in clear conditions.
Turns detailed reports about crashes, closures, construction, and planned events into the updates drivers can use.
Source feeds can be limited, late or incomplete, so each update is checked before it changes public data.
Each successful collection refreshes the current corridor picture while retained snapshots build history.
An incident keeps its history across updates.
A failed or incomplete update does not replace the last complete report.
History is a long-term asset.
Corridor speeds
Half-mile road state
Current incidents
Traffic and speed zones
Hourly road sections
Incident changes
Provider health
Request budgets
Scheduled work
Live and archived views
Summary calculations
Time-series support
Older rows move into queryable archive tables instead of being deleted.
The dashboard and public API share one service but use separate routes.
Corridor summaries
Incidents
Half-mile road state
System health
Traffic samples
Speed zones
Replay windows
Hourly map data
Historical baselines
Trends and hotspots
Unusual slowdowns
Short local trends
Dashboard responses
Map geometry
Bounded public reads
Cache and rate limits
Current conditions, historical comparisons, speed zones, incidents, replay, corridor maps, and clear system health.
Fast answers, backed by retained historyThis makes locations consistent even when the source geometry changes.
First-seen time, last-seen time, and status persist across provider updates to build an extended historical reference.
Live and archived rows share one read path, so long-range views keep growing over time.
Production runtime
Four isolated containers with explicit health checks. The dashboard is served by the API container.
Operations & recovery
Engineering verification
Every change travels the same visible path. Independent gates check the application, browser, recovery tools, and backup client.
One clear scope
Pinned toolchain
Results collected
Evidence attached
Each gate covers a different failure mode. A release is ready only when the applicable set is clear.
Current operational state
Health is based on when data was successfully observed and comparatively verified, not whether traffic speeds changed.
The application is checking flow freshness, CDOT snapshot freshness, and TomTom provider state.
Waiting for the status response…
The server reports externally twice daily. It allows one hour for traffic and CDOT freshness, warns after eight days without an off-site backup, and warns at 10 GB of available disk space.
Every warning includes what happened and a next action.
