Latest Contributions by ColinLawrence

It does not sound like the same issue we are investigating as this issue was specific to Android 10 devices. It could be a device limitation. Devices can come with a wide range of built in GPS capabilities (or none at all). Getting in contact with the manufacturer is the best way to find out to what extent GPS is supported. If there is no GPS chip in the device it will attempt to pull locations from Wifi/bluetooth or other sources and the resulting fix will be dramatically less accurate. The Samsung S7 (should) support GPS/NMEA and therefore could potentially get accuracy up to ~ 10ft/3m in ideal conditions. I cannot speak for the other devices. What are the accuracy readings you are receiving and consequently what is the accuracy threshold you have set in the app (default is 30ft)? Also, are you using Collector or Collector Classic? Regards, Colin ... View more

What device model and Android OS version are you using? We are investigating a problem likely related to this. Regards, Colin ... View more

Molly, You can vote up this functionality for the new Collector here: https://community.esri.com/ideas/17381  Also, as Katherine mentioned, Quick Capture is useful for speedy and simple collections.  Regards, Colin ... View more

Kristal, I am not sure I can answer the "why" unfortunately. This thread has some discussions around this functionality and I can see you are not the only one requesting this functionality to return. I would encourage you to reach out to Support and get attached to the bug referenced in that thread if possible. The more people that request this functionality the greater the chance it is considered. Can you detail a bit more around the workflow you are trying to accomplish so I can pass the feedback on? Regards, Colin ... View more

Good to hear you got to the bottom of it. There is a lesson there because I had to learn it myself after bumping my head a few times on the same workflow; It will go more smoothly next time.  Happy to help! Regards, Colin ... View more

Hi Kristal, The article you linked is a bit dated and shows the interface for Collector Classic. It is true that the copy workflow differed in Classic from what you see in the current version of Collector. When using copy in Collector, it only copies the attributes and not the feature geometry. If the new feature lies directly on top of the copied feature you could use snapping to trace over the existing feature, otherwise, it may be best to use other parts of the ArcGIS platform to accomplish these workflows (or utilize Classic).  Regards, Colin ... View more

Hello Steve, Are you seeing this problem on any other devices (if available)? Maybe you could detail your work area a bit for me (ie where are you working, is it near buildings with wifi coverage, etc)? I would be curious is others are experiencing this as well. I tested with an S9 (seems to share the same GPS specs as the S20) and didnt get the same results as you; sometimes jumping from 4m to 10m when going in and out of wifi range. The way Collector interacts with Location Services is different from Classic so one might expect different behavior, but it shouldnt necessarily be worse. Regards, Colin ... View more

Molly, The imagery hybrid basemap contains a vector tile reference layer (for the labeling). Classic does not support vector tiles so my guess is that this is causing the crashing.  Is there a reason you are still using Classic instead of the current version of Collector? Regards, Colin ... View more

Vertical transformations are still very much in our future plans for Collector. Although I cannot give you a specific date, we hope to have this in some form within the year.  Regards, Colin ... View more

Hello, Following up on Katherine's suggestions, generally this type of error is the result of something data specific. Having a copy of a layer in the Web Map is a common cause of this type of error. Please also check for special or reserved characters in the service name or fields. If you are still at a loss it could be worth turning off sync on the service and re-enabling it. Before doing this, ensure you have no existing replicas with outstanding data that needs to be synced. You could also try republishing. However, if it is data specific, these steps may not resolve your issue.  Let me know if any of these suggestions help. Regards, Colin ... View more

Hi Katharina, The links are processed all at once so it would not be possible to go to the map browse screen first, select a map, then continue with further parameters in the link (like search). The only exception to this is with sign in. If you are not currently signed in, it takes you to the sign in screen and after credentials are entered it proceeds with the rest of the URL parameters.  You can populate attributes to a specified layer in a certain map. You may already be aware of this, but here is more info on the available parameters in Collector today.  Regards, Colin ... View more

Hello Alina, In your example, Survey123 is the application parsing the URL; I am not sure that Survey123 supports the callbackprompt parameter at this time which could be why you do not see the message. In an example I setup that goes from Explorer to Collector, I put the message "this is a callback message" for the callbackprompt parameter.  ... View more

Charlie, It should take you back to the previous state the app was in which in this case should be the survey that was open. I do not believe there is a way to specify a certain screen to open with the callback.  Regards, Colin ... View more

Hello Molly, Are you still having issues with the app crashing? The imagery hybrid basemap downloads without issue for me. Have you tried turning on the troubleshooting logs in Collector? These are found under the settings in the app > Troubleshooting. You can return and check the logs after a failure/crash and share them. Also, please note the app version and what type of device you are using. Thanks! Regards, Colin ... View more