Skip to content

Releases: insight-lane/crash-model

Policy Relevance, Model Upgrades & Deployment

27 Mar 19:41
37de9d9
Compare
Choose a tag to compare

In this release

  • Onboarded our first non US city: Brisbane!
  • Worked towards more streamlined deployment of our public facing visualization and exploring Docker for the same.
  • Enhancements to the visualization.
    • Address search
    • Map filters
    • List of highest risk segments
    • Segment-specific panel with details for the segment selected
  • Incorporating adjacency information into segments
  • Moved our model to be segment based.
  • Documenting our model features in a data dictionary.
  • Our first attempt to understand how segments in a city can be grouped together based on their risk level, and what factors contribute to the formation of those groups.

Tech Upgrade

12 Aug 23:10
c79a562
Compare
Choose a tag to compare

Upgrade to python 3
Continue data standardization work - predictions, volumes, point-based features
Upgrade pipeline process to work for cities without OSM polygons
Better Docker integration with automated image builds
Restructure predictions output to support visualization upgrade in v2.0
Implement improved code testing strategies
Move to using GeoJSON format

Pipeline

07 Jun 00:54
26d8299
Compare
Choose a tag to compare

This release demonstrates running the full pipeline process for any of the demo cities (Boston MA, Cambridge MA or Washington D.C) using the data referenced in the readme. Alternatively it can be run against any other city that has compatible crashes (and optionally concerns) data available, see the readme for additional instructions.