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

data.cityofchicago.org | Last Updated 16 Jul 2021

This dataset contains the historical estimated congestion for over 1,000 traffic segments, starting in approximately March 2018. Older records are in https://data.cityofchicago.org/d/77hq-huss. The most recent estimates for each segment are 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.

Tags: traffic, sustainability, historical, link to article present

This dataset has the following 22 columns:

Column NameAPI Column NameData TypeDescriptionSample Values
TIMEtimecalendar_date
SEGMENT_IDsegment_idnumberUnique arbitrary number to represent each segment.
SPEEDspeednumberEstimated traffic speed in miles per hour. A value of -1 means no estimate is available.
STREETstreettextStreet name of the traffic segment.
DIRECTIONdirectiontextTraffic flow direction for the segment.
FROM_STREETfrom_streettextStart street for the segment in the direction of traffic flow.
TO_STREETto_streettextEnd street for the segment in the direction of traffic flow.
LENGTHlengthnumberLength of the segment in miles.
STREET_HEADINGstreet_headingtextThe position of the segment in the address grid. North, South, East, or West of State and Madison.
COMMENTScommentstext
BUS_COUNTbus_countnumberNumber of buses providing a GPS feed used to estimate congestion.
MESSAGE_COUNTmessage_countnumberNumber of GPS probes received(or used) for estimating the speed for that segment.
HOURhournumberHour of the day.
DAY_OF_WEEKday_of_weeknumberDay of the week. Sunday = 1
MONTHmonthnumberMonth of the year.
RECORD_IDrecord_idtextA unique identifier for each record in the dataset.
START_LATITUDEstart_latitudenumberLatitude of the start of the segment.
START_LONGITUDEstart_longitudenumberLongitude of the start of the segment.
END_LATITUDEend_latitudenumberLatitude of the end of the segment.
END_LONGITUDEend_longitudenumberLongitude of the end of the segment.
START_LOCATIONstart_locationpointLocation of the start of the segment.
END_LOCATIONend_locationpointLocation of the end of the segment.