Configure Police Transparency

Police Transparency can be used to share authoritative information and communicate engagement efforts that build trust with the public and community stakeholders.

In this topic, you will learn how to configure the Police Transparency solution to meet specific needs in your organization.

Organize your data

Police Transparency uses crime, personnel demographics, and use of force data from your authoritative systems to generate maps and apps used in the solution. Before you begin configuring the solution, take some time to organize your source data.

Five foundational data sets (community policing areas, personnel demographics, crimes, use of force, and context of use of force) are required to configure the solution.

Community policing areas

The CommunityPolicingAreas feature layer is used to store community policing areas for an organization as well as the contact information for the officer assigned to each area. Each area must be a polygon and must have a unique name. The data should also include the following fields:

• areaname
• Officer Name
• Officer Phone
• Officer Email
• Officer Shift
• Address
• Comments
• Officer Image URL

Note:

If your organization does not use community policing areas, you may use any alternative polygon layer (for example, contact information for district captains) as long as it has equivalent fields to those listed above.

Personnel demographics

The Police_Personnel table is used to store personnel demographic data for the Law Enforcement Diversity Dashboard. Each record should contain demographic information about each organization employee, but no personally identifying information. The data should also include the following fields:

• Resident of Jurisdiction?
• Gender
• Race
• Ethnicity
• Age
• HireDate
• Years
• Employee_Status
• Employees_Type
• Rank
• Rank_Start_Date

Crimes

The solution requires a minimum of two years (optimally, four years) of reported crime data that is typically sourced from your records management system and is updated on a nightly basis. This data must be in a flattened form and must be accessed from a database table (or table view), CSV file, or spreadsheet. The data must have existing XY coordinates or addresses of sufficient quality to be geocoded. If you are using address data, an address locator is also required. By default, the solution conforms to the Federal Bureau of Investigation's National Incident-Based Reporting System (NIBRS) standard for crime incident reporting in the United States. The data should also have the following minimum required fields:

• Offense ID
• NIBRS Code
• NIBRS Description
• NIBRS Offense Category
• NIBRS Crimes Against Category
• Full Address
• Beat
• District
• Weapon Type Code
• Weapon Description
• Weapon Category
• Location Type Code
• Location Description
• Location Category
• Case Status
• Reporting Officer
• Reported Date
• Reported Date Year
• Reported Date Month
• Reported Date Hour
• Reported Day of Week
• Reported Day of Week Number
• X (only if rendering geometry from coordinates)
• Y (only if rendering geometry from coordinates)

Use of Force

The UseOfForce feature layer is used for storing information about use of force incidents. Demography of persons subjected to force and officers involved are stored in related tables The data required to load into this layer comes should come from an internal affairs, use of force reporting, or other system of record within your organization. The schema of the UseOfForce layer is modeled after the Federal Bureau of Investigation (FBI) standards for the National Use Of Force Collection program. To load data into the UseOfForce layer, you will need to export a spreadsheet from the source system flattened into three tabs. The first tab should contain location and other key information about an incident, the second tab should contain demographic information about subjects of force, and the third tab should contain demographic information about officers involved. All three tabs should contain a unique case number id field that is used to relate the datasets together.

Incident data should have the following minimum required fields:

• Case Number
• Incident Date
• Level of Force Used
• Adjudication
• Incident Context
• Call Type
• Full Address
• City
• State
• Latitude
• Longitude

Subjects of force data should have the following minimum required fields:

• Case Number
• Age
• Race/Ethnicity
• Gender
• Impairment Type
• Weapon Type
• Resistance Type
• Force Type
• Injury Type
• Subject ID

Officer data should have the following minimum required fields:

• Case Number
• Age
• Race/Ethnicity
• Gender
• Assignment
• Years of Service
• Injury Type
• Officer ID

Context of Use of Force

The ContextOfUseOfForce hosted table is used in a chart on the Use of Force page that illustrates the frequency in which force is used when compared to overall police activity. The table contains a single year’s worth of summary totals for Calls For Service, Arrests, Total Use of Force, Serious Injury Force, and Deadly Force incidents.

Review layers

Review the required and optional feature layers used in the Police Transparency solution and compare the feature layers to the source data sets that 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 that 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, follow steps 1 - 4 for the UseOfForce, Police_Personnel, and CommunityPolicingAreas 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

Police Transparency can be used by law enforcement agencies to share crime, use of force, police personnel, and community policing boundary information. In some cases, you may already have this information in ArcGIS Enterprise or another business system.

Review the layers provided with the solution and determine what source data you want to load. Then, load your existing data into the layers provided with the ArcGIS Solution before sharing the maps or apps.

Load police personnel roster data from a spreadsheet

Police Transparency can be used by law enforcement agencies to share data about the diversity of their agency personnel. The Police Transparency solution includes the Law Enforcement Diversity Dashboard that can be used to display this information by race, ethnicity, and gender in relation to community proportions.

To load your agency personnel roster into the Law Enforcement Diversity Dashboard from a spreadsheet, complete the following steps:

1. Sign in to your ArcGIS organization and browse to the Police_Personnel Excel item.
2. From the item page, click Download.
3. Open the spreadsheet and edit it with your information.

   Tip:

   Many fields have existing domain values that are used for filters and charts in the Law Enforcement Diversity Dashboard. If the values in your data are not identical to the values in each domain, you can either change the values in your data to match the values already in each field’s domain list to update the domain list of each field in the Police_Personnel table to reflect the values in your data. Then follow the steps in the Modify apps section to update the Law Enforcement Diversity Dashboard to reflect your values.

4. Verify that the spreadsheet name is Police_Personnel and do not change any field names.
5. Save and close the file.
6. In your ArcGIS organization, browse to the Police_Personnel hosted feature table.
7. From the item page, click Update Data.
8. Follow the steps in the Update data wizard to load your data.

Tip:

For more information about uploading data, see Manage hosted feature layers—Append data to layers.

In subsequent data loads, you will want to delete the existing data in the Police_Personnel hosted feature table before loading updated roster information. Learn how to delete data from a hosted feature layer.

Load community policing area data from a shapefile

To load data from a shapefile into the CommunityPolicingAreas feature layer, complete the following steps:

1. Create a .zip file of your shapefile of your community policing areas.
2. Verify that you are signed in to your ArcGIS organization and browse to the feature layer that you want to populate.
3. From the item page, click Update Data.
4. Follow the steps in the Update data wizard to load your data.

Tip:

For more information about uploading data, see Manage hosted feature layers—Append data to layers.

Load use of force data from a spreadsheet

Police Transparency can be used by law enforcement agencies to share use of force information. The solution includes several charts and dashboards that can be used to display characteristics of use of force incidents by race and ethnicity, neighborhood, subject of the force, and the officer involved. To support these visualizations, the UseOfForce feature layer includes a layer containing information about the incident in which the use of force occurred, as well as a related table containing information about subjects of force in the incident and a table containing information about the officers applying force. The UseOfForce feature layer can be updated by downloading a spreadsheet from the UseOfForce Excel item, adding your organizational data, and then uploading the spreadsheet to the UseOfForce layer.

To load your agency use of force data from a spreadsheet into the UseOfForce feature layer, complete the following steps:

1. Verify that you are signed in to your ArcGIS organization and browse to the UseOfForce Excel item.
2. From the item page, click Download.
3. Open the spreadsheet and edit the Incidents tab with your information.

   Note:

   The UseOfForce spreadsheet contains three tabs—Incidents, Subjects, and Officers. The Incidents tab contains information about the incident in which the use of force occurred, the Subjects tab contains information about the subject of the use of force, and the Officers tab contains information about the officer applying the force. In any use of force incident, multiple subjects and officers can be involved. Each tab contains a Case Number field used to relate data together once loaded into the UseOfForce feature layer.

4. Verify that the spreadsheet name is UseOfForce and do not change any field names.

   Note:

   Review the fields in the UseOfForce feature layer. This layer is comprised of an Incidents layer, an Officers related table, and a Subjects related table—you will need to be familiar with the fields and domain values of all three.

   Tip:

   Many fields have existing domain values that are used in filters and charts on the ArcGIS Enterprise Sites page and in the use of force dashboard. If the values in your data are not identical to the values in each domain, you can either change the values in your data to match the values already in each field’s domain list or follow the steps in the Modify data section to update the domain list of each field in the UseOfForce feature layer to reflect the values in your data. Then, you can follow the steps in the Modify apps section to update the ArcGIS Enterprise Sites charts, Use of Force by Race and Ethnicity, Use of Force by Neighborhood, Use of Force by Officer, and Use of Force by Subject dashboards to reflect your values.

5. Save and close the file.
6. In your ArcGIS organization, browse to the UseOfForce hosted feature layer.
7. From the item page, click Update Data.
8. Follow the steps in the Update data wizard to load your data. In Choose the layer to update, select Incidents, and in Choose the layer from UseOfForce.xlsx that contains the updated dta, select Incidents. Review field matching to ensure that all layer fields have a corresponding match field from the spreadsheet.

   Note:

   Ensure that the data in your Excel workbook already has valid latitude and longitude coordinates. If your data has only addresses and no coordinates, you can geocode it using a local address locator and ArcGIS Pro, or the Publish an Excel file workflow in your ArcGIS organizational portal. Export the resulting layer as a CSV file or Excel spreadsheet and add the Latitude and Longitude values to the UseOfForce worksheet in the Incidents layer.

Tip:

For more information about uploading data, see Manage hosted feature layers—Append data to layers.

9. Repeat these steps to append the data from the Officers and Subjects tabs of your spreadsheet into the Officers and Subjects feature tables.

Note:

If you want to automate the process of appending new Use of Force data from a local Excel workbook into the UseOfForce feature layer, see the Automate data updates section.

Load crime data from a spreadsheet

Police Transparency can be used by law enforcement agencies to share crime data. The solution includes web mapping apps and dashboards that can be used to display current and historical crime conditions in a community. To enable these apps, data can be manually loaded into the Crimes feature layer using a spreadsheet of crime incident records exported from your records management system (RMS).

To load your agency crime data from a spreadsheet into the Crime feature layer, complete the following steps below.

1. Verify that you are signed in to your ArcGIS organization and browse to the Crimes feature layer.
2. From the item page, click Update Data.
3. Follow the steps in the Update data wizard to load your data.

   Tip:

   Ensure that the data in your Excel workbook already has valid latitude and longitude coordinates. If your data has only addresses and no coordinates, you can geocode it using a local address locator and ArcGIS Pro, or the Publish an Excel file workflow in your ArcGIS organizational portal. Export the resulting layer as a CSV file or Excel spreadsheet and add the Latitude and Longitude values to the Crimes worksheet along with the rest of your features.

Tip:

For more information about uploading data, see Manage hosted feature layers—Append data to layers.

Note:

If you want to automate the process of appending crime data from into the Crimes feature layer, see the Automate record import section.

Load Context of Use of Force data from a spreadsheet

To load data into the ContextOfUseOfForce table, complete the following steps below:

1. Verify that you are signed in to your ArcGIS organization and browse to the ContextOfUseOfForce CSV item.
2. From the item page, click Download.
3. Open the CSV file.
4. Click Edit and enter a single year’s worth of summary totals for the following datasets: Calls For Service, Arrests, Total Use of Force, Serious Injury Force, and Deadly Force.
5. Save and close the file.
6. In your ArcGIS organization, browse to the ContextOfUseOfForce feature table.
7. From the item page, click Update Data.
8. Follow the steps in the Update data wizard to load your data.

Tip:

For more information about uploading data, see Manage hosted feature layers—Append data to layers.

Tip:

To modify the data in this table after the initial load, browse to the data section of the ContextOfUseOfForce item, and double-click a value in the table to change it.

Remove outdated personnel records (optional)

At some point, you may want to delete all data in a feature layer to load new information. For example, your organization may update the personnel roster information used in the Law Enforcement Diversity Dashboard semi-annually. To avoid duplicate or incorrect records, the existing records must first be deleted before a current roster can be appended into the solution’s Police Personnel table.

Delete features

To delete features from a hosted feature layer or table, complete the following steps:

1. Sign in to your ArcGIS organization.
2. Go to the Overview tab of the Police_Personnel hosted feature table.

   Note:

   The Police_Personnel hosted feature table must have Editing enabled with the Delete setting turned on. See Settings that control editing access.

3. In the lower right corner, in the URL category, click View.

   The ArcGIS REST Services Directory for this page appears.

4. Click the link of the layer or table from which you want to delete records.
5. In Supported Operations, click Delete Features.

   This option is only available when editing has been enabled on the service

6. In the Where parameter, type the following: ObjectID>0.
7. In the Async parameter, set the value to: TRUE.
8. Click Delete Features.

   This process can take several minutes when many features are present.

Update a layer with a join view

The Police Transparency solution includes a series of feature layer join views that are used to display information in the Use Of Force page and in a series of use of force dashboards. Join views are created using the Join Features analysis tool by joining two sources together based on a matching field. The benefit of the join view is that it remains up to date as the source data changes. However, when new fields are added to the source layers or when field domain values are changed, the join views must be recreated with the same name and URL for the charts and dashboards to continue working properly.

To add a field to a layer and update the join views, complete the following steps:

1. Browse to the join view in your contents.
2. On the item's Overview page, scroll to the URL section. Click the Copy button.
3. Paste the copied URL into Microsoft Notepad or another text editor for reference.

   Note:

   The feature layer’s service name will be used below when re-creating the join. The name can be found after services in the URL structure and may also contain a unique GUID, for example, UseOfForce_Incidents_Subjects_joina45f71a48587425c9b90ee5527cd26d1.

4. Delete the existing join view.
5. Using Map Viewer Classic, add the source hosted feature layer to a new web map (for example, UseOfForce).
6. Click Analysis, Summarize Data, Join Features.
7. Configure the join using the table below.

   Name of join	Target layer	Layer to join to the target layer	Fields to match	Join operation
   UseOfForce_Incidents_Subjects_join	Incidents (UseOfForce)	Subjects (UseOfForce)	agency_case_number=agency_case_number	Join one to many
   UseOfForce_Incidents_Officers_join	Incidents (UseOfForce)	Officers (UseOfForce)	agency_case_number=agency_case_number	Join one to many

   Tip:

   Ensure each new join view uses the names defined in the table above. If you use the same names, the layers in the map and the existing dashboard widgets will not have to be reconfigured. If your join view contained a unique GUID, the new join view must be named with the unique GUID.

8. If necessary, uncheck Use current map extent. Check Create results as hosted feature layer view.
9. Update the web map and app configurations of Use of Force by Race and Ethnicity, Use of Force by Neighborhood, Use of Force by Subject, and Use of Force by Officer Dashboard to account for the new fields or domain values you added.

Automate record import (optional)

Some organizations may want to automate the importing of data from their record systems into the layers in the Police Transparency solution. In particular, users may want to perform daily updates of their Crimes data to ensure that residents have timely access to information.

The Law Enforcement Data Management ArcGIS Pro project includes series of tasks that can be used to configure nightly automated loading of crime data from your authoritative system into the Crimes feature layer 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. From the item page, click Download.
3. Unzip the downloaded folder, and then from the unzipped folder, open the ArcGIS Pro project.
4. In the Catalog pane, expand the Tasks folder.

   Note:

   If you do not see the Catalog pane, from the View tab, in the Windows group, click Catalog Pane.

5. Double-click the Law Enforcement Data Management task item.
6. 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.
Each task group includes a set of steps for using the solution.
7. 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 like Crime Reduction Statistics, and Daily Activity Dashboard. If you implemented data loading and automation for the layers used in the Police Transparency solution then you do not need to do this again if the solutions are using the same feature layer within your ArcGIS organization.

Configure the Police Transparency site

The Police Transparency solution includes an ArcGIS Enterprise Sites site. This site can be configured with your organization's branding and used to share information with the public.

Update with organizational information 

After deploying the Police Transparency solution, the Police Transparencysite requires a few updates to fit your local context.

To update the site with your organizational information, complete the following steps:

1. Verify that you are signed in to your ArcGIS organization and browse to the Police Transparency site.
2. From the item page, click Configure.
3. In the side panel, click Header and, if necessary, expand Appearance.
4. Update the header appearance to with information and graphics applicable to your organization.
5. Expand Social Icons and add URLs for your agency's social media accounts, or disable any social media platforms that you do not want displayed.
6. In the side panel, click the Customize back arrow.
7. Scroll to any additional sections that you want to update, hover over the card, and click the edit pencil that appears in the horizontal toolbar, and then edit the content with information specific to your organization.
8. In the side panel, click Footer.

   A custom footer is provided. In most cases, you will need to update it with your organization's branding, contact information, and social media references.

9. Click the HTML box.

   The HTML window appears.

10. Make the necessary changes and click Apply.
11. Click Save.
12. Click the Save drop-down arrow and click Publish Draft.
13. To edit content on an associated Hub page, follow these steps:
    1. At the top left, click the Police Transparency drop-down arrow and choose Site Home.
    2. To the right of Customize, click the number of associated pages button.
    3. Under Home, click the Hub page that you want to edit.
    4. Scroll through the page to a section that you want to update, click the edit pencil, and edit the content with information specific to your organization.
    5. Click Save.
    6. Click the Save drop-down arrow and click Publish Draft.

    Note:

    To edit another Hub page, click the Police Transparency drop-down arrow and choose Site Home, and then repeat the previous steps.

Remove ArcGIS Hub Premium content

The Police Transparency solution comes with features that require ArcGIS Hub Premium; if you are using ArcGIS Enterprise Sites, you want to remove the features that require ArcGIS Hub Premium. Organizations using this solution with ArcGIS Enterprise Sites should perform the following steps to remove ArcGIS Hub Premium content from their site.

To remove ArcGIS Hub premium content, complete the following steps:

1. In your ArcGIS organization, click the Apps button in the header of the site.
2. From the app launcher, click Hub to open the app, and then click Police Transparency to begin editing the site.
3. Scroll to the Get Involved section on the main site page.
4. Hover over the row and click the delete button in the vertical toolbar, and then click Remove to delete the row card from the site.
5. Click Save.
6. Click the Save drop-down arrow and click Publish Draft.
7. Repeat these steps to remove the Get Involved section from the Community Engagement, Workforce Diversity, Crime Stats, and Use of Forces pages.

   Tip:

   At the top left, click the Police Transparency drop-down arrow and choose Site Home, and then click the number of associated pages button.

8. Under Home, click Community Engagement and scroll to the Scheduled Events section.
9. Hover over the row and click the delete button in the vertical toolbar, and then click Remove to delete the row card from the site.
10. Click Save.
11. Click the Save drop-down arrow and click Publish Draft.

Modify custom use of force charts

Several charts on the Use of Force Hub page make use of custom queries from solution layers that use preexisting values from domain lists. For your data to display properly in these charts, the values in your data must exactly match the values in the field domain list of the field in the feature layer. If your data contains different values, you must modify the custom JSON of the Hub charts to reflect your field values.

To modify the JSON of the custom use of force charts, complete the following steps:

1. In your ArcGIS organization, click the Apps button in the header of the site.
2. From the app launcher, click Sites to open the app, and then click Police Transparency to begin editing the site.
3. To the right of Customize, click the number of associated pages button.
4. Under Home, click Use of Force.
5. Scroll to the Key Use of Force Metrics section, hover over the Serious Injury Use of Force Incidents chart, and click the ddit pencil.
6. In the JSON Chart Definition box, find the following JSON code:

   "where": "forcelevel='Level 3- Serious Injury'"

7. Replace Level 3- Serious Injury with the value in your data that represents incidents involving serious injury.
8. Click Apply.
9. Click Save.
10. Click the Save drop-down arrow and click Publish Draft.
11. Repeat these steps for the Fatal Use Of Force Incidents chart, replacing Deadly Force-Fatality with the value in your data that represents fatal use of force incidents, and then save and publish the draft.

Share items with the public

Several layer views, maps, and apps included in the Police Transparency solution must be shared with everyone so they can be accessed by the public on the Police Transparency site.

To share items with the public, complete the following steps:

1. Verify that you are signed in to your ArcGIS organization and browse to the Police Transparency folder.
2. Next to each of the following items, check the check box:

   Name	Item type
   Community Safety and Police Satisfaction Survey	Feature layer (hosted)
   CommunityPolicingAreas_public	Feature layer (hosted, view)
   Crimes_public	Feature layer (hosted, view)
   Police Interaction Survey_fieldworker	Feature layer (hosted, view)
   UseOfForce	Feature layer (hosted)
   UseOfForce_Incidents_Officers_join	Feature layer (hosted, view)
   UseOfForce_Incidents_Subjects_join	Feature layer (hosted, view)
   ContextOfUseOfForce	Table (hosted)
   Police_Personnel	Table (hosted)
   Crime Summary and Trends	Web Map
   My Community Officer	Web Map
   Public Crime Map	Web Map
   Use of Force By Neighborhood	Web Map
   Use of Force By Officer	Web Map
   Use of Force By Subject	Web Map
   Crime Summary Dashboard	Dashboard
   Crime Summary Mobile Dashboard	Dashboard
   Crime Trends Dashboard	Dashboard
   Law Enforcement Diversity Dashboard	Dashboard
   Law Enforcement Diversity Mobile Dashboard	Dashboard
   Use of Force by Neighborhood	Dashboard
   Use of Force by Officer	Dashboard
   Use of Force by Race and Ethnicity	Dashboard
   Use of Force by Race and Ethnicity Mobile Dashboard	Dashboard
   Use of Force by Subject	Dashboard
   Community Engagement	Hub Page
   Crime Stats	Hub Page
   Use of Force	Hub Page
   Workforce Diversity	Hub Page
   Public Crime Map	Web Mapping Application
   My Community Officer	Instant app
   Community Safety and Police Satisfaction Survey	Form
   Police Interaction Survey	Form
   Police Transparency	Site Application
   Police Transparency	Hub Initiative

3. Click Share.
4. In the Share window, click Everyone (public) and click Save.

   The Warning: Sharing editable layers publicly message appears notifying you that you are sharing editable layers publicly.

5. Click Update.

Modify apps

The Police Transparency solution includes many apps that are used by law enforcement agencies to help residents and stakeholders explore crime conditions, use of force patterns, and departmental diversity. Apps in the Police Transparency solution can be modified to meet the needs of individual organizations. This section covers several app modification workflows organizations commonly require.

Modify dashboards

The Use of Force by Race and Ethnicity and Law Enforcement Diversity Dashboard require an organization to manually enter your jurisdiction’s population percentage values for each race/ethnicity group represented on the dashboards. This information helps to contextualize proportions of force and personnel data relative to the composition of the community.

To update the dashboards with population percentages by race and ethnicity for your jurisdiction, complete the following steps:

1. Obtain information about population percentages by race and ethnicity for your jurisdiction.

   Tip:

   This data is most typically obtained from the U.S. Census Bureau’s Quick Facts web page, where you can type the name of your jurisdiction to get population percentages by race and ethnicity. Consult your planning department for more information.

2. Sign in to your ArcGIS organization.
3. Browse to and click to open the item page of the dashboard you want to edit.
4. Click Edit Dashboard.
5. Find the first indicator element where the language Community Makeup: X% appears and click the configure (gear) button.
6. Click the General options category, then click Edit in the Description section.
7. Switch the default value with the appropriate value for your jurisdiction.
8. Repeat for all indicator elements with the Community Makeup: X% text.
9. Click Save.

Update dashboard charts to reflect new field values

Dashboards in the Police Transparency solution have been preconfigured to use layer fields that are powered by default domain values. If your data does not match the preexisting values, your data may not display or may display as a gray other value in dashboard charts.

To update dashboards to reflect new field values, complete the following workflow:

1. Sign in to your ArcGIS organization.
2. Browse to and click to open the item page of the dashboard you want to edit.
3. Click Edit Dashboard.
4. Review your dashboard and identify all chart elements that require updating.
5. For each chart element that needs an update, click the configure button.
6. If the chart is a pie chart, click the Slices options category, delete the existing values, then click Load Categories. Style the categories with colors appropriate for the dashboard.
7. If the chart is a serial chart, click the Series options category, delete the existing values, then click Load Series. Style the categories with colors appropriate for the dashboard.
8. Click Save.

Update dashboard filters to reflect new field values

The Use of Force by Race and Ethnicity and Law Enforcement Diversity Dashboard both use field values (that are preset by a domain) to filter by specific demographic groups. If the values in your data differ from the domains present in the default fields of the Police_Personnel, UseOfForce-Subjects, and UseOfForce-Officers tables, these dashboards may not properly display. For example, if your data contains coded values for race/ethnicity (A, B, W, I, H, and so on) instead of complete values such as the domain for these fields, you will need to modify the element filters of these dashboards to reflect your values.

To update dashboard elements in Law Enforcement Diversity Dashboard or Use of Force by Race and Ethnicity to use your field values, complete the following steps:

1. Sign in to your ArcGIS organization.
2. Browse to and click to open the item page of the dashboard you want to edit.
3. Click Edit Dashboard.
4. Review your dashboard and identify all chart elements that require updating.
5. For each indicator element that needs an update, click the configure button.
6. In the Value drop-down list of the Filter section, replace the default value with the appropriate value from your data that represents the information conveyed by the element.
7. Click Done.
8. Repeat for all other indicator elements in the dashboard that require updating.
9. Click the Save button.

Change the crime summary dashboard from NIBRS to UCR

Some organizations may want to provide public crime data according to the Federal Bureau of Investigation’s old Uniform Crime Reporting Summary Reporting System (SRS) standards rather than the new National Incident-Based Reporting System (NIBRS). The Crime Summary Dashboard is configured using the NIBRS standard, but can be updated to reflect the older UCR SRS standard if required by an organization.

To update the Crime Summary Dashboard from NIBRS reporting standards to UCR SRS standards, complete the following workflow.

Note:

Before you begin this workflow, ensure that you have valid values populated in the UCR Offense Description and UCR Offense Category fields of the Crimes layer.

1. Sign in to your ArcGIS organization.
2. Browse to your content and click the Crime Summary Dashboard.
3. Click Edit Dashboard.
4. Click the configure button in the upper left corner of the Rich Text element containing the text Crimes Against Persons.
5. In the text box, change the text to Violent Crime, then click Done.
6. In the indicator element immediately below, click the configure button.
7. In the Value section and Filter subsection, change the drop-down selection from NIBRS Crime Against Category to UCR Category, then change the value from Crimes Against Persons to Violent Crime (or the equivalent value in your data).
8. Scroll down to the Reference section and Filter subsection, change the drop-down selection from NIBRS Crime Against Category to UCR Category, then change the value from Crimes Against Persons to Violent Crime (or the equivalent value in your data).
9. Click Done.
10. Click the configure button on the Crimes Against Persons By Year chart element to the right of the last two elements you modified.
11. In the Filter section, change the drop-down selection from NIBRS Crime Against Category to UCR Category, then change the value from Crimes Against Persons to Violent Crime (or the equivalent value in your data).
12. Click Done.
13. Click the configure button on the Crimes Against Persons By Month chart element to the right of the last element you modified.
14. In the Filter section, change the drop-down selection from NIBRS Crime Against Category to UCR Category, then change the value from Crimes Against Persons to Violent Crime (or the equivalent value in your data).
15. Click Done.
16. Repeat steps 4 through 15 for the remaining two rows of elements, replacing Crimes Against Property with Property Crime (or the equivalent value in your data), then replacing Crimes Against Society with Part II crimes (or the equivalent value in your data).
17. Click the Save button.

Change the crime trends dashboard from NIBRS to UCR

Some organizations may want to provide public crime data according to the Federal Bureau of Investigation’s old Uniform Crime Reporting Summary Reporting System (SRS) standards rather than the new National Incident-Based Reporting System (NIBRS). The Crime Trends Dashboard is configured using the NIBRS standard, but can be updated to reflect the older UCR SRS standard if required by an organization.

To update the Crime Trends Dashboard from NIBRS reporting standards to UCR SRS standards, complete the following workflow.

Note:

Before you begin this workflow, ensure that you have valid values populated in the UCR Offense Description and UCR Offense Category fields of the Crimes layer.

1. Sign in to your ArcGIS organization.
2. Browse to your content and click the Crime Summary Dashboard.
3. Click Edit Dashboard.
4. Click the configure button along the right side of the Crime Type filter.
5. In the Category Field, change the drop-down selection from NIBRS Description to UCR Description.
6. Click the Actions options tab.
7. In the Target Field drop-down list for the Crime Hotspots layer, select UCR Description.
8. Click Done.
9. Click the Save button.

Change the public crime map from NIBRS to UCR SRS

Some organizations may want to provide public crime data according to the Federal Bureau of Investigation’s old Uniform Crime Reporting Summary Reporting System (SRS) standards rather than the new National Incident-Based Reporting System (NIBRS). The Public Crime Map app is configured using the NIBRS standard, but can be updated to reflect the older UCR SRS standard if required by an organization.

To update the Public Crime Map app from NIBRS reporting standards to UCR SRS standards, complete the following workflow.

Note:

Before you begin this workflow, ensure that you have valid values populated in the UCR Offense Description and UCR Offense Category fields of the Crimes layer.

1. Sign in to your ArcGIS organization.
2. Browse to your content and click the Public Crime Map Web Mapping app.
3. Click Edit Application.
4. Click the Widget button at the top of the configuration section of Web AppBuilder.
5. Click the Header Control- Set the widgets in this controller button.
6. Click the Configure this widget edit button on the Summary widget.
7. Click the edit button under Display Options for the Crimes layer.
8. Click the Panel tab.
9. In the Layer Options section, change the drop-down selection from NIBRS Description to UCR Description.
10. In the Group Options section, change the drop-down selection from NIBRS Offense Category to UCR Category.
11. Click OK twice to save the reconfigured Summary widget.
12. Click the Configure this widget edit button on the Filter widget.
13. Click the NIBRS Offense Category filter.
14. On the Info tab, change the label of the filter from NIBRS Offense Category to UCR Category.
15. On the Expressions tab, change the drop-down selection from NIBRS Offense Category to UCR Category.
16. Change operator to is any of.
17. Check the Ask for values check box.
18. Click the NIBRS Offense Description filter.
19. On the Info tab, change the label of the filter from NIBRS Offense Description to UCR Description.
20. On the Expressions tab, change the drop-down selection from NIBRS Offense Description to UCR Description.
21. Change operator to is any of.
22. Check the Ask for values check box.
23. Click OK to save the reconfigured Filter widget.
24. Click the Configure this widget edit button on the Report widget.
25. Click the edit button under Actions for the Crimes layer.
26. Change the drop-down selection from NIBRS Description to UCR Description.
27. Click OK twice to save the reconfigured Report widget.
28. Click Save at the bottom of the configuration window of Web AppBuilder.

Modify Police Transparency surveys

To modify any survey in the Police Transparency solution, including the Police Interaction Survey or theCommunity Safety and Policing Satisfaction Survey, complete the following steps:

1. Install ArcGIS Survey123 Connect.
2. Start ArcGIS Survey123 Connect and sign in to your ArcGIS organization.
3. Click to download the survey you want to edit.
4. Click again to open the survey.
5. In the left pane, click Open XLSForm Spreadsheet.
6. In the Microsoft Excel spreadsheet, click the choices tab. This tab comprises all the selectable options for survey questions.
7. Revise the survey to reflect your organizational needs.
8. Save the Microsoft Excel spreadsheet and preview your changes in ArcGIS Survey123 Connect.
9. In ArcGIS Survey123 Connect, click Publish in the left pane to publish your changes.
To view your changes in ArcGIS Survey123 Connect, on the Download Surveys page, click Download to download the updated survey.