ichivite-esristaff

Understanding User Inputs in ArcGIS QuickCapture

Blog Post created by ichivite-esristaff Employee on Oct 6, 2019

Capturing data with ArcGIS QuickCapture boils down to pushing a big fat button. If configured appropriately with device variables, you can also have additional attributes in your GIS feature be added automatically: direction and speed of travel, time-of-capture, horizontal accuracy and many others. That is the basic idea and the most common pattern of use for the app: push a QuickCapture button and the app does the rest.

 

User inputs are an advanced capability that lets field workers manually enter extra information for captured observations, without losing the fluent big button user experience of QuickCapture.

 

QuickCapture supports two different types of user inputs:

 

  • Button User Input: The user input dialog is shown immediately after a button is pushed.  A typical example for a button user input is that where you want to use the dialog for the user to add some extra comments or observations on the feature just captured.
  • Project User Input: The user input dialog is shown when the project is opened, and the value entered is used to attribute subsequently captured features.

 

User inputs can be easily authored from the QuickCapture designer.

 

 

 

Configuring Project User Inputs

 

A Project User Input lets you define a value which will later be used when data is captured from the app. Configuring a Project User Input is a two-step project:

 

  1. Create a project User Input dialog: While in the designer, open the settings pane and scroll down to open the Project User Input category.  Give it a label and other basic properties.
  2. Define when to store the value from your Project User Input: Select a button from your project and open its Data properties. Then apply the project user input to a field of type text.

 

The following animation shows how to create a project user input to let the end-user type her name. Then we select all buttons in the project and use the value entered to populate the police officer attribute.

 

 

When testing your User Input from the QuickCapture mobile, you will notice that if you make your user input required, then you will not be able to start data capture unless you enter a value in the user input.  Once you are capturing data, you can change the user input value at any moment.

 

Project User Inputs configured using QuickCapture designer always apply to fields of type text.

 

Configuring Button User Inputs

 

A Button User Input dialog always opens immediately after a feature has been captured.  You can define a maximum of one Button User Input per button.

 

To configure a Button User Input you need to first select the field on which you want to store the value, and then define the label and other basic properties for your dialog.

 

In the following animation, we select a single button in the project and configure it with a button user input so the end user can enter some comments. The value of the user input is persisted in the Notes attribute.

 

Button User Inputs will always honor the characteristics of the target field. For example, if you configure your Button User Input on top of a field of type text, the User Input will let you enter free text. If your field as a geodatabase domain defined, then your User Input will automatically display a list of values, etc.

 

You can only define one single button user input per button.

Outcomes