ArcGIS QuickCapture is Esri's rapid field data collection mobile app. If you are not familiar with QuickCapture, have a look at this short video:
We just updated ArcGIS QuickCapture across all supported platforms. The new build number is 1.7. With this new release, you can build much more powerful field data collection mobile apps, while keeping the end-user experience as simple as the single tap of a button. This video gives summarizes the highlights of this release:
Bigger buttons, of course.
With this update, you can configure your QuickCapture apps with bigger buttons. This is useful when authoring projects for large tablets, with very few or even a single button. Larger buttons help you take full advantage of the available screen real estate on the device, facilitating data capture.
Enhanced Project User Inputs (Define lists from designer)
When configuring your QuickCapture app, you can define a Project User Input. A Project User Input presents a dialog where information can be entered, prior to start capturing data. This information can then be used to automatically populate attributes of collected data. For example, say you are building a Pavement Condition QuickCapture app. You may want to configure a Project User Input for field crews to enter a charge code number or the ID of the field crew. That charge code or field crew ID can then be automatically added as an attribute to every feature collected. Checkhttps://community.esri.com/community/arcgis-quickcapture/blog/2019/10/06/understanding-user-inputs-i... for more details on Project User Inputs.
Up until this release, you could only create free text Project User Inputs. That is, a dialog with either a single line or a multi line text input control. Starting with version 1.7, you can also present a list with well defined values. Using lists makes sense when you want to limit entries to a well known collection of choices. It is easier for users to pick an option than having to type.
The animation below shows you can now create a Project User Input and define a list of values for it.
Once you have your project input dialog defined, just as before, you can choose which buttons will make use of that value.
Enhanced Project User Inputs (Remember previous entries)
To facilitate quick data entry from end users, the QuickCapture mobile app now remembers previous Project User Input entries. In the animation on the side, for example, the Police Officer Reporter app presents a dialog for end users to enter the ID of the person that will collect data. Note that the dialog presents two options in a list right below the text input control. The end user can either enter a new ID, or tap on any of the previously entered IDs.
The QuickCapture mobile app will list the three last entries. The idea listing previous entries is to accelerate data capture and reduce errors when entering this information.
QuickCapture buttons can be logically organized in groups. Groups help end users navigate across QuickCapture apps that include many buttons.
By default, groups can be collapsed and expanded by end users.With this update, the QuickCapture app author can decide to hide the handle to collapse and expand a group. This is useful when you want to make sure a set of buttons will always be visible to users. You can control the group properties from QuickCapture designer.
Link buttons (launching any URL)
Link buttons allow you to open other mobile or web apps right from within ArcGIS QuickCapture. For example, you may want to configure a button to open a live dashboard in a web browser, a PDF file or launch a Survey123 smart form. With link buttons you can convert your QuickCapture project into a launchpad for other applications.
The animation below shows how you can add a new link button into a QuickCapture app, to launch a website.
You can include dynamic content in your target URL. For example, you may want to add custom URL parameters to center a Web AppBuilder application at the user's location, or pass a filter into an ArcGIS Dashboard. For more information about URL parameters in ArcGIS Dashboards and Web AppBuilder, check the following links:
In the animation below, we are passing the current latitude and longitude of the user when the link button is pushed. Note that dynamic content in the URL can be populated from device variables as well as from the Project User Input.
You can really launch any URL from a link button. This includes URLs to launch mobile apps. For example, using app link syntax you can launch Survey123, Tracker, Collector, Navigator and even third party apps. Here are some links to help you better understand how to build URLs to launch other apps:
If you want to launch a Survey123 smart form from QuickCapture, you do not need to figure out how to build the custom URL link yourself. We have added a streamlined user experience so you can more easily launch Survey123 forms and pass parameters to them.
You can select a survey and what dynamic data you want to pass into it.
Once you configure a link button in this manner, Survey123 will be automatically invoked when you press the QuickCapture button.
With link buttons, you can now model much more sophisticated data collection workflows. You can for example configure a few buttons to capture quick field observations and a button to launch Survey123 to do more involved reporting.
More device variables
Device variables in QuickCapture allow you to automatically populate attributes in the GIS features you collect. Device variables let you capture for example the exact time when a button is pushed, the speed and direction of travel, or the horizontal accuracy of your GPS. The complete list of device variables is available in the Configure a project—ArcGIS QuickCapture | Documentation help topic. In this release, we are adding the following new variables:
Photo: Lat, Lon, Heading
Travel: Cardinal direction
Location: DMS, DDM, USNG, MGRS
Device Info: App Version and Device Operating System
Length and Area
Starting with version 1.7 of QuickCapture, all photos taken from the mobile app will include EXIF metadata.
In the UC session: ArcGIS QuickCapture: An Introductionand What's New we briefly mentioned the integration between QuickCapture and Site Scan for ArcGIS - Flight Planning. The purpose of this blog is to bring you to speed with this, and tell you how you can start testing.
First of all, a bit of background on Site Scan for ArcGIS. This Esri app is used to allow drone pilots to easily collect accurate, high-resolution maps, and 3D models. It helps at the planning stage by providing access to basemaps, flight plans, overlays, and previously captured orthomosaics, and offers a variety of flight modes tailored to the type of site being scanned. Once planning is complete, the app is able to automatically conduct aircraft checks and then execute the flight. Finally, captured imagery is wirelessly transferred from the drone to an iPad, ready for upload to Site Scan Manager for processing in the cloud.
Note that the Site Scan for ArcGIS App will only run on iOS tablets and there are two versions available:
To find out more (as well as a list of supported drone models), please see the following Q and A.
The integration between ArcGIS QuickCapture and Site Scan for ArcGIS is pretty simple. The Site Scan app provides a position source to QuickCapture, meaning that instead of using the GPS of the phone, QuickCapture uses the location of the drone. The intended workflow is that operators use two tablets; one running Site Scan; and the other running QuickCapture. Site Scan is used to guide the drone (and provide a video output) and QuickCapture is used to capture records and upload them to ArcGIS.
This offers support for a number of interesting workflows. For example, you could:
Tap a button in QuickCapture as the drone flys over a building to record its location and status (e.g. damaged, partially damaged, etc)
Use the drone to fly the perimeter of an oil spill, with QuickCapture capturing polygons to record changing extents.
Record a polyline representing the flight path to illustrate which areas have been searched.
The benefit of such workflows is that information coming from the drone can be pushed straight into ArcGIS, without waiting for the drone to land. Web maps and dashboards can, therefore, be fed with near real-time spatial information.
If you don't have a drone to test, don't worry. Both versions of the Site Scan app offer a drone simulation option.
The workflow is designed for both apps to be run on different devices on the same network (so they can communicate with each other). The Site Scan app doesn't work in background mode, so you can't reliably run both apps on the same device unless you use the using multitasking feature on iPad (https://support.apple.com/en-us/HT207582). The QuickCapture app can run over the SiteScan app and you can control the drone and record the data at the same time. However: We don't recommend that one person fly the drone and simultaneously use QuickCapture for safety reasons.
To get started, some configuration of both Site Scan and QuickCapture is required:
So many questions came today through UC Live about QuickCapture that we through we would share the most common questions, and the answers of course! We will be adding more content throughout the week in here.
Will I be able to watch the QuickCapture Tech Session once the UC is over? Most sessions will be available for registered attendees until September and then most sessions will be shared publicly. There is no guarantee that this particular QuickCapture session will be shared. Use the session feedback survey or the Survey123 daily survey to request that this particular session is shared.
Can ArcGIS QuickCapture work while disconnected from the network? Yes!. In short: Once a QuickCapture project has been downloaded into your device, you can use it while offline. All captured data will remain in your device and once you get back online again, it will be sent to ArcGIS. There is nothing special you need to do to get this going, other than simply downloading your project into your device. You can optionally configure your QuickCapture project with offline maps. Check https://community.esri.com/community/arcgis-quickcapture/blog/2020/04/14/configuring-a-map-in-your-a... for details.
For ArcGIS QuickCapture to work, your must configure your device to allow QuickCapture to access your location.
Does ArcGIS QuickCapture work with an ArcGIS Enterprise portal? Yes, as long as the version of your portal is 10.7.1 or newer. Your data can configure it against a multi-user enterprise geodatabase or the ArcGIS Data Store.
Can I use non-hosted feature layers with QuickCapture? Yes, you can target a layer from a multi-user geodatabase with ArcGIS QuickCapture. However, you must make sure the feature layer resides in an ArcGIS Server instance that is federated with your portal.
Can I capture lines and polygons? Yes. And you can capture multiple lines and polygons as the same time too.
When I capture a polygon, how is the polygon closed? The polygon starts when you activate the button. As long as the button flashes, we capture vertices. When the button is tapped again, then the last vertex is used to close the polygon.
Can I have QuickCapture populate multiple attributes? Yes. When you configure buttons in QuickCapture designer, you can decide what exact values should go into each attribute.
If I have multiple people capturing data with QuickCapture, how can I tell who created which feature? You will use editor tracking for this, which is enabled by default. When someone creates a feature, by default the Creator field is automatically populated with the username of the person that submitted the record.
Does QuickCapture work with external GNSS receivers? Yes. You can choose to connect your QuickCapture app to an external GNSS receiver to improve the location accuracy of your data and associate location quality GNSS metadata with your records. The list of supported GNSS receivers is available at Use a high-accuracy receiver—QuickCapture | Documentation If the particular receiver you want to use is not supported yet, feel free to propose support for it throughArcGIS Ideas.
Can I configure QuickCapture to collect information about horizontal accuracy? Yes. You can in fact configure it to capture horizontal and vertical accuracy as well as the name of your external GNSS receiver and many other GNSS metadata. For details, check the Configure a project—ArcGIS QuickCapture | Documentation help topic.
What type of ArcGIS account I need to use ArcGIS QuickCapture? It depends. If you want to create new QuickCapture projects, you will need a Creator (or GIS Professional) user type with privileges to create new content. If you simply want to use the mobile app to collect data, you will need a Field Worker (or Creator, or GIS Professional) user type with privileges to add records into feature layers. Alternatively, the mobile app can also be used with an Editor user type, as long as you buy an add-on license for the QuickCapture mobile app.
Please note that Free ArcGIS Public Accounts are not supported with ArcGIS QuickCapture.
Can I use ArcGIS QuickCapture without an ArcGIS account? Yes, as long as you share your QuickCapture project publicly. For example, to support the Esri Run/Walk event this year, we created a public QuickCapture project so anyone can download the app and map their routes. To learn more, visit: Esri UC Virtual Run/Walk 2020
Can I capture a point observation while a line button is active? Yes. You can in fact capture multiple lines at the same time and while they are active, you can capture additional points. This is known as nested field data capture. Say for example you want to map the condition of pedestrian trails within a park as well as park furniture. You can activate the Trail in Good Condition button to capture a line as you walk, and capture benches and other park furniture as you go.
Is it possible for an end-user to create new buttons on the fly? No. Only the author of the QuickCapture project can create and organize data capture buttons. If you want to accommodate your project to the possibility of new feature category types, I would consider adding a new button for a generic 'Other' category. You can use a User Input to let end users type some free text to describe the new category. You can later look at entries in the category 'Other' and decide if more buttons should be added to the project.
Can multiple feature layers be added to a QuickCapture project? Yes. You can combine layers of different geometry types for example. You can also have a mix of layers coming from ArcGIS Online and Enterprise if you like. You can also build multiple QuickCapture projects on top of a single feature layer, and even build Survey123 and Collector projects against the same layers you are using with QuickCapture.
I am a University professor and want to cover field data collection tools. Should I teach QuickCapture, Survey123 or Collector? I would say that an important lesson for your students is to learn that not one single tool is going to serve all possible field data collection workflows. The three apps you mention are all about capturing georeferenced data in the field: they all let you capture points, lines and polygons; they all can be combined with external GNSS receivers, they all let you capture photos, etc. Now, the way they let you capture data is radically different. Choosing the right user experience to meet the way field users work is critical for success.
QuickCapture is ideal for rapid and at-speed data collection workflows. It delivers a minimalist user experience where end users can capture observations with minimum distraction and with minimum training. Think aerial patrols, quick reporting of issues and violations, at-speed road asset inventories, etc.
Survey123 delivers a form-centric approach to data capture. This is for use cases where you need people to spend a bit more time completing a form to capture multiple aspects of something. Think routine asset inspections, formal damage assessments, documenting code violations, etc. If people are used to do their work completing a paper form... chances are you in front of a candidate for Survey123.
Collector is great when you want the data capture experience driven from a map. This is the way to go when working with multiple GIS layers is needed to provide context to your own editing workflows, or where you want to map assets across multiple layers of a map.
In practice, you will find some workflows where any of the options above could do the job. There are other use cases where one app will be the a best fit. Choosing wisely between the different options often comes after full understanding of the pros and cons of each in relation to your specific workflow. Your seasoned students will be able to make the right call with experience. Finally, in some cases it makes sense to combine apps as well.
Can I use QuickCapture to update existing features? No. With QuickCapture you can only submit new records. Survey123 and Collector would be a better fit.
Can I have QuickCapture add a related record to an existing feature? In my scenario, I want to use QuickCapture for a quick inspection and have that inspection record (Pass/Failed) be associated with an asset. You could automatically add the inspection Pass/Fail information as a related record to the asset closest to the location where the inspection was done. This can be done with webhooks as described here: https://community.esri.com/community/arcgis-quickcapture/blog/2020/06/04/data-enrichment-with-arcgis...
User in field has a need to collect 4 to 5 attributes such as 1. missing structure in map, 2. storm MH, 3. 7 hole cover. How many buttons would i need for him to collect this correctly if the next set is 1.missing structure in field, Storm CB MH, 3. vein grate cover? What is the workflow? You should be using Survey123.
Will I lose data I already collected when updating the app? No.
Ever wondered if you could simulate your own location when using the QuickCapture mobile app? It is possible with version 1.6 or newer. Best of all, you can even play a simulation that makes you move around. This can be quite handy for proof of concept demonstrations and for testing purposes. Here is how you do it:
Use a File Location Provider to simulate locations in QuickCapture
As you may already know, the QuickCapture app can be configured with a custom location provider. This is typically used to connect QuickCapture to external GNSS receivers via Bluetooth or a network connection. These connections feed the app with NMEA messages, carrying location information from the GNSS receiver.
You can also configure a location provider from a file, which is exactly what you need to do to simulate locations in QuickCapture. The file format QuickCapture expects is a NMEA log file. Most GNSS receivers can export NMEA logs, so if you get out in the field and want to replay your locations in QuickCapture, you can easily use those files as a location provider. If you do not have a GNSS receiver, there are a handful of utilities that you can use to create a NMEA file.
How to create a custom NMEA file using nmeagen.org
One particular tool I like to use to create NMEA files is https://nmeagen.org/. Here is a video showing how easy it is:
If you plan to run QuickCapture on Windows or macOS, keep your file in a known folder so you can browse to it in the field app. If you plan to use an Android or iOS mobile device, then you need to copy your file onto the device.
In iOS, the easiest way to transfer the NMEA file is via e-mail, as an attachment:
Add your NMEA file to an email as an attachment and send it to yourself.
In your email client, select the attachment file and swipe up
Select Save to Files and move the file to the QuickCapture directory.
The animation on the right side shows the steps. You simply need to use the operating system 'Save to Files' option and select as the destination the QuickCapture folder in your device.
Alternatively, you can also connect your iOS device to your laptop and use iTunes as shown in the animation below:
We just updated the ArcGIS QuickCapture mobile app across all supported platforms and refreshed the QuickCapture website and designer. Here is what is new:
ArcGIS QuickCapture mobile app
Share QuickCapture projects from your own device
Starting with this release, you can share your QuickCapture projects with colleagues, right from your device. We added a couple of new handy options so you can quickly share a link to a project you already have, or display a QR code for others to scan.
You can access this new feature from the project details dialog. Note that at the top there is a menu button which will let you obtain the link or QR code.
If you choose to copy the link, you can share it by email, SMS, iOS AirDrop or through other apps installed in your device... think WhatsApp, WeChat, etc.
Whoever is presented with your QR Code or link, will need to be authorized the project you are sharing. This is not about bypassing the ArcGIS security model: this is about making it easier for you to share projects you have already downloaded with people around you, when appropriate.
Note for Android users
In accordance with security requirements by Google for applications that target Android 10, QuickCapture now stores downloaded projects and unsent records in a new location. Up until this release, all application data was stored in Local Storage>ArcGIS>ArcGIS QuickCapture. The new location is Local Storage>Android>data>com.esri.arcgisquickcapture>files>ArcGIS> ArcGIS QuickCapture. Because of this change, you will need to download your QuickCapture projects again. Additionally, you will want to send any records left in your device before installing this release.
All Android users: Before upgrading ArcGIS QuickCapture to version 1.6, it is strongly recommended that you send all records on your device.
We are aware that this is an inconvenience to you, but it is a change that if needed for compatibility with Android 10. Also, note that subsequent upgrades of the QuickCapture app will not require you to send records before the upgrade.
ArcGIS QuickCapture in the Microsoft Store
QuickCapture's support for Windows has been present since its first release. The Windows installer can be downloaded from our resources page. With this release, you can also install the QuickCapture mobile app directly from the Microsoft Store. We know this is important to some of you, so we are pleased to announce it!
Simulate locations in the QuickCapture mobile app
This one may not be of interest to everybody, but if you ever need to simulate locations in the mobile app, now you can! Since QuickCapture is about field data collection while on the move, we wanted to provide options for you to simulate not just a fixed location but also a track. Essentially, now you can setup a file location provider in the mobile app and feed it with a NMEA file. NMEA files can be easily generated. Once your file location provider is set, you can easily test and demo the QuickCapture mobile app as if you were outside, while sitting on your desk. To learn more about this, check our Simulating Locations in ArcGIS QuickCapture mobile app blog post.
QuickCapture designer enhancements
ArcGIS QuickCapture designer lets you create and manage QuickCapture projects, right from your web browser. In this update, we are adding a handful of productivity enhancements as well as new features for you to better control the data capture experience in the QuickCapture mobile app. Here are the highlights:
Support for shared update groups in QuickCapture designer
ArcGIS shared update groups are designed to allow members of the group to make changes to items in it. Say for example John, Karissa and Anna belong to an ArcGIS group configured with shared update capabilities. If John shares an ArcGIS QuickCapture project with that group, then Anna and Karissa will be able make changes in that project. For example: change the description, thumbnail, map, device variables, buttons and layout of the project.
Updating sharing, changing ownership, or deleting the project are actions that only the owner of the project or a user with administrative privileges can do. Support for shared update groups brings more flexibility to the management and design of QuickCapture projects. To learn more about shared update groups, check Create groups—ArcGIS Online Help | Documentation
Disable location editing
While QuickCapture uses the location of your device when you capture a point observation, it is possible for end users to make adjustments right after having pushed the button. For example, if you are documenting a violation of right of way across a power line, you may want to adjust the location of the observation to center it in its actual location, rather than yours. This is a very handy feature, but in some cases you do not want field users to alter the location of events captured. Now you can optionally disable location editing from QuickCapture designer as shown in the screenshot below.
Custom template gallery
We introduced the concept of QuickCapture templates in our previous update. QuickCapture templates are ready to use QuickCapture projects which you can use to kick-start your own projects. We have created a small number of templates, but we recognize that many of you would like to create your own and share them within your organization. In this way, you can create relevant templates to your workflows and help standardize field data collection projects within your organization.
With this update, you can configure the QuickCapture template gallery to feed from a group in your own ArcGIS organization. Just like you can define a custom group to set the basemaps in your org, you can also set a group to define your own QuickCapture templates. Like other ArcGIS organizational settings, this property can only be updated by a user with administrative privileges.
As shown in the screenshot below, you can click on your profile to bring the Administrator Settings dialog. Within that dialog you can set the template group and decide if the Esri templates should be shown to users of your organization or not.
This release includes some additional enhancements and fixes. For details, check out What's New help topic, which also will help you review highlights for previous versions.
We hope all these new features and enhancements are of your interest. We are now heads down working in our next update, which is planned for early October. We want to bring more exciting new features for you!
The whole idea with ArcGIS QuickCapture is to simplify as much as possible the field data collection experience. Now, simplicity for end users, is not in conflict with being able to generate rich GIS data. I assume you are already familiar with ArcGIS QuickCapture's device variables. Device variables allow you to automatically calculate a good number of GIS attributes such as direction of travel, fix time, username, speed, horizontal accuracy and many others. Device variables are a great way to enrich the GIS attributes of field observations made with the QuickCapture mobile app.
Integromat is commonly used to automate notifications when data from QuickCapture is captured. For example, say you want an SMS to be sent to a field coordinator when a high priority issue is reported through the QuickCapture mobile app. That is about one of the most common reasons why people use Integromat. As I said earlier, our intent in this article is to explore data enrichment with Integromat. This is also a very powerful use! What if you could automatically populate GIS attributes to field observations from QuickCapture? Say you want to calculate the closest address to a record submitted, or store the current weather conditions at the location where an incident is reported... What if you want to automatically associate a parcel identifier with data submitted from QuickCapture? All of this can be done. Automatically, and without much effort.
Example 1: Reverse Geocoding
Lets start with a simple example to warm up: A new record is submitted from the QuickCapture mobile app and the closest address to that location is automatically found and stored as a GIS attribute. Something like this:
To achieve the above an Integromat scenario can be put together so every time a record is submitted, a call to the Esri World Geocoding service is made. The output from the reverse geocoding service call is used to update the new record with the address. A step by step guide is included in this 12 minute video. This recording should give you enough information for you to build scenarios like this on your own:
When using the Esri World Geocoding service, keep in mind you should pass forStorage=true as a parameter in your reverse geocode call if you plan to store the output as an attribute in your feature. Alternatively, you can use a similar technique to use your own locator service from ArcGIS Enterprise. When using your own locator service, you do not have to worry about ArcGIS Online credit consumption or including the forStorage=true parameter.
Custom locator services can also be used to find the closest asset to a location. In this case, you may not be interested in getting an address, but just the identifier of the closest asset to a location. This can be useful, for example, when using QuickCapture to report the condition of an asset. The user taps the button when close enough to the asset and keeps moving; your Integromat scenario will do the rest: associate the condition to the closest asset.
Example 2: Point in Polygon query
You can also enrich field observations using a point in polygon query. Say for example you have a parcel layer and you want to know in which parcel a particular observation was made. As long as the observation was made inside the parcel, a point in polygon query will do the job for you.
You will note that in the documentation for the query operation, the geometry input is a json object, but you can also pass, for points an x,y value. Not officially documented, but it works!
A quick important reminders:
Always use https
Your feature layer URL must specify the layer index too. The end of it will look something like https://...FeatureServer/0/ Where /0/ is the index of your layer in the feature service.
It is important to pass the inSR parameter as 4326, to ensure that the query will work regardless of the spatial reference of your target polygon layer.
For the outFields parameter, indicate the exact attributes you want to back from your query. Do not be lazy requesting all the attributes as this will increase the network traffic unnecessarily and will complicate your life when authoring the scenario in Integromat.
Once you have the values you want from the intersecting polygon, you will use the Integromat http module to update your feature attributes. If you have watched the reverse geocoding video above, this should be no secret to you.
Example 3: Weather forecast
Using the Integromat Weather app, you can also enrich incoming QuickCapture records with a weather forecast. The Weather app takes an an input the XY coordinates of the location you are interested in and can report a weather forecast for the following day or days.
Example 4: ArcGIS Geoprocessing Services
If you are into ArcGIS geoprocessing services, you can also use the HTTP module in Integromat to pass parameters and run your own gp services. The great thing about gp services is that they provide great flexibility to do more sophisticated analysis on the QuickCapture record location. In the screenshot below, for example, the HTTP module invokes a service that runs a valve isolation trace against a Utility Network dataset. The output, again, is used to enrich a QuickCapture observation.
When working with Geoprocessing services in this way, it is important to execute the tasks synchronously. The ouptuts from a gp service are processed similarly to how outputs are parsed from the Esri Geocoding service.
QuickCapture 1.5 is now available! You can download the latest update into your mobile device and enjoy many new enhancements in the QuickCapture website too! Lets have a quick look at the highlights of this release:
Workflow automation with Integromat
Capturing data quickly is not enough; being able to get that data to people who need it, where they need it, is what makes the real difference. For this reason, we are introducing support for Integromat in QuickCapture. Integromat is a powerful workflow automation solution, allowing you to connect many apps and services together.
With Integromat, you can easily automate tasks when data from QuickCapture is sent. Automatically send SMS or email notifications, copy your data into third party databases, spreadsheets, etc. The screenshot below, shows an Integromat scenario configured to automatically send an email notification every time a vehicle accident event is reported from the QuickCapture mobile app.
While email and SMS notifications are common tasks you will want to automate, you can do much more:
When a new incident is reported, immediately send an SMS to the division manager.
Create an ArcGIS Workforce assignment when a new service request is submitted.
Use AI algorithms to classify and label photos submitted.
Automatically assign the appropriate asset ID to condition assessments sent.
To learn more about ArcGIS QuickCapture and Integromat, check this 4 minute video tutorial:
Support for Integromat is possible because QuickCapture now can work with webhooks. If you want to create webhooks to target your own custom web services, Google Cloud functions or some other workflow automation providers, you can now do it from the QuickCapture designer. Simply go to the Project Settings panel and scroll down until you find the Webhooks section.
Enhanced App Links
It is not news that you can use a link to launch the QuickCapture mobile app. It is not news either that your link can open any project you want, have QuickCapture target automatically your enterprise portal and even pass a value to a Project User Input. What is new, is that now you can use app link syntax (sometimes also referred to as universal links), rather than through a deep link (custom url scheme).
Why is this important? Well, it is important because app links are more iOS and Android friendly, allowing you to launch your link from virtually any application in your device. Through the new app link syntax, for example, you can now launch QuickCapture from other ArcGIS apps, such as as ArcGIS Indoors, Survey123, Collector, Workforce, Explorer, etc. You can also more safely launch QuickCapture from e-mail clients and even from your own custom mobile apps. The deep link syntax will continue to work as usual. In fact, in Windows deep links are the only supported syntax.
This is what an app link to open a QuickCapture project looks like:
There are great new features in the QuickCapture website that will make managing and designing your QuickCapture projects much easier. Lets have a quick tour of the most important:
A new panel on the left side of the QuickCapture designer will now assist you during the design process. Sharing errors, inconsistencies, missing properties, etc. This new panel will help you follow best practices and fix problems in your project in a heartbeat.
Starting with this update you can also now control the size of the photos to be submitted from your QuickCapture project. Choose to leave photos at full resolution, or reduce their size to facilitate working in low-bandwidth environments:
In our last release we added a ‘Save as’ option to duplicate existing projects easily. Some of you suggested we should add a choice to duplicate the project layers as well, so now you have it!
This update introduces a new template gallery; use it for inspiration or to quick-start your own projects. The gallery features a small collection of templates for now, but we will be adding more in the future. Very soon you will be able to create your own template gallery, so you can help people in your organization get started with templates that are relevant to their own work.
Other work worth highlighting
There are a handful other new features and enhancements that I want to highlight:
The QuickCapture mobile app now supports PKI authentication.
Users of the mobile app can now change the distance units (US standard vs metric)
The source code of the QuickCapture mobile app for this release has been made available as an AppStudio enterprise template.
We are now deep into 1.6 development, which we plan to make available in July 2020. Our development agenda is loaded with user-driven requests. Thanks to all of you who share with us your work and ideas. You are a constant source of inspiration. Your ideas and feedback are shaping this product.
On April 22, as part of the Esri Transportation GIS Webinar Series, we aired a live Data Collection at Speed with ArcGIS QuickCapture Webinar. In this article you will find a recording of the event as well as a summary of many common questions we received.
The video recording is one hour in length and it has the following sections:
Introduction to Field Data Collection with ArcGIS by Terry Bills
Minute 20:54: Using ArcGIS QuickCapture at the Michigan DOT, by James Hainstock
Minute 28:50: How to create your own QuickCapture projects and other things you should know, by Ismael Chivite
Minute 39: Live Q&A
We did address many questions during the event, but there were many others we could not address live, so here is a more complete Q&A for you:
What are the most common workflows for ArcGIS QuickCapture? QuickCapture is specifically designed to support at-speed and rapid GIS field data collection workflows. Think of situations where field users need minimal distraction to capture geo-referenced field observations: aerial surveys, pass/fail inspections, ROW patrols, quick hazard reporting, etc. The purpose of QuickCapture is to provide the simplest and quickest experience possible for people to capture observations. Tap on the screen, and move on!
What is the difference between QuickCapture and other data collection apps such as Survey123 and Collector? QuickCapture, Survey123 and Collector are all built on top of the ArcGIS platform and as such, leverage the same security model against ArcGIS Online and Enterprise. They also all work on top of ArcGIS feature layers, allow you to capture point, line and polygon geometries, work online and offline and work well with high accuracy GNSS receivers. That's all they have in common but the big differentiator is the user experience they provide to the end user.
Buttons: QuickCapture lets you capture field observations quickly with the push of a button.
Forms: Survey123 lets you capture data through a smart form.
Maps: Collector lets you capture data through a map.
Generally speaking, you will want to carefully look at the workflow at hand and explore which user experience is best for your users. There are many workflows where your decision is not going to make a difference, because any of the three apps could do the job. There are other situations where selecting one app versus the other will make the difference between success or failure.
In the seminar, we described for example an interesting scenario where QuickCapture was selected for snowplow drivers to easily report hazards while driving. QuickCapture is the right choice because it can be used hands-free, so it will not distract drivers. QuickCapture is plenty for the task, because we simply want to add a point in the map highlighting a hazard of some type.
Now, for the maintenance crews that need to follow up on reported hazards, Survey123 was selected. A form is used to report all the work done because that is a more involved process: Maintenance crews need to describe the work done, take photos, document the time spent and materials used, etc. Survey123 is the right tool for that because a from provides the most natural and efficient user experience.
The great thing is, that since QuickCapture and Survey123 all work against ArcGIS feature layers, maintenance crews can work and update the existing hazard GIS features submitted from QuickCapture.
There are other workflows where Collector is a good fit. For example, for field crews who need to map assets along the road, a map-centric user experience is ideal, because it allows field users to see different layers of information in a map and even add new records into the map.
The above is not a comprehensive answer, but highlights the fundamental difference between the apps, which is the user experience. At Esri, we are building different user experiences for field data capture because we understand that different people and different workflows can require different approaches to data capture. As you gain familiarity with each of the apps, you will naturally learn how to pick the best for the task at hand. You will also learn that in some cases, any of the apps will do the job great.
How does QuickCapture integrate with the rest of ArcGIS? QuickCapture is built on ArcGIS so you can easily leverage other ArcGIS apps with data captured from QuickCapture. For example, you can:
Build a live ArcGIS dashboard on top of the feature layers where QuickCapture stores data.
Perform QA/QC workflows on QuickCapture data using ArcGIS Web AppBuilder or ArcGIS Pro
Is QuickCapture limited to capturing points? No. You can capture points, lines and even polygons. For example, you can use QuickCapture to capture pavement condition as lines, or sidewalks as you walk through them. When working with lines and polygons you can configure your project to support nested data capture workflows (capture multiple features at once, for example, guardrail on the left and also on your right...) as well as in exclusive mode (the pavement condition is either good or bad...). Check https://community.esri.com/community/arcgis-quickcapture/blog/2019/10/06/understanding-exclusivity-g... for details.
Why would I want to use an external GNSS receiver with QuickCapture? QuickCapture works by default with the built-in GPS receiver in your device. It does not require additional hardware to run. However, in some cases, using an external GNSS receiver can help you in different ways:
More accurate location data: If used correctly, an external GNSS receiver will feed QuickCapture with more accurate locations. The accuracy of the X,Y and Z coordinates of your data will be better and more consistent that with the built-in location sensor.
Higher throughput: Generally, built-in location sensors work at 1hz. That is, you get at most 1 position per second. That is plenty for the vast majority of workflows but in some cases you may want more throughput. If you are capturing data while in a moving vehicle, such as a helicopter or a car, you will want that extra throughput to generate smoother lines or more accurate point observations. Even if you use QuickCapture from a bicycle! See: Trailblazers | ArcNews | Spring 2020
Metadata: When creating your QuickCapture project, you can configure it to automatically store GNSS metadata as GIS attributes. This will give you extra information to better understand the quality of the data submitted from the mobile app.
Can I time-stamp features as they get captured? Yes. QuickCapture projects can be configured to automatically capture the time when a button is pushed. For line and polygon data capture, you can also automatically store when the data capture starts and ends. For more information, check the Quick reference—QuickCapture | Documentation help topic.
Does QuickCapture work offline? Yes. Once a project is downloaded into your device, you no longer need to be connected to capture data. You do not need to configure your feature layers or projects in any special way to support offline workflows. That is, you do not need create an offline map, or even turn sync capabilities on in your feature layer. Once a project is locally downloaded, QuickCapture will work even if disconnected.
Can QuickCapture be used to update existing GIS data? No. With ArcGIS QuickCapture you can only add new records into a feature layer. If you want to update existing GIS features from a field app, you will need to use either Survey123 or Collector.
Can I use Spike for offset data capture workflows ? No. Spike is a laser measurement solution by Esri Partner IkeGPS. At this moment, Spike tightly integrates with Survey123, but not with QuickCapture. For more details see Survey123: Laser Measurements with Spike - YouTube We could bring similar integration into QuickCapture if we see interest in this.
When will QuickCapture support webhooks? In May 5 2020 we will release version 1.5 which will introduce support for webhooks.
What do I need to license ArcGIS QuickCapture? To create ArcGIS QuickCapture projects you need a Creator user type. To use the QuickCapture mobile app, you need at least a Field Worker user type, or an Editor user type with a QuickCapture license.
If using QuickCapture to document asset conditions, how can I keep historic records? Since QuickCapture can only add new records to a feature layer, you could theoretically use QuickCapture to record asset conditions. Every time a condition is submitted, a new record is added to your feature layer. The location of the GIS features could be used to identify your assets uniquely and navigate history back and forth by looking at the different GIS records added. This is technically possible, but I think there are likely better approaches to this. If you want to use a mobile app to uniquely identify an existing asset, look at its condition history and add a new inspection, I would go with Survey123 or Collector. Both applications allow you to do this in a much more effective and less error prone process.
In this post I will describe, step by step, how to launch ArcGIS QuickCapture from the Survey123 field application. The animation below illustrates the basic concept where a user launches the Survey123 field app, and then through a link launches QuickCapture. The link sets the target project to be opened in the QuickCapture app and optionally a value to be passed to the project user input.
There are two basic aspects to all of this: 1) Understanding the syntax for launching QuickCapture from a link and 2) Understanding how to dynamically create a link within a Survey123 survey. The good news, is that both of these things are very easy to do!
How to launch QuickCapture from a link
ArcGIS QuickCapture, like many other apps in your mobile device, can be launched from a link. The syntax for your link is straight-forward. The following shows the basics for opening a new project and passing a value to the project user input:
arcgis-quickcapture://?itemId=<your project item id>&projectInput:<your user input>=<the value you want to pass>
To construct the URL as shown above, you can follow these steps:
Login into QuickCapture designer and open your project in edit mode.
Now, get the itemId of your QuickCapture project from the browser address. In the screenshot below the itemId is highlighted in red. Make sure you do not include the / slashes at the end and beginning.
The name of your user input is essentially its label. Below I highlight where in designer you can get this value. Note that your user input can have spaces in the name.
With that, you will have your complete link to get things going. Take the link and test it from your mobile device. In fact, if simply want to do a quick test from your computer, you can trigger your link from your Windows web browser as long as you have the QuickCapture app for windows installed. Sorry if you are running a Mac.
Now we are going to include your link within a Survey123 form, and also describe how you can manipulate the link dynamically, to include information from your responses in your survey. This section, by the way, assumes you already know how to work with Survey123 Connect and XLSForm.
Go into Survey123 Connect and open your survey. In the XLSForm, start by adding a note type of question and wrap your link within an HTML link tag. For example:
Enter a value here
<a href="arcgis-quickcapture://?itemId=1cf9606a97d0451e83a600ccb5691ef3&userInput:Trail Name=Santa Ana River Trail">QuickCapture link</a>
Give it a go to try things out. You can even try from your computer if ArcGIS QuickCapture is installed locally.
Next, we are going to dynamically change the value passed in the user input by using an XLSForm variable replacement.