Issues

• Work with CSS to improve mobile experience (v3)

  code-for-chapel-hill/CrashModel#26 · Filter by author garrisonreid opened on May 1, 2019
  1

• System must use model instead of computed danger score from previous version (v4)

  code-for-chapel-hill/CrashModel#25 · Filter by author garrisonreid opened on Apr 30, 2019

• System must train machine learning model to predict scores for segments and intersections (v4)

  code-for-chapel-hill/CrashModel#24 · Filter by author garrisonreid opened on Apr 30, 2019

• System must allow searching of an address and then zooming to that address (v4)

  code-for-chapel-hill/CrashModel#23 · Filter by author garrisonreid opened on Apr 30, 2019

• System must allow filtering of intersections/segments by score (v3)

  code-for-chapel-hill/CrashModel#22 · Filter by author garrisonreid opened on Apr 30, 2019

• System must highlight all intersections/segments color coded by danger score (v3)

  code-for-chapel-hill/CrashModel#21 · Filter by author garrisonreid opened on Apr 30, 2019

• System must compute a danger score from the number of crashes for each intersection and road segment (v3)

  code-for-chapel-hill/CrashModel#20 · Filter by author garrisonreid opened on Apr 30, 2019

• [low priority/easy] Move geo functions from crash_model.js to geo_functions.js

  code-for-chapel-hill/CrashModel#19 · Filter by author bimbashrestha opened on Apr 1, 2019
  1