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:
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:
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.