311-data report improvements

[KarinaLopez19]

Description

Improving existing data reports to make them more accessible and meaningful to users.

Action Items

• Review existing reports and identify pain-points for users less comfortable with data (e.g., Add plot descriptions)
• Identify points of improvements to make plots more meaningful to different audiences (e.g., features helpful for neighborhood council members, neighbor, activist)
• Prototype Plotly reports following these suggestions
• Review final reports and publish on website

Resources

• Slide deck offering quick improvement suggestions
• Brainstorming notes
• Existing Plotly reports
• Plotly gallery
• Storage for Matt Recordings

[KarinaLopez19]

Assigned issue to @chelseybeck. Here is the onboarding data science document for the 311 project. Under the resources section of this issue, you will also find a slide deck and notes that may be helpful to review.

[chelseybeck]

Review existing reports and identify pain points for users less comfortable with data.

Recommendations

• include a high-level description for each report page (e.g., the figure below displays the total number of 311 requests made across LA county from 2016-2021. During 2020, there was an all-time high of over 1.4 million requests made.)
• include a high-level description for each figure (e.g., This visualization represents the volume of 311-requests per neighborhood from 2016-2020.)
• replace all pie graphs with donut charts
• replace all column charts with stacked bar charts - here is a tutorial w/ a great intro to Plotly's Dash Framework

Dashboards

Overview

• Remove bottom graph of total requests by neighborhood until we can add population/housing data. Empower LA has data on housing units that would probably work well. We should explore tapping into that. The issue with leaving the bar graph up without population data is that the number of housing units per neighborhood council varies from around 6k to more than 20k. This creates the concern of misrepresentation of the data.
• Potentially show a stacked bar (or even a line plot with area in red) depicting the number of requests CLOSED in that time frame. This may be a helpful visual to showcase how many requests are left open each year. See sample visualizations in the link below.
• turn total requests by year into line plot

Neighborhoods

• Add functionality for users to select date ranges in addition to neighborhoods
• Rotate total requests by neighborhood chart at bottom of page to horizontal

311 Report Improvements sample visualizations

[chelseybeck]

Identify points of improvements to make plots more meaningful to different audiences

[ExperimentsInHonesty]

@chelseybeck is this issue completed with the PP #1133 Please provide update

1. Progress
2. Blockers
3. Availability
4. ETA

[chelseybeck]

@ExperimentsInHonesty - no. I'm breaking this down into multiple issues for the data science team so I need to move everything over before I close. Will be done tonight.

[EchoProject]

Closing issue #1107 because it seems like it's covered under this epic.

[chelseybeck]

Closing this as the issue has been broken into smaller issues inside the data science repo