cityofchicago/chicago-traffic-tracker-congestion-estimates-by-n4j6-wkkf
Icon for Socrata external plugin
 
Readme
Updated 22 days ago
Indexed 5 hours ago

Chicago Traffic Tracker - Congestion Estimates by Segments

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.

Querying over HTTP

Splitgraph serves as an HTTP API that lets you run SQL queries directly on this data to power Web applications. For example:

curl https://data.splitgraph.com/sql/query/ddn \
    -H "Content-Type: application/json" \
    -d@-<<EOF
{"sql": "
    SELECT *
    FROM \"cityofchicago/chicago-traffic-tracker-congestion-estimates-by-n4j6-wkkf\".\"chicago_traffic_tracker_congestion_estimates_by\"
    LIMIT 100 
"}
EOF

See the Splitgraph documentation for more information.

 
Preview
  • chicago_traffic_tracker_congestion_estimates_by
     
Upstream Metadata