ScrAPD - Analyze traffic fatalities in Austin

[rgreinho]

What problem are you trying to solve?

We are trying to solve 2 problems:

1. The city does not provide a reliable data set of traffic fatalities:
   • open data: https://data.austintexas.gov/Public-Safety/2017-APD-Traffic-Fatalities/ijds-pcyq
   • APD reports: http://austintexas.gov/department/news/296
2. The users need to be able to visualize the data (i.e. with graphs or maps), and generate reports for a given period of time.

Who will benefit (directly and indirectly) from your project?

Mostly local organizations interested in traffic safety (Pedestrian Advisory Council (PAC), Bicycle Advisory Council (BAC), Vision Zero) and anyone else looking for current human and machine readable traffic fatality data.

What other resources/tools are currently serving the same need? How does your project set itself apart?

For existing resources, see section above.

The ScrAPD project is compose of 3 projects:

1. A tool to retrieve the data from the APD report website and convert it into various formats.
2. The data sets
3. A visualization dashboard giving the users a graphical visualization of the data they are searching.

Where can we find any research/data available/articles?

• 2018 PAC retrospective presentation
• The Statesman
• DWI Insights, a prior Open Austin project. (blog post)

What help do you need now?

The most immediate needs is to create the visualization dashboard.

Managing the data sets would also require some help. Using the raw data to create curated/enhanced data sets would absolutely benefit the users.

The extractor is feature complete and in maintenance mode at this point.

What are the next steps (validation, research, coding, design)?

Building a team, working on the data and display it.

Current status:

1. ScrAPD and the documentation
2. ScrAPDviz
3. The data sets

---

Project management

Checklist for NEW ideas 👶

Hey, you're official! You're now part of the growing civic hacking community in Austin. Here's a few things to get started (a couple you've probably already done).

• Create this idea issue
• Flesh out the who, where, and what questions above
• Start the conversation about this idea on Slack Replace this link to the #general channel with your project's preferred channel.

Checklist for ACTIVE projects 🔥

Let's get this project started! When this idea starts taking off, the Projects Core Team will start helping this project's lead(s) out with project management and connecting you to resources you may need. To get there, please complete and check off the following:

• Post an update at least once a month to this issue. Use BASEDEF for ideas, but it's ok even if your update is just "nothing new happened this month" or "we saw a small increase in traffic to our app this month". If there's no activity for two months, that's no problem, life happens. We'll just label this as backlog so others know you'll get back to it when you have the time. If nobody hears from you at all in more than two months, we may mark it as abandoned so that others can pick up this idea and run with it.
• Take 30 minutes to complete Open Leadership 101
• Create a GitHub repository. Ask for help setting up permissions if you want your repository to be within the Open Austin Github organization.
• Create a README file in your project repository. This file should help newcomers understand what your project is, why it's important, and kinds of help you're looking for.
• Create issues to describe each task that you plan to do or need help with and how a contributor can get started on that task. You might start and stop a lot, so consider issues as your to-do list.
• Create a team for your core contributors
  • This will make it easier for you to manage your github repo access. People on a team have the same level of access. Admin access will allow your trusted contributors to make changes as needed.
  • You can remove and add people to your team as needed.
  • View some of our teams: https://github.com/orgs/open-austin/teams
  • Note: You can also allow collaborators outside of your team and give them more limited access.
• Create a user group in Slack so you can "@" your core contributors all at once, without bothering other people who use the Slack channel. You'll need permission from a Slack admin, so just mention @Leadership on Slack to get this set up.
• Create a Google Drive, Dropbox, or other cloud storage to share larger files. Github and Data.World are good for code and data, respectively, especially when you need version control. But they're not good for very large files, documentation, articles, etc. A cloud storage option will allow you to easily share, create, and collaborate on documents with your team and help organize ideas and thoughts.
  • Doing this early on can help your team stay organized and to onboard new contributors who wouldn't have access to files you all have shared over email.

Checklist for FEATURED Projects 🎉

To have your project FEATURED on Open-Austin.org, complete the following documentation. In past projects, well-documented featured projects have more contributions than other projects.

• In your README, link to the Open Austin Code of Conduct or write your own code of conduct.
• Create file: LICENSE to give your project an open license, allowing for sharing and remixing.
• Create file: CONTRIBUTING.md so others know how they can contribute.
• Create an easily shareable project management artifact, like a Civic Tech Canvas or Open Canvas
• Create an issue on the open-austin.github.io repo with the title Add [my project] to projects page. An Open Austin leader will review this issue and post your project 🎈
• Tell the City of Austin. If your idea is in a shareable format and can benefit people around the city, go to that site and follow the instructions on the bottom of the page to showcase your work there.

If you get stuck at any point, feel free to reach out to the leadership team on Slack by adding @Leadership to your message. We're here to help you make real changes to our city.

[thebestmensch]

@rgreinho this looks really cool, nice work. Have you spoken to any potential end-users yet? I'm trying to wrap my head around what problems they would solve using a viz like this.

[rgreinho]

Yes I did, and this project already has potential users waiting for it: Pedestrian Advisory Council (PAC), Bicycle Advisory Council (BAC), Vision Zero.

Basically, every month they do the following:

1. Browse through http://austintexas.gov/department/news/296
2. Manually add new fatality details into a spreadsheet
3. Create a monthly report
4. At the beginning of the year they compile all the data they collected and generate a retrospective of the previous year

The goal of these projects, in addition to the ones mentioned above, is to remove the need for them to perform any manual task. Let ScrAPDviz do the work you need, stop using a spreadsheet.

[cbaumanis]

The best place to get the most accurate fatality data is from the FARS database, but it's not as up-to-date as TxDOT's CRIS database.

APD sends the crash report to TxDOT and then TxDOT uploads crash data to CRIS. CRIS shows BOTH fatalities and non-fatality crashes. There's a lag between when the crash happens, when it gets put into CRIS, and when details get finalized and finally get sent over to NHTSA. However I've personally matched CRIS to FARS and didn't find any discrepancies. The CRIS public database has mapping capabilities.

https://cris.dot.state.tx.us/public/Purchase/app/home/welcome
https://www.nhtsa.gov/research-data/fatality-analysis-reporting-system-fars

[mscarey]

I haven't compared the city's Vision Zero dashboard with ScrAPD feature-for-feature, but it might supersede this project entirely. Most impactful Code for America projects become blueprints for services provided by the government, so being superseded is a good result.

[rgreinho]

Yes, the official Vision Zero dashboard definitely supersedes this project.

The only 2 reasons I keep this project up and running are:

1. I show the names of the victims. It is a requirement for some local organizations.
2. I check APD data hourly. The city updates the dataset on a monthly or bi-monthly basis.

[mateoclarke]

I agree that ScrAPD's project work was a useful product demonstration that helped inspire the Vision Zero Viewer team. Our team at ATD collaborated with @rgreinho during the project planning and implementation. Definitely a success in that way.