Latest Contributions by XiaoxuLi

Hi Mike, thanks for reporting this. I have sent you an email to discuss this further.

Hi, Megan! By other attributes, do you mean pre-populating the value of a feature layer's data fields in Collector and pass them as QuickCapture URL parameters? We don't support it, but would like to hear about your use cases. @JohnHasthorpe

Hi Jesse, the example above is just an illustration of the concept, the key here is simply to apply the button user input to a data field that has coded value domain defined. We have a similar template called Marine Debris Sampling. You can try it directly in the QuickCapture mobile app (Continue without signing in), and if interested, deploy it to your account in QuickCapture designer and customize your project based on it. You can also send us your feedback at QuickCapture@esri.com or if you have any issues setting up your project.

Hi Jesse, here are some ideas: The Known species button. Create a data field with coded value domain (a list of valid species) and configure a button user input on this field for the button. You may want to create several of these buttons for known species, and group or categorize them by their family. You'll also need a Other species button for the tree species that are unknown, and also set it with a button user input to take notes. QuickCapture supports offline maps including tile package, vector tile package, and mobile map package, they can be created from ArcGIS Pro. In the standard workflow, you'll need to upload the package as an AGOL item, then set it as QuickCapture project map. Adding the package as an item is good for distribution purposes if several field workers were to sign in to QuickCapture and work on the same project collaboratively. Unfortunately, QuickCapture currently doesn't support adding a map/package from local files on the device.

In short, the 'Location Latitude/Longitude' means the coordinates when a button is pressed in QuickCapture, the 'Photo Latitude/Longitude' specifically means the coordinates when a photo is taken in QuickCapture. For example, when pressing the 'Deer' button like below in QuickCapture, the value of 'Location Latitude/Longitude' variables is captured. Then the camera dialog appears, now when you press again to take a photo, the value of 'Photo Latitude/Longitude' variables are captured and are saved to the photo EXIF tags. In most scenarios, the captured coordinates of these two locations are almost the same, but in some at-speed data collection workflows, a user may press the button at one location and take a photo at an updated location. Or some people just require the exact location info where the photo is taken, so the 'Photo Latitude/Longitude' variables become more useful to them. Thanks, Mandy

Hi Helene, this is not possible, unfortunately. If you give the field with a fixed value, it by default always stores this given value when the button is pressed. If you want the user to dynamically enter a value for SharedID , try configure this field with a project user input. However, neither of these would satisfy the need for auto-incrementing.

Hi Helene, p lease see the comments below. "I am imagining a function where it auto incremented for each started track." This is possible and out of the box when you select a feature layer for capturing streaming points. Each point has a field called ObjectID and it's auto-incremented. "...t he points building one track would share one ID." This can be done by manually adding a new data field, i.e. the shared ID field, to the feature layer. In the QuickCapture project, you can preconfigure the button to submit streaming points to this field with a fixed value, so that points captured by this button always submit the same value to this specified field. Thanks, Mandy

Hi Wade, Sounds like you can try using Project user input to solve this problem. The project user input is basically a user input dialog (or a choice list) that shows up when a project is opened. It can be applied to a field in the feature layer so the input value is collected as a data attribute, which later you can use for filtering purposes on the web map. In this way, you can still keep one QuickCapture project, but configure the project user input with a list of districts names, so when user opens the project, the first thing to do is select a district to work on, and then continue to capture other information you configured for the project. Let me know if this helps with your question. Thanks, Mandy

Online Status	Offline
Date Last Visited	an hour ago

My Ideas

Latest Contributions by XiaoxuLi

Re: Add an option to Watermark Photos in QuickCapture - Status changed to: In Product Plan

Re: Battery overheating

Re: Passing Multiple Attributes from Collector to QuickCapture

Re: Tree sampling with QuickCapture

Re: Tree sampling with QuickCapture

Re: QuickCapture Capture fields Device variable photo vs. location

Re: Uniquely identifying a track built with points

Re: Uniquely identifying a track built with points

Re: Multiple Project User Input fields in QuickCapture - Status changed to: Under Consideration

Re: Need to capture 2 its in the same quick capture