Skip to content

Issues: code-for-chapel-hill/CrashModel

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.

Sign up for GitHub

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

8 Open 19 Closed
8 Open 19 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Work with CSS to improve mobile experience (v3)
#26 opened May 1, 2019 by garrisonreid
1
System must use model instead of computed danger score from previous version (v4)
#25 opened Apr 30, 2019 by garrisonreid
System must train machine learning model to predict scores for segments and intersections (v4)
#24 opened Apr 30, 2019 by garrisonreid
System must allow searching of an address and then zooming to that address (v4)
#23 opened Apr 30, 2019 by garrisonreid
System must allow filtering of intersections/segments by score (v3)
#22 opened Apr 30, 2019 by garrisonreid
System must highlight all intersections/segments color coded by danger score (v3)
#21 opened Apr 30, 2019 by garrisonreid
System must compute a danger score from the number of crashes for each intersection and road segment (v3)
#20 opened Apr 30, 2019 by garrisonreid
[low priority/easy] Move geo functions from crash_model.js to geo_functions.js
#19 opened Apr 1, 2019 by bimbashrestha
1
ProTip! Find all open issues with in progress development work with linked:pr.