Back to Top

Configure Police Transparency

In this topic

  1. Organize your data
  2. Load data
  3. Remove outdated personnel records
  4. Update a layer with a join view
  5. Automate record import
  6. Configure the Police Transparency site
  7. Modify apps

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'll learn how to configure the Police Transparency solution to meet specific needs in your organization.

Tip:
As you configure the solution, record the configurations or alterations you make with each version in a change log. This information will be valuable if you upgrade to a new version and need to evaluate the effort required.

Organize your data

Police Transparency uses crime, personnel demographics, administrative areas, 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 review and organize your source data and the feature layers and tables deployed with the solution.

Eight foundational data sets (community policing areas, beats, districts, divisions, personnel demographics, calls for service, crimes, use of force, and context of use of force) are required to configure the Police Transparency 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 must 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.

Beats

The Beat feature layer is used to store the smallest administrative areas for a local law enforcement agency. The data should include the following fields:

  • Beat
  • District
  • Division
  • Agency

Districts

The District feature layer is used to store the administrative areas of each police station at a local law enforcement agency. Each district will have multiple beats, and each division will have multiple districts. The data should include the following field:

  • District

Divisions

The Division feature layer is used to store the highest grouping of administrative areas of a local law enforcement agency. Each division will have multiple districts. In some cases, an agency may not have divisional boundaries. The data should include the following field:

  • Division

Personnel demographics

The Police_Personnel table is used to store personnel demographic data for the Police Personnel Dashboard app. 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

Calls for service

The CallsForService feature layer is used to store calls for service reported to law enforcement. The data should include the following fields:

  • Call ID
  • Call Category
  • Call Type
  • Priority
  • Description
  • Call Source
  • Caller Information
  • Full Address
  • City
  • State
  • Zip
  • Location Description
  • Beat
  • District
  • Division
  • Call Date
  • Call Year
  • Call Month
  • Call Day of Week
  • Call Day of Week Number
  • Call Hour
  • Dispatch Date
  • Enroute Date
  • Arrival Date
  • Clear Date
  • Time to Dispatch
  • Queue Time
  • Travel Time
  • Time on Call
  • Total Response Time
  • First Responding Agency
  • First Responding Unit ID
  • Total Units Responding
  • Disposition
  • Comments
  • Analyst Notes
  • Problem Name
  • Problem Type
  • X (only if rendering geometry from coordinates)
  • Y (only if rendering geometry from coordinates)

Crimes

The solution requires a minimum of two 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 in incidents are stored in related tables. The data required to load into this layer comes from a use-of-force reporting or other internal affairs 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 the Use of Force Summary Dashboard app that illustrates how often force is used in proportion 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.

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 Enterpriseor 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 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 Police Personnel Dashboard app that can be used to display this information by race, ethnicity, and gender.

To load your police personnel roster into the Police Personnel table using a spreadsheet, complete the following steps:

  1. Sign in to your ArcGIS organization and browse to the Police_Personnel Microsoft 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 Police Personnel Dashboard app. 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 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 Police Personnel Dashboard app 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.
    9. 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 CommunityPolicingAreas feature layer.
  3. From the item page, click Update Data.
  4. Follow the steps in the Update data wizard to load your data.
    5. 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 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 Use of Force Summary Dashboard app, Use of Force by Officer dashboard app, and Use of Force by Subject dashboard app 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. For Choose the layer to update, select Incidents, and for Choose the updated data for Incidents from the sheet UseOfForce.xlsx, 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 tab.

    9. 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 or calls for service data from a spreadsheet

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

To load your agency crime or call data from a spreadsheet into the associated Crimes of CallsForService feature layer, complete the following steps:

  1. Verify that you are signed in to your ArcGIS organization and browse to either the Crimes or CallsForService 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.

    4. 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 into the Crimes or CallsForService feature layers, 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:

  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.
    9. 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

Note:
This workflow is optional and does not need to be completed to work with the solution.

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

Delete features

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

  1. Verify that you are signed in to your ArcGIS organization and browse to the Police_Personnel hosted feature table.
  2. From the item page, scroll to the URL item and click View.

    The ArcGIS REST Services Directory for this page appears.

    Note:

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

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

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

  5. In the Where parameter, type ObjectID>0.
  6. In the Async parameter, set the value to True.
  7. 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 on 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. Verify that you are signed in to your ArcGIS organization and browse to the join view.
    Tip:

    All joined views include join the layer name.

  2. From the item page, scroll to the URL item and 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. Click the Settings tab, and click Delete Item.
  5. Click Delete.
  6. At the top of the site, click Content.
  7. Open the recycle bin.
  8. Check the check boxes next to the deleted join feature layers and click Permanently Delete.
  9. Browse to the UseOfForce layer, and on the Overview page, click Create View Layer, then click Joined View Layer.
  10. Select Incidents as your target layer, then click Next.
  11. Select Subjects as your join layer, then click Next.
  12. Configure the join using the following table as a guide:

    Target layerJoin layerTarget fieldJoin fieldJoin operationJoin type

    UseOfForce - Incidents

    UseOfForce - Subjects

    Case Number

    agency_case_number=agency_case_number

    Join one to many

    Left join
  13. Click Next.
  14. In the Title field, enter the name of the original joined view layer from the copied service URL in step 2.
  15. Click Create.
  16. Repeat this process with the Officers table to re-create the UseOfForce_Incidents_Officers_join join view layer, using the following table as a guide:

    Target layerJoin layerTarget fieldJoin fieldJoin operationJoin type

    UseOfForce - Incidents

    UseOfForce - Officers

    Case Number

    agency_case_number=agency_case_number

    Join one to many

    Left join
  17. Update the map and app configurations of Use of Force Summary Dashboard app, Use of Force by Subject dashboard app, and Use of Force by Officer dashboard app to account for the new fields or domain values you added. For example, adding new fields to display in pop-ups or on list elements in dashboards.

Automate record import

Note:
This workflow is optional and does not need to be completed to work with the solution.

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. Verify that you are signed 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.
    7. 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 Transparency site 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 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 Edit 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. On the upper left, click the Police Transparency drop-down arrow and choose Site Home.
    2. In the side panel, click the Customize back arrow.
    3. To the right of Customize, click the number of associated pages button.
    4. Under Home, click the page that you want to edit.
    5. 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.
    6. Click Save.
    7. 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 an event calendar capability that requires ArcGIS Hub Premium. Organizations using this solution with ArcGIS Enterprise Sites should perform the following steps to remove the event calendar from their site.

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

  1. Verify that you are signed in to your ArcGIS organization and click the Apps button 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. On the upper left, click the Police Transparency drop-down arrow and choose Site Home, and then click the number of associated pages button.
  4. Under Home, click Community Engagement and scroll to the Scheduled Events section.
  5. 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.
  6. Click Save.
  7. Click the Save drop-down arrow and click Publish 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:

    NameItem type

    Beat_public

    Feature layer (hosted, view)

    CallsForService_public

    Feature layer (hosted, view)

    Community Safety and Police Satisfaction Survey

    Feature layer (hosted)

    CommunityPolicingAreas_public

    Feature layer (hosted, view)

    Crimes_public

    Feature layer (hosted, view)

    District_public

    Feature layer (hosted, view)

    Division_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)

    Community Calls for Service Explorer

    Web Map

    Community Crime Explorer

    Web Map

    My Community Officer

    Web Map

    Use of Force by Officer

    Web Map

    Use of Force by Subject

    Web Map

    Police Personnel Dashboard

    Dashboard

    Use of Force by Officer

    Dashboard

    Use of Force by Subject

    Dashboard

    Use of Force Summary Dashboard

    Dashboard

    Year-to-date Crime Statistics Dashboard

    Dashboard

    Community Safety and Police Satisfaction Survey

    Form

    Police Interaction Survey

    Form

    Community Engagement

    Hub Page

    Maps & Stats

    Hub Page

    Use of Force

    Hub Page

    Personnel

    Hub Page

    Police Transparency

    Site Application

    My Community Officer

    Instant app

    Community Calls for Service Explorer

    Web Mapping Application

    Community Crime Explorer

    Web Mapping Application

  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.

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 steps:

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

Update dashboard filters to reflect new field values

The Use of Force by Subject dashboard app and Police Personnel Dashboard app 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, the 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 the Police Personnel Dashboard app or the Use of Force by Subject dashboard app to use your field values, complete the following steps:

  1. Verify that you are signed in to your ArcGIS organization and browse to the dashboard that you want to edit.
  2. From the item page, click Edit Dashboard.
  3. Review your dashboard and identify all chart elements that require updating.
  4. For each indicator element that needs an update, click the Configure button.
  5. 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.
  6. Click Done.
  7. Repeat for all other indicator elements in the dashboard that require updating.
  8. Click Save.

Change crime reporting standard 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 modern National Incident-Based Reporting System (NIBRS). If your organization wishes to use UCR SRS standards, apply the following field mappings during data loading:

Field name in Crimes layerCorresponding UCR field

NIBRS Code

UCR Code

NIBRS Description

UCR Description

NIBRS Offense Category

UCR Category (Violence, Property)

NIBRS Crimes Against Category

UCR Part (Part I, Part II)

After UCR values are available in the Crimes layer features, labels and filters will need to be updated to reflect UCR values. Review the following items and update all labels and filters as necessary:

  • Crimes (Feature layer)
  • Crimes_public (Feature layer view)
  • Year-to-date Crime Statistics Dashboard
  • Community Crime Explorer app
  • Community Crime Explorer web map

Modify Police Transparency surveys

To modify any survey in the Police Transparency solution, including the Police Interaction Survey or the Community Safety and Police 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 that you want to edit.
  4. In the Download window, click Download and click OK.
  5. Click the survey name to open the survey.
  6. On the left, from the side toolbar, click the XLSForm button.
  7. At the bottom of the Microsoft Excel spreadsheet, click the choices tab.

    This tab comprises all the selectable options for survey questions.

  8. Revise the survey to reflect your needs.
  9. Save and close the Microsoft Excel spreadsheet and preview your changes in ArcGIS Survey123 Connect.
  10. In ArcGIS Survey123 Connect, in the left toolbar, click Publish to publish your changes.
  11. Click Publish survey to publish your changes, and then click OK.

Feedback on this topic?

In this topic
  1. Organize your data
  2. Load data
  3. Remove outdated personnel records
  4. Update a layer with a join view
  5. Automate record import
  6. Configure the Police Transparency site
  7. Modify apps