Chicago

List of all Chicago streets with suffixes and minimum and maximum address numbers.

Map shows physical locations where CTA fare media, such as Transit Cards, CTA Passes and Chicago Cards were sold through approximately July 2014, prior to the implementation of Ventra cards. The locations for Ventra card sales/reloading are more extensive and not yet available in this format. Please see http://www.transitchicago.com/ventra for information on the Ventra program and https://www.ventrachicago.com/retailers/locations to find Ventra retail locations.

This dataset displays location for vehicles that have been towed and impounded by the City of Chicago within the last 90 days. Illegally parked vehicles, abandoned vehicles and vehicles used for illegal activities may be towed by the Chicago Police Department, the Department of Streets and Sanitation, the Department of Revenue, Aviation and the office of the City Clerk. After a tow request is issued, an inventory number is assigned by the Department of Streets and Sanitation and a truck is dispatched to tow the requested vehicle to a City auto pound. Disclaimer: This dataset includes vehicles towed or relocated by the City of Chicago; it does not include vehicles towed by a private towing company. Background Info: Auto Pound Locations (http://j.mp/kG5sgF). Tow Process Overview (http://j.mp/lfBOEP). Common Towing Questions (http://j.mp/imFYlp). Parking and Standing Violations (http://j.mp/ifW8Uj). Data Owner: Chicago Police Department. Time Period: Last 90 days. Frequency: Data is updated daily. Related Applications: Find Your Vehicle (http://j.mp/lWn0S7).

This lists datasets published by CTA in the City of Chicago Data Portal.

Average Daily Traffic (ADT) counts are analogous to a census count of vehicles on city streets. These counts provide a close approximation to the actual number of vehicles passing through a given location on an average weekday. Since it is not possible to count every vehicle on every city street, sample counts are taken along larger streets to get an estimate of traffic on half-mile or one-mile street segments. ADT counts are used by city planners, transportation engineers, real-estate developers, marketers and many others for myriad planning and operational purposes. Data Owner: Transportation. Time Period: 2006. Frequency: A citywide count is taken approximately every 10 years. A limited number of traffic counts will be taken and added to the list periodically. Related Applications: Traffic Information Interactive Map (http://webapps.cityofchicago.org/traffic/).

Current permitted street closures in Chicago by location, date and type. Closures due to construction or other work being performed in the thoroughfare are indicated by the “Street Full Closure” permit type. Street closure permits are also granted for festivals, athletic events, block parties, parades, and movie or other filming. Data Owner: Transportation. Time Period: All closure permits for current day. Frequency: Data is updated daily. Related Applications: Today’s Street Closures (http://webapps.cityofchicago.org/StreetClosure/org/cityofchicago/streetclosure/cdot/getreport.do).

This dataset shows CTA Bus Stop shelters which are slated to have digital signs added to them to show upcoming arrivals. The listing is subject to change.

Average Daily Traffic (ADT) counts are analogous to a census count of vehicles on city streets. These counts provide a close approximation to the actual number of vehicles passing through a given location on an average weekday. Since it is not possible to count every vehicle on every city street, sample counts are taken along larger streets to get an estimate of traffic on half-mile or one-mile street segments. ADT counts are used by city planners, transportation engineers, real-estate developers, marketers and many others for myriad planning and operational purposes. Data Owner: Transportation. Time Period: 2006. Frequency: A citywide count is taken approximately every 10 years. A limited number of traffic counts will be taken and added to the list periodically. Related Applications: Traffic Information Interactive Map (http://webapps.cityofchicago.org/traffic/).

Major streets in Chicago. To view or use these files, compression software and special GIS software, such as ESRI ArcGIS, is required.

This list shows daily totals of ridership, by station entry, for each 'L' station dating back to 2001. Dataset shows entries at all turnstiles, combined, for each station. Daytypes are as follows: W=Weekday, A=Saturday, U=Sunday/Holiday. See attached readme file for information on how these numbers are calculated.

This dataset shows approximate, average, weekday boardings by bus stop from the month of October 2012.

Bike racks in Chicago. To view or use the attachment files, compression software and special GIS software, such as ESRI ArcGIS, is required.

This dataset contains the current estimated congestion for the 29 traffic regions. For a detailed description, go to: http://bitly.com/TeqrNv. 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.

This dataset presents current and former locations of vehicles that have been relocated by the City of Chicago within the last 90 days. Vehicles may be relocated, but not impounded, due to inoperability, accident, severe weather, special events, construction or other work being performed in a thoroughfare where the vehicle was previously located. Data Owner: Streets & Sanitation. Time Period: Last 90 days. Frequency: Data is updated daily. Related Applications: Find Your Vehicle (http://j.mp/iZiX0B).

The Chicago Department of Transportation (CDOT) reviews applications for permits for the temporary use of the public way for construction projects, parades, festivals, block parties, athletic events, etc.This dataset includes permits applied for, issued, amended and expired with permit start dates beginning January 1, 2011. Note a permit may be amended if any details are changed after the initial issuance. For more information about Public Right-of-Way Use Permits, go to http://bit.ly/15ypkkL.

This dataset shows systemwide boardings for both bus and rail services provided by CTA, dating back to 2001. Daytypes are as follows: W = Weekday, A = Saturday, U = Sunday/Holiday. See attached readme file for information on how these numbers are calculated.

Bike racks in Chicago. To view or use the attachment files, compression software and special GIS software, such as ESRI ArcGIS, is required.

This dataset shows total daily ridership on a per-route basis dating back to 2001. Daytypes are as follows: W=Weekday, A=Saturday, U=Sunday/Holiday. See attached readme file for more detailed information.

Street center lines in Chicago. To view or use these files, compression software and special GIS software, such as ESRI ArcGIS, is required. Metadata may be viewed and downloaded at http://bit.ly/HLdp8B.

List of physical locations where fare media were sold through approximately July 2014, prior to the implementation of Ventra cards. The locations for Ventra card sales/reloading are more extensive and not yet available in dataset format. Please see http://www.transitchicago.com/ventra for information on the Ventra program and https://www.ventrachicago.com/retailers/locations to find Ventra retail locations.

Lines representing approximately where the CTA rail lines are. To view or use these files, compression software and special GIS software, such as ESRI ArcGIS is required. Projected Coordinate System: NAD_1983_StatePlane_Illinois_East_FIPS_1201_Feet

This dataset gives annual ridership totals dating to the mid-1980s. Numbers are presented in boardings (see attached readme file for information on how these numbers are calculated).

This dataset contains the historical estimated congestion for 1270 traffic segments. 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/Vz3rIh.

This dataset contains the current estimated speed for about 1250 segments covering 300 miles of arterial roads. For a more detailed description, go to: http://bit.ly/Q9AZAD. The Chicago Traffic Tracker estimates traffic congestion on Chicago’s arterial streets (nonfreeway 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 ten minutes: 1) by Traffic Segments and 2) by Traffic Regions or Zones. Congestion estimate by traffic segments gives the 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). This dataset contains the current estimated speed for about 1250 segments covering 300 miles of arterial roads. There is much volatility in traffic segment speed. However, the congestion estimates for the traffic regions remain consistent for 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.

OUTDATED, HISTORICAL VERSION -- Lines representing approximately where the CTA 'L' (rail) lines are. To view or use these files, special GIS software, such as Google Earth, is required.