DataShield Ontology
SOCRATATransportationofficialSee Terms of Use

Chicago Traffic Tracker - Historical Congestion Estimates by Segment - 2018-2023

Attribution: City of Chicago · source

This dataset contains the historical estimated congestion for over 1,000 traffic segments, starting in approximately 2/28/2018 and ending 9/8/2023. Older records are in https://data.cityofchicago.org/d/77hq-huss. Newer records are in https://data.cityofchicago.org/d/4g9f-3jbs. The most recent estimate for each segment is in https://data.cityofchicago.org/d/n4j6-wkkf. The Chicago Traffic Tracker estimates traffic congestion on Chicago’s arterial streets (non-freeway streets) in real-time by continuously monitoring and analyzing GPS traces received from Chicago Transit Authority (CTA) buses. Two types of congestion estimates are produced every 10 minutes: 1) by Traffic Segments and 2) by Traffic Regions or Zones. Congestion estimates by traffic segments gives observed speed typically for one-half mile of a street in one direction of traffic. Traffic Segment level congestion is available for about 300 miles of principal arterials. Congestion by Traffic Region gives the average traffic condition for all arterial street segments within a region. A traffic region is comprised of two or three community areas with comparable traffic patterns. 29 regions are created to cover the entire city (except O’Hare airport area). There is much volatility in traffic segment speed. However, the congestion estimates for the traffic regions remain consistent for a relatively longer period. Most volatility in arterial speed comes from the very nature of the arterials themselves. Due to a myriad of factors, including but not limited to frequent intersections, traffic signals, transit movements, availability of alternative routes, crashes, short length of the segments, etc. Speed on individual arterial segments can fluctuate from heavily congested to no congestion and back in a few minutes. The segment speed and traffic region congestion estimates together may give a better understanding of the actual traffic conditions.

trafficsustainabilityhistorical
← Back to browse

Dataset Profile

274.9M
Total records
25
Columns
table
Type
ID: sxs8-h27x

Popularity

70.4K
Views
12.3K
Downloads
~274.9M rows · 25 columns

Freshness & Tracking

Rows updated1 years ago · 5/15/2025
View modified5 months ago
Created on source2/28/2018
Published3/1/2018
Discovered5/13/2026, 11:38:35 PM
Last checked5/13/2026, 11:38:35 PM
Last changed5/13/2026, 11:38:35 PM
Reads0
Search hits9
View raw source ↗
📁

No files attached

Upload a file to get started

Owner & Attribution

OwnerJonathan Levy
AuthorJonathan Levy
PublisherCity of Chicago

Metadata

Data OwnerChicago Department of Transportation
Time Period2/28/2018 - 9/8/2023, with occasional gaps due to system maintenance and other temporary technical issues.
Changes and Other Historical Information Useful to Understanding This Datasethttps://www.google.com/search?q=site:data.cityofchicago.org/stories+"Related+dataset+ID+s"+"sxs8-h27x"

Schema (25 columns)

Column metadata from the source provider's own profiling

ColumnTypeCardinalityNullsTop ValuesRange
TIME
calendar_date11.0M0
2018-02-28T20:40:00.2018-02-28T23:50:00.2018-02-28T21:01:00.
2018-02-28T1 … 2023-09-08T1
SEGMENT_ID
Unique arbitrary number to represent each segment.
number1.0K0
130713051152
1 … 1309
SPEED
Estimated traffic speed in miles per hour. A value of -1 means no estimate is available.
number670
-12523
-1 … 65
STREET
Street name of the traffic segment.
text620
WesternPulaskiHalsted
111th … Western
DIRECTION
Traffic flow direction for the segment.
text80
NBSBEB
EB … WB
FROM_STREET
Start street for the segment in the direction of traffic flow.
text1450
HalstedAshlandWestern
103rd … Woodlawn
TO_STREET
End street for the segment in the direction of traffic flow.
text1440
HalstedAshlandDamen
103rd … Woodlawn
LENGTH
Length of the segment in miles.
number1060
0.50.510.49
0.07 … 1.54
STREET_HEADING
The position of the segment in the address grid. North, South, East, or West of State and Madison.
text40
SWN
E … W
COMMENTS
text12241.5M
IDOT Signals PossiblOutside City LimitsOneway
IDOT Signal … Western Blvd
BUS_COUNT
Number of buses providing a GPS feed used to estimate congestion.
number500
012
0 … 52
MESSAGE_COUNT
Number of GPS probes received(or used) for estimating the speed for that segment.
number5980
01110
0 … 1027
HOUR
Hour of the day.
number240
171216
0 … 23
DAY_OF_WEEK
Day of the week. Sunday = 1
number70
645
1 … 7
MONTH
Month of the year.
number120
784
1 … 12
RECORD_ID
A unique identifier for each record in the dataset.
text11.0M0
2018-02-28T20:40:00.2018-02-28T23:50:00.2018-02-28T21:01:00.
2018-02-28T1 … 2023-09-08T1
START_LATITUDE
Latitude of the start of the segment.
number1.9K0
41.87423841.81618441.838046
41.65897022 … 42.01283101
START_LONGITUDE
Longitude of the start of the segment.
number1.9K0
-87.639487-87.645915-87.647745
-87.83676501 … -87.535052
END_LATITUDE
Latitude of the end of the segment.
number1.9K0
41.8307541.80886441.816184
41.65900629 … 42.012828860
END_LONGITUDE
Longitude of the end of the segment.
number1.9K0
-87.639487-87.645915-87.647745
-87.83683351 … -87.535052
START_LOCATION
Location of the start of the segment.
point1.1K0
[object Object][object Object][object Object]
END_LOCATION
Location of the end of the segment.
point1.1K0
[object Object][object Object][object Object]
Community Areas
number
Zip Codes
number
Wards
number

Send Feedback