cityofchicago/chicago-traffic-tracker-historical-congestion-kf7e-cur8

  • historical
  • link to article present
  • sustainability
  • traffic

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

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

This dataset contains the historical estimated congestion for the 29 traffic regions, starting in approximately March 2018. Older records are in https://data.cityofchicago.org/d/emtn-qqdi. The most recent estimates for each segment are in https://data.cityofchicago.org/d/t2qc-9pjd.

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. Current estimates of traffic congestion by region are available at http://bit.ly/103beCf.

Columns

NameSocrata field nameColumn name in sgr mountData typeDescription
Zip Codes:@computed_region_6mkv_f3dw:@computed_region_6mkv_f3dwNumber
EASTeasteastNumberApproximate longitude of the east edge of the region.
NW_LOCATIONnw_locationnw_locationPointThe location corresponding to the intersection of NORTH and WEST in a format that allows for creation of maps and other geographic operations on this data portal.
MONTHmonthmonthNumberThe month component of TIME.
SOUTHsouthsouthNumberApproximate latitude of the south edge of the region.
DAY_OF_WEEKday_of_weekday_of_weekNumberThe day of the week component of TIME. Sunday=1
RECORD_IDrecord_idrecord_idTextUnique arbitrary number to represent each region.
Community Areas:@computed_region_vrxf_vc4k:@computed_region_vrxf_vc4kNumber
REGION_IDregion_idregion_idNumberUnique arbitrary number to represent each region.
BUS_COUNTbus_countbus_countNumberThe number of buses used to estimate traffic.
SE_LOCATIONse_locationse_locationPointThe location corresponding to the intersection of SOUTH and EAST in a format that allows for creation of maps and other geographic operations on this data portal.
TIMEtimetimeCalendar dateTimestamp of the record.
WESTwestwestNumberApproximate longitude of the west edge of the region.
NUM_READSnum_readsnum_readsNumberNumber of GPS probes received(or used) for estimating the speed for that segment.
REGIONregionregionTextName of the region.
SPEEDspeedspeedNumberEstimated congestion level. Although expressed in miles per hour, this value is more a reflection of the congestion level in the region than it is indicative of the average raw speed vehicles are travelling within the region.
HOURhourhourNumberThe hour of the day component of TIME.
DESCRIPTIONdescriptiondescriptionTextDescription of the region.
NORTHnorthnorthNumberApproximate latitude of the north edge of the region.
Wards:@computed_region_43wa_7qmu:@computed_region_43wa_7qmuNumber

Upstream Metadata