hackforla / access-the-data

The Access the Data project was created to address the growing gaps between new technology development and decisions impacting our communities with the underlying systems and data that drive those initiatives
GNU General Public License v2.0
18 stars 2 forks source link

311 Data Storyline Brainstorm #89

Closed snooravi closed 2 years ago

snooravi commented 2 years ago

Overview

We are looking to anchor on a story that will be interesting to LA citizens leveraging available 311 data. Example storylines we have considered:

Action Items

Each member of the Access the Data Workshop will provide 1-3 different ideas for us to consider in Wednesday's team meeting.

Resources/Instructions

311data.org

MalakH21 commented 2 years ago

@MalakH21 's ideas

  1. Not sure if graffiti harbors some of the same sentiment as homeless encampments - but it seems like a good storyline to consider since the reporters here cited the usage of 311. Although you can only use the Alpha tool to go back as far in time as cited in the article, the map and data visualization tools lend themselves very well to understanding volume change. There could also be a local understanding of where a mural exists or street art and that could be used in conjunction with the tool to see how requests in that specific spot have changed over time vs. more "non-artistic" graffiti.
  2. Explore the interactions between [SSL] Single Streetlight and [MSL] Multiple Streetlight requests and particular intersects and traffic collision data and here to see if there is any correlation - it might be difficult to pinpoint because it would involve digging into the why of the accident, which may not be worth doing
ShikaZzz commented 2 years ago

Service request data from MyLA311 for 2015 - 2021 data source: LA open data

explore the data patterns and trends in:

with respect to request # per person/NC

so that we could see if there is anything interesting to make suggestions on e.g a specific request overwhelms in several NC's

(simple ML prediction?)

mcmorgan27 commented 2 years ago

Background A bit of background/moodling to start:

  1. I too am using the MyLA311 data set.
  2. Thinking of 311 systems and interoperability should be a long term goal, but probably beyond scope now.
  3. Always a good place to help in thinking about use cases
  4. One example of system wide analytic thinking.
  5. Finally, one idea for a data driven application? Could we building something like the neighborhood indicators in SF?

I'm thinking of scoping base on different "user" types:

  1. Joe Citizen - local resident
  2. Suzy Small Biz owner - brings a commercial perspective to the problem/questions
  3. NC board member/citizen volunteer
  4. City level "planner" and "service agencies"

I'm thinking about this from the data not the existing web app. I'm starting to look at viability of these ideas in the app.

Use Cases/Storylines

  1. Analyze at the Address Level - This question leads to an understanding of the blighted properties, properties that cause the most problems. A generalization would be to look at reports by street (probably filtered by geographic NC area), ... This would primarily be focused at users 1, 2, 4
  2. Analyze by request type + time - Get some averages for different services types. Target users 3, 4.
  3. Analyze by "owner" (service org) + time - What are the patterns for each of the orgnanizations that service requests. Target users 3, 4.
  4. Analyze by NC + use cases 2 and 3 - Combine basics geospatially? Target users 3, 4.
  5. Analyze with "other" NC information - This may be over the horizon but consider foundation geometry combined with 1) demographics for pop density; 2) or osmnx by NC; or 3) or zoning geo's for commercial vs residential NC's; ...

These are some basic ideas. I will look at the reference doc on 311 users from last night to see specifics of alignment. I will put together more details for next monday. Don't want to spend a lot of time if this is too far afield.

snooravi commented 2 years ago

Next steps: Chose your favorite topic and explore the datasets within or that would support to review on Wednesday with the team.

MalakH21 commented 2 years ago

@MalakH21 's ideas

  1. Not sure if graffiti harbors some of the same sentiment as homeless encampments - but it seems like a good storyline to consider since the reporters here cited the usage of 311. Although you can only use the Alpha tool to go back as far in time as cited in the article, the map and data visualization tools lend themselves very well to understanding volume change. There could also be a local understanding of where a mural exists or street art and that could be used in conjunction with the tool to see how requests in that specific spot have changed over time vs. more "non-artistic" graffiti.
  2. Explore the interactions between [SSL] Single Streetlight and [MSL] Multiple Streetlight requests and particular intersects and traffic collision data and here to see if there is any correlation - it might be difficult to pinpoint because it would involve digging into the why of the accident, which may not be worth doing

relevant to #1 & #2 service request data - https://data.lacity.org/City-Infrastructure-Service-Requests/MyLA311-Service-Request-Data-2020/rq3b-xjk8

data source for #2 https://data.lacity.org/Public-Safety/Traffic-Collision-Data-from-2010-to-Present/d5tf-ez2w has codes for which types of collisions were caused by stop signs/street lights

data sources for #1 more context on grafitti cleaning in LA http://laocb.org/programs/graffiti-abatement/

snooravi commented 2 years ago

Notes:

ExperimentsInHonesty commented 2 years ago

Re this post https://github.com/hackforla/access-the-data/issues/89#issuecomment-960305167

The definition of graffiti is unsanctioned painting on a surface

If you paint on a wall with the owner's permission is art if you paint on the wall without the owner's permission, it's graffiti

Not sure if graffiti harbors some of the same sentiment as homeless encampments - but it seems like a good storyline to consider since the reporters here cited the usage of 311. Although you can only use the Alpha tool to go back as far in time as cited in the article, the map and data visualization tools lend themselves very well to understanding volume change. There could also be a local understanding of where a mural exists or street art and that could be used in conjunction with the tool to see how requests in that specific spot have changed over time vs. more "non-artistic" graffiti.

Have you tried the Hack for LA 311 tool https://311-data.org?

Explore the interactions between [SSL] Single Streetlight and [MSL] Multiple Streetlight requests and particular intersects and traffic collision data and here to see if there is any correlation - it might be difficult to pinpoint because it would involve digging into the why of the accident, which may not be worth doing

Have you reviewed the work Henry Kaplan did for Greater Wilshire NC

ExperimentsInHonesty commented 2 years ago

@snooravi @mcmorgan27 @MalakH21 @ShikaZzz I think Sarah is indicting what I am about explicitly spell out, but I do want to leave the note on this issue for future team members.

After having read all the brainstorming here, I am appreciative of all the talent on this team.

I think this is a great starting point

@mcmorgan27 I'm thinking of scoping base on different "user" types:

  1. Joe Citizen - local resident
  2. Suzy Small Biz owner - brings a commercial perspective to the problem/questions
  3. NC board member/citizen volunteer
  4. City level "planner" and "service agencies"

I'm thinking about this from the data not the existing web app. I'm starting to look at viability of these ideas in the app.

Data Analysis using the raw data from the portal is too high a level for the initial workshop. Our team will focus on building our workshop, which is how to use the 311-data.org tools and the Alpha Report Tool https://hackforla.github.io/311-report/

snooravi commented 2 years ago

Final outcome:

We will focus on grafitti volume in LA over time in various neighborhoods.