Design view for simultaneous incidents on incident analysis page

[chopchop505]

@andersonad recently added new fields and a better breakdown of the concurrent and in_process incidents. These fields are available at the department, first_due, census tract, and battalion level. Others may be added in the future.

For example, when the call was created, the department had 3 other calls in progress (1 in the same first due). By the time the call was closed, 5 incidents were also active during this time period across the department.

{
   department: {
     overlapping: 5,
     in_progress: 3,
  },
  first_due: {
    overlapping: 2,
    in_progress, 1
  } 
 ....

in_progress: the number of incidents in progress when the given incident was opened
overlapping (aka concurrent): the number of incidents that overlap in any period of time with the given incident

The current incident analysis page only shows concurrent incidents across the department:

We should redesign this view to show both in_progress and overlapping, and by the different facets (department, first_due, census_tract, etc)

[chopchop505]

The most important aspect is calling attention to in_progress calls in the smallest areas of interest

[bingles]

First pass on this one via discussions with @chopchop505.

The thought is to create a "Simultaneous Incidents" module with a couple supporting visualizations along with a modified incidents table (columns TBD). The user can quickly affect the information displayed in the visualizations by using the filter pills which also act as an indicator as to what info they are viewing. Another thought we had was to bump up the size of the tick label on the axis that is currently being filtered on the radar chart (Department is the default).

@andersonad @larskendall Please let me know if you have any concerns, suggestions or recommendations.

Tooltip

[chopchop505]

@garnertb

[chopchop505]

Although I originally suggested the radar chart, on deeper thought, it may not be the best visualization choice. In Progress will always be smaller than overlapping, so the red polygon will always be covering the blue. Secondly often times, you'll have 0 in progress/overlapping so all the dots will be sitting ontop of each other (especially for smaller departments). Possibly a lolipop instead?

I wonder how we can call attention more to when an incident is in progress in the smaller geographic regions (first due/census tract) thus likely having a bigger impact on operations.

Curious to hear your thoughts @andersonad

[larskendall]

Do you think we should put some kind of bar along the bottom of the graph that shows exactly where there's overlap, so that the user doesn't have to eyeball it? It could also potentially increase in thickness depending on the number of incidents that are overlapping.