Configure Daily Activity Dashboard

Daily Activity Dashboard can be used to understand recent trends and visualize current hot spots to improve daily response efforts.

In this topic, you'll learn how to configure the Daily Activity Dashboard solution to meet specific needs of your organization.

Organize your data

Daily Activity Dashboard uses crime and calls for service data from your authoritative systems to generate maps used in the solution. Before you begin configuring the solution, take some time to organize your source data.

Four foundational data sets (beat, district, crimes, and calls for service) are required to configure the solution. An additional administrative area, division, can optionally be used for organizations with a larger administrative area hierarchy.

Note:

Organizations may use different terminology to describe beat, districts, and division. If your organization utilizes terminology other than beat to describe your smallest unit of administrative area or district to describe this administrative area covered by each police station in the organization, you can update the layer name of the feature layer.

Beat

Beats, or the area that represents the smallest unit of administrative area utilized by your organization, are required to configure the solution. This data must be a polygon, each beat must have a unique name, and, to ensure that preset filters and dashboard actions work properly, this value must match exactly to the value found in the corresponding field in the Crimes and CallsForService layers.

Review layers

Review the required and optional feature layers used in the Daily Activity Dashboard solution and compare the feature layers to the source data sets you previously organized.

To update data, complete the following steps:

  1. Sign in to your ArcGIS organization and browse to the Crimes feature layer item.
  2. Click Data, and then click Fields.
  3. Click a field and review Description, Field Value Type, and Settings.
  4. Compare the Crimes feature layer to the data you organized previously.

    This comparison will determine whether you need to add or modify your source data to work with the feature layers provided in the solution.

  5. After you have completed reviewing the Crimes feature layer, and then follow steps 1-4 for CallsForService, Beat, District, and, optionally, Division feature layers.
Tip:

The closer your source data sets match the feature layer schema provided, the easier it is to configure the solution.

Load data

The Law Enforcement Data Management ArcGIS Pro project includes series of tasks that can be used to load your administrative areas into the Beat, District, and Division feature layers and configure nightly automated loading of crime and calls for service source data from your authoritative system into the Crimes and CallsForService feature layers used by the solution.

To load data complete the following steps:

  1. Sign in to your ArcGIS organization and browse to the Law Enforcement Data Management item.
  2. Open the item page and click Download.
  3. Expand the Tasks folder, and then double-click the Law Enforcement Data Management task group.
  4. In the Tasks pane, expand the Getting to know Law Enforcement Data Management task group to see the collection of tasks.
    Tip:

    Click a group heading or task name to view its description at the bottom of the Tasks pane.

  5. Each task group includes a set of steps for using the solution.
  6. Open each task and follow the steps provided.

    Law Enforcement Data Management is used to load data used in the solution apps.

Note:

The Law Enforcement Data Management ArcGIS Pro project is used in other law enforcement solutions, such as Police Transparency and Daily Activity Dashboard. If you implemented data loading and automation for the layers used in the solution, you do not need to do it again if the solutions are using the same feature layers within your ArcGIS organization.

Configure layers and maps

Before use, the layers and maps in the Daily Activity Dashboard should be configured to meet the unique needs of your organization.

Update preferred time zone

The Law Enforcement Data Management ArcGIS Pro project uses the Update Features With Incident Records tool to load and update crimes and calls for service data. This tool automatically converts date field values data to universal time (UTC) prior to being appended or updated. The conversion is based on the time zone of the machine running the tool. Because of this conversion, the maps and apps will always display date information in the time zone of the machine you are using.

If you are using the crimes and calls for service layers in ArcGIS Pro, you will need to set a preferred time zone on the feature layers to ensure the date field values are displayed in your preferred time zone instead of UTC. Use the Publish a feature service with a preferred time zone technical article to make this update. If the preferred time zone is not added to the feature layer, date values in the layer will display in UTC rather than your preferred time zone when using ArcGIS Pro.

Modify layers and maps

Optionally, the maps and layers in theDaily Activity Dashboard solution can be extended, modified, or optimized to meet the needs of your organization.

Examples of optional modifications include:

  • Update field display names—You can update field display names when terminology used in solution does not match your organizations language. For example, administrative areas are described as beat, district, and division, which may differ from how your organization describes its administrative areas.
  • Update pop-ups—You can update the pop-up display to meet your organizational preferences. For example, if you updated fields in the Crimes and Calls for Service layers, you'll likely want to include that information in your pop-up. While pop-ups can be configured in the web maps of the solution; they are configured by default within the feature layer views (Crimes_dashboard and CallsForService_dashboard). Updating the pop-ups in the feature layer view will make it easier to manage your pop-up configuration across multiple solutions rather than a specific map. Update pop-ups from the Visualization tab or configure within the map.
  • Update symbols—You can update the symbols, including color and size to meet your organizational preferences. While symbols can be configured in the maps of the solution; they are configured by default within the feature layer views (Crimes_dashboard and CallsForService_dashboard). Updating the symbols in the feature layer view will make it easier to manage your pop-up configuration across multiple solutions rather than a specific map. Update symbology from the Visualization tab or configure symbology within the web map.
  • Modify clustering—You can modify or remove clustering from Crimes and Calls for Service in the web maps.
  • Modify basemap—By default, the solution's web map leverages the Color Dodge blend mode with a background color and a heightened contrast style to lighten the basemap and coordinate with the dashboard colors. You can use this blended basemap or use another basemap.
  • Update hot spots—The Crimes and Calls For Service hot spot layers included in the Daily Calls and Daily Crimes maps are configured to display hot spots for the last 365 days using the default settings of the Map Viewer heat map style. If your hot spots do not appear, you must update your heat map style settings or default date filters.

Manage performance

Note:
This workflow is optional and doesn't need to be completed in order to work with the solution.

Some organization have a large volume of Crimes and Calls for Service data and adjustments can be made to enhance dashboard performance. By default, the solution looks at 365 days of data by using a filter on the feature layer view; however, if you notice that your dashboards are not updating as quickly as you would like, consider updating the solution to look at 28 days of data by updating the filter on the crimes_dashboard and callsforservice_dashboard hosted feature layer view.

In general, if you find the map and dashboard are performing slowly after loading a large number of features, rebuild the spatial index of the Crimes and Calls for Service layer.