Overview of available form items
Table of Contents
Note: When creating forms through Map Editor, you need to create or import the database table on your own (when working through the Mobile Data Collection Portal, this is done automatically for you). When connecting the form field to a field (column) in the database table, you should keep in mind the database table field type (String, Integer, Real) and make sure it fits with the type required for the form item. To help with this step, you’ll find information on the required field (column) type in the database table at the end of each item description.
Standard items
Text – allows input of alphanumeric characters. The single-line option is intended for short input, while the Multiline option supports input of more than one line of text. The field data type should be set to String.
Number – allows input of numeric values. The field data type should be set to Integer or Real.
Date and Time – allows you to select Time and Date together or just Time or just Date. When collecting Date and Time, the collector’s timezone is also submitted; learn more about it here. The field data type should be set to String.
Select list – is used to create a dropdown list. Define the name, and in the Details, define each field value and, optionally, a title or alias that will be visible to the person in the field. You can set one value as a default one. You can also create group values. The field data type should be set to String.
Checkboxes – enables users to have multiple selected values at the same time. The field data type should be set to String.
Radio buttons – similar to the Select list but more suitable for a simpler input with just a few options. When using the Select list, you only see the chosen value, whereas with Radio buttons, all optional values are visible at all times, saving you a tap. The field data type should be set to String.
Signature – allows you to capture an electronic signature on your survey and use it as proof of authenticity and data integrity. The field data type should be set to String.
Hidden field – define a hidden field with a default value (not visible to a user / the collector). The field data type should be set to String.
Media
Photos – allows taking photos in the field or uploading them from the device’s album. Note that you can add multiple photos into one photo field. The field data type should be set to String.
Videos – allows taking videos in the field or uploading them from the device’s album. The limit for video files is 50MB. Note that you can add multiple videos into one photo field. The field data type should be set to String.
Audio recording – allows recording audio in the field (up to 5 minutes long). The audio recorder is built into the MDC app for newer devices (Android 8.1 and higher). This results in a smooth recording experience and no need for switching between apps, even though the switch happens automatically. The field data type should be set to String.
QR/Barcode – allows the recognition of QR codes and barcodes. This way, a collector in the field can input attributes by scanning a code instead of typing values. The field data type should be set to String.
Device and user
These form items are invisible to a data collector in the field.
Username – the collector’s username will be automatically added to every data submission. If the feature is edited, this field will record the username of the user who last edited it. The field data type should be set to String.
Device ID – ID will be automatically assigned to every device and entered by every data submission. The field data type should be set to String.
Device Model – every data submission will automatically enter the device model. The field data type should be set to String.
Device Version – the device version will be automatically entered on every data submission. The field data type should be set to String.
Device Platform – The OS version will be automatically entered on every data submission. The field data type should be set to String.
Location
These form items are invisible to a data collector in the field. The accuracy depends on the device’s GNSS, but you can connect it to an external GNSS to improve it.
Latitude – the latitude of the data collected using GNSS. Column data type should be set to Real.
Longitude – the longitude of the data collected using GNSS. Column data type should be set to Real.
Altitude – the altitude of the data collected using GNSS. If Pinpoint is used, the altitude value is left blank. The column data type should be set to Integer or Real. Note: When adding this field through the Mobile Data Collection Portal, it’s automatically set as an Integer. To use Real, create a new layer with the Altitude field set as Real (or add one to an existing layer), and follow this guide to prepare your data collection project.
Speed – records the speed at which the device is moving. If Pinpoint is used, the speed value is left blank. The column data type should be set to Integer.
GPS Heading – records the direction the device is moving in. If Pinpoint is used, the GNSS heading value is left blank. The column data type should be set to Real.
Compass Heading – records the orientation of the device. The column data type should be set to Real.
Accuracy – records the accuracy of the GNSS location in metres (m). It is set to 0 if the Pinpoint tool is used. The column data type should be set to Real.
Altitude Accuracy – records the altitude accuracy of the GNSS location in metres (m). If Pinpoint is used, the altitude value is left blank. The column data type should be set to Integer or Real.
Time – records the time when the device has submitted data (converted into the local timezone of the viewer). It refers to time information about the location of the device. For example, if GNSS is used to send location data, then it refers to the time of the last received GNSS location. If pinpoint is used, it refers to the time of the last accepted point. The column data type should be set to String, Integer or Real.
Options
Individual settings for each item are added to the project form if the field type supports the option.
Persistent – normally, after submitting data, the field’s value is reset – emptied or set to the default value. Persistent fields retain the last entered value. This way, you can avoid entering often-repeated values.
Required – data submission will be disabled if no data is entered in the required field. A popup warning message appears.
Read-only – the owner of the project controls which forms fields that can be edited (input made by field data collectors) and which are in the form of static non-editable data.
Form Field Descriptions – a feature that provides an additional description of optional length to a particular field.
Default value – defined value will be entered in the specified column by default.
Autofill – a feature that fetches values from existing features on the map depending on your current location; it enters the value already submitted from the closest feature.
Dependencies – Dependent fields allow you to manage sets of dependencies between fields. When a field is dependent, it will only be available for editing and displayed if the state of the parent field satisfies the right rule. If the rule is not satisfied, viewing or editing dependent form fields will not be possible. Learn more about dependencies on form items. You can also create dependencies on value items.
Unique value – specify which form items should be used to collect unique data; if you enable this option, you will not be able to collect duplicate data. Learn how to enable this option, and check out some examples here.
Note: Certain column data types are specified for forms created via Forms Manager in Map Editor and connected to a layer. Make sure to follow the suggestions to avoid any data loss. The table structure (column types and names) is defined automatically if the MDC project is created through the MDC Portal. Learn all about creating data-collecting forms in MDC and Map Editor.