nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS QuickCapture- Reduce Location Tracking Interval

Amanda.Huber@threeriversparks.org_trpd

Hello QuickCapture Team and/or @JohnathanHasthorpe ,

We recently discovered that QuickCapture's LocationTracking is limited to every 10 minutes. Even when editing the JSON to a lower interval, the project is restricted to none at all or 10min minimum.

For those using QuickCapture in the field, it's imperitive that they can view their current location tracks on the map. We desprately need this solution to be equivilant with how ArcGIS Field Maps handles uploading Location Tracks:

Currently we're using QuickCapture to conduct Aerial Deer Count surveys via helicoper. It's crucial that our team can see the area they've covered in real time.

Is this planned for a future update? If not, is there someone we can speak with and provide all our use cases?

Thank you,

Amanda Huber

Find more posts tagged with

Designer

Needs Clarification

Status: Needs Clarification

Comments

BrettFrahm

FYI @JohnathanHasthorpe & @Amanda__Huber Here is the idea I made that asks for real-time tracks / field maps equivalency / on-device tracks.

https://community.esri.com/t5/arcgis-quickcapture-ideas/on-device-tracks-layer-for-quick-capture/idi-p/1587982

Amanda.Huber@threeriversparks.org_trpd

@JohnathanHasthorpe thank you for clarifying.

Can this be improved and have more of an equivilancy with how Field Maps uses location tracking?

If location tracking isn't real-time then it kinda defeats the purpose of it in the field.

Thanks,

Amanda Huber

JHasthorpe

@Amanda__Huber - Yes 60s is the minimum.

Amanda.Huber@threeriversparks.org_trpd

Hi @JohnathanHasthorpe,

Thanks for your response. Yes, having more time options in the designer dropdown would be ideal for this product.

Is 60 seconds the lowest it can go? I read through the JSON documentation and it sounded like it's either -1 or 600s with no options in between:

Thanks again,

Amanda Huber

JHasthorpe

@Amanda__Huber

You can edit the project JSON as follows:

"tracking": {
"enabled": true,
"required": true,
"lastKnownLocationsUpdateInterval": 60,
"tracksUploadInterval": 60,
"tracksCategory": "${projectName}",
"lastKnownLocationsCategory": "${projectName}"
},

This will give you a tracks upload interval of 60 seconds (the app allows this).

If we expose a 60 second option in designer, would this meet your requirements?

@BrettFrahm Could you open a seperate idea, for viewing the sent tracks on the device and share youre use case.

BrettFrahm

@Amanda__Huber thank you for making this post. This is a much needed enhancement for Quick Capture, but I'd like to add that the upload interval is only part of the issue for viewing live tracks in this app. Being able to view "on device layers" just like you can do in Field Maps is 100% needed for Quick Capture. This is the feature that allows users in Field Maps to view their tracks in real time.

Since we do not have the ability to view "on device layers" we are required to pull the tracks service into the map, which is dependent on the upload interval.

Please ESRI, bring Field Map tracking equivalency to Quick Capture!