Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review of time-to-close data #318

Open
smarziano opened this issue Feb 4, 2014 · 0 comments
Open

Review of time-to-close data #318

smarziano opened this issue Feb 4, 2014 · 0 comments
Assignees

Comments

@smarziano
Copy link
Member

There were questions from Alderman staff regarding time-to-close data on their ward page. They believe that a time-to-close of 0.68 days was unrealistic for the types of service requests that were made during that week.

An example is Graffiti removal time-to-close (image below) had 11 requests and 0.04 days to close. The Alderman staff said it could take a couple of days for graffiti to be removed.
image

Looking at Ward 49's information on the City of Chicago Data Portal for Graffiti removal requests, we see that requests were made on the same day that the crew completed the work: https://data.cityofchicago.org/Service-Requests/311-Service-Requests-Graffiti-Removal/hec5-y4x5

How can we provide a better understanding of time-to-close rankings?

@ghost ghost assigned danxoneil Feb 4, 2014
@danxoneil danxoneil assigned smarziano and unassigned danxoneil Feb 7, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants