Latest Contributions by MeganEngel

Good afternoon, I am writing to see if other users have encountered syncing delays when syncing data (with photos) and what sorts of work arounds y'all have done to help alleviate some of these delays. Users syncing 15+data points (with photos) are experiencing long delays, and sometimes the sync times out. They sync when they're back in the office and connected to WiFi Photos are native camera size. I recently downgraded the photo size to see if that will help with the syncing Battery Saving Mode is turned on. Sometimes the syncing goes at 5 data points at a time, and the user has to keep pressing "sync" after it syncs five then times out. Work around currently for me is ensuring the map associated with the QC app i am using is saved in regular Map Viewer and not Map Viewer Beta. This work around doesn't work every time though. I welcome any thoughts or insights into this, thank you.

John, The crashing for two of the users has occurred with previous versions of QC. As for the other two lines, I have folks testing this now and will respond when I get their details.

Yes, this has happened to my end-users before and they were able to email the data and I was able to use the data recovery method and amend the data back into the dataset.

Hey John, thanks for getting back with me. The users encountering the issues all have ore than 5 GB of memory on their device They all have the battery saving mode turned on. The iPhone 6 and 7 have reliable crashes, then the iPhone X has unreliable crashes, and it's more random when it happens. Users are running collector at the same time as QC I would say 50% of the time. Sometimes they may have S123 open as well, but that is less common. The QCCreator account has been added to my organizations troubleshooting group. You should be able to see the application and data associated with this application. My username with my organization is "aprickett_angler". Here is the link to one of our applications that is experiencing crashes: https://arcg.is/G1O8X

A hand full of end-users in my organization have been experiencing crashing issues with the QuickCapture applications I have deployed. The applications allow users to collect a single point, take a photo, and write a note. The users encountering the crashing issue can take the photo, but then the app crashes. Is there something I do on the designer side of things to resolve the issue, or provide them guidance on how to resolve the issue on their devices. They have all update their devices, uninstalled and re-installed the QC application, and remove and re-add the specific QC apps I have authored. Additionally, this has happened both in the AGOL QC apps I have authored, and one of the Enterprise QC apps I have authored. I had them send me the specs on their devices. Device 1 Iphone 6 iOS – 12.5.1 QC Version – 1.9.127 Device 2 iPhone 7 iOS 14.4.1 QC 1.9.127 Device 3 iPhone XR iOS 13.6 1.9.127

‎03-02-2021

Hey @JohnathanHasthorpe and @XiaoxuLi , So it would be passing certain attributes from a certain feature layer (in collector) to a different feature layer (in QC), so not populating the same data set. If the option to have multiple project user inputs was implemented, that would be a good solution for this, since the custom URL is already being used to launch QC and populate the project user input field. The primary purpose for us, is to ensure that the feature layer we are using in QC (which is a point layer for collecting initial site evaluation information and photos across the state), has some of the same information as the parcel layers the end-user sees in Collector, and the point layer (from QC) be filtered later. Since this is a statewide dataset, being able to filter multiple levels is key. Let me know if you have additional questions/comments and i will be happy to provide additional information. Thanks!

‎02-26-2021

Please add an option to watermark photos with date and/or time to photos taken using QuickCapture field applications. This would be a great option to see in the QC designer page. Use Case: In my line of work, having a watermarked photo with the date the photo was taken is required for some of our regulatory documentation. We are able to add a watermark during post-processing, however if watermarking was an option in the designer page for our photos, we would have one less step in our post-processing and the photos would be ready to use as soon as their collected. Thanks!

‎02-25-2021

I am writing to see if there is a way, without use of a 3rd party automation software or script, to pass multiple attributes from Collector to QuickCapture, similar to how you can do for Collector to S123. Currently I am using the Project User Input to pass a parcel id from an attribute in a parcel layer to a point layer where data collection efforts are taking place. However, I am interested in passing multiple attributes (Parcel owner, watershed, etc) from collector to QC in a way that every point collected after launching QC from collector retains just not the user input, but those other attribute. Thank you, and please let me know if you need additional details.

‎02-18-2021

Brett, Sorry for such a long delay on this! After troubleshooting the issue with my field folks, I ended up re-publishing the survey with form updates they had requested. Ultimately, once I republished the survey end-users were not encountering this issue again, and I was unable to replicate my original issue to supply you with a screen recording. The issue they had been encountering was only for the 'freehand' tool, and the error message was only appearing when users would go to submit the survey.

‎02-18-2021

This functionality would be extremely helpful. I have encountered a similar example repeatedly; having to add additional project data (say soils or wetland areas) for my field users. In which case, I've had to overwrite existing services for those projects to add those layers. On the other hard, some feature services I have published, have layers that I would like to remove from the feature service entirely, because they're out of date and/or not pertinent anymore, without having to either 1. remove the that specific layer from every web map that I use the feature service in or 2. republish the service with out that layer. Great idea!

Online Status	Offline
Date Last Visited	3 weeks ago

My Ideas

Latest Contributions by MeganEngel

QuickCapture Syncing Delays

Re: QC Crashing after collecting photo points

Re: QC Crashing after collecting photo points

Re: QC Crashing after collecting photo points

QC Crashing after collecting photo points

Re: Passing Multiple Attributes from Collector to QuickCapture

Add an option to Watermark Photos in QuickCapture

Passing Multiple Attributes from Collector to QuickCapture

Re: Operation Rollback Error when using a drawn in geoshape in a repeat

Re: Add and remove layers to existing hosted feature service without affecting existing data and configurations