cityofchicago/311-service-requests-pot-holes-reported-historical-7as2-ds3y
Icon for Socrata external plugin
Open repository in Console
 
Readme
Updated almost 4 years ago
Indexed 4 hours ago

311 Service Requests - Pot Holes Reported - Historical

As described in http://bit.ly/311HistoricalPost, the function of this dataset was replaced by https://data.cityofchicago.org/d/v6vf-nfxy. This dataset is historical-only.

The Chicago Department of Transportation (CDOT) oversees the patching of potholes on over 4,000 miles of arterial and residential streets in Chicago. CDOT receives reports of potholes through the 311 call center and uses a computerized mapping and tracking system to identify pothole locations and efficiently schedule crews. One call to 311 can generate multiple pothole repairs. When a crew arrives to repair a 311 pothole, it fills all the other potholes within the block. Pothole repairs are generally completed within 7 days from the first report of a pothole to 311. Weather conditions, particularly frigid temps and precipitation, influence how long a repair takes. On days when weather is cooperative and there is no precipitation, crews can fill several thousand potholes.

If a previous request is already open for a buffer of 4 addresses the request is given the status of "Duplicate (Open)". For example, if there is an existing CSR for 6535 N Western and a new request is received for 6531 N Western (which is within four addresses of the original CSR) then the new request is given a status of "Duplicate (Open)".

Once the street is repaired, the status in CSR will read “Completed” for the original request and "Duplicate (Closed)" for any duplicate requests. A service request also receives the status of “Completed” when the reported address is inspected but no potholes are found or have already been filled. If another issue is found with the street, such as a “cave-in” or “failed utility cut”, then it is directed to the appropriate department or contractor.

Data Owner: Transportation. Time Period: All open requests and all completed requests since January 1, 2011. Frequency: Data is updated daily.

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/311-service-requests-pot-holes-reported-historical-7as2-ds3y\".\"311_service_requests_pot_holes_reported_historical\"
    LIMIT 100 
"}
EOF

See the Splitgraph documentation for more information.

 
Preview
  • 311_service_requests_pot_holes_reported_historical
     
     
     
     
     
Upstream Metadata