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

neighborhood stats #12

Open
mrcnc opened this issue Dec 21, 2016 · 5 comments
Open

neighborhood stats #12

mrcnc opened this issue Dec 21, 2016 · 5 comments
Assignees

Comments

@mrcnc
Copy link
Member

mrcnc commented Dec 21, 2016

It would be useful to view the following stats for each neighborhood:

  • Total number of open tickets
  • Total number tickets by type
  • Rank median time to close across all neighborhoods
  • Median time to close (across all, and by type)
  • Top issue type
  • Most recently opened tickets
  • Most recently closed tickets
  • YTD number of closed tickets
@nihonjinrxs nihonjinrxs self-assigned this Dec 21, 2016
@mrcnc
Copy link
Member Author

mrcnc commented Sep 22, 2017

I think an interactive d3 donut chart like this would be an interesting way to see issue types by neighborhood:
http://bl.ocks.org/juan-cb/1984c7f2b446fffeedde

You could create a category called "other" for types that are less than 5% of the total.

Also creating a slider component to allow exploring by year would make it the visualization interactive:
http://jsfiddle.net/Q3dhh/25/

@nihonjinrxs
Copy link
Member

Not so sure about the donut chart idea. See this talk for why.

Slider idea could be nice.

@mrcnc
Copy link
Member Author

mrcnc commented Sep 22, 2017

Very interesting talk with some great information! But I still believe a donut chart can use area to effectively communicate the percentage of request types, even though that may be subjective. The only alternative I can see would be to just show the data in a table...something like this:

nola311=> with totals as (select count(*) as total, issue_type from calls where neighborhood_district = 'MARIGNY' group by issue_type order by total desc) select issue_type, total from totals;
             issue_type              | total
-------------------------------------+-------
 Abandoned Vehicle Reporting/Removal |   453
 Trash/Garbage Pickup                |   373
 Residential Recycling Programs      |   269
 Large Item Trash/Garbage Pickup     |   207
 Street Light                        |   195
 Street Flooding/Drainage            |   113
 Code Enforcement General Request    |    99
 Traffic Sign                        |    79
 Pothole/Roadway Surface Repair      |    75
 Tree Service                        |    57
 Catch Basin Maintenance             |    51
 Traffic Signal                      |    50
 Sidewalk Repair                     |    36
 Illegal Dumping Reporting           |    17
 Tree Service Emergency              |    16
 Manhole Cover Maintenance           |    15
 Mosquito Control                    |    12
 Tree Maintenance                    |    12
 Rodent Complaint                    |    11
 Road Surface Marking                |     8
 Subsidence                          |     8
 Street Name Sign                    |     6
 Dead Animal Pickup                  |     6
 Road Shoulder Repair                |     5
 General Service Request             |     5
 Park Maintenance                    |     4
 Curb Repair                         |     2
 Grass Service                       |     1
 Non Rodent Complaint                |     1
(29 rows)

While the table shows all of the data, I find a donunt chart is more compelling. Thoughts?

@nihonjinrxs
Copy link
Member

A stacked percentage bar, or just a regular bar chart, would be more effective for that than a pie or donut. It's more difficult to perceive angle differences than relative length differences.

A table is also likely more effective than a pie or donut, but perhaps not as good as some sort of bar chart.

@nihonjinrxs
Copy link
Member

Note the ranking of visual encodings:

rauservelocityamsterdam2016-visualencodingsofdata

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants