|
POST
|
Hi Robert, What kind of location searches are they doing? Are these addresses, coordinates, or parts of a Feature search (feature attributes)? Signal strength can certainly be a factor when searching addresses and coordinates because the requests have to hit the geocoding service; if this fails or takes too long there will be no results. Regards, Colin
... View more
05-06-2020
04:07 PM
|
0
|
0
|
669
|
|
POST
|
Kyle, Brad, This was a bug and we have fixed it for the next release, 20.2. Very timely as this release should be available within the next week or two. There is still some funkiness around Offline Areas. As you may know you can have multiple areas and in this scenario the link will only work to open the area listed as "current" - in other words, the last opened map. If none of the Offline Areas are the "current" the link will only open to the Offline Areas Browse screen. A link could also not work if the Offline Area was just downloaded but not opened first or when all Areas were removed but the "online" map has not been opened yet (or any other map). We hope to iron out these behaviors in a future release but the tight window did not allow it. Thanks! Regards, Colin
... View more
05-01-2020
05:25 PM
|
1
|
0
|
1905
|
|
POST
|
Erica, Thanks for sharing the data. I can reproduce the problem but I dont see anything obvious jumping out at the moment. I will take a more extended look at this. Do you know if this is reproducible with any other View layers (from the original source or another)? I would note that when you take this data offline, the layer displays just fine. This could give you a temporary workaround. Regards, Colin
... View more
04-30-2020
03:49 PM
|
0
|
3
|
2469
|
|
POST
|
We are very close to wrapping up 20.2, so we are hoping it will be available early May. I cant give an exact date at this point unfortunately. Regards, Colin
... View more
04-30-2020
08:55 AM
|
0
|
0
|
2190
|
|
POST
|
I can reproduce this problem; addFeature is never popping. We are looking into what the problem is. It is isolated to offline maps. Thanks for reporting this. Regards, Colin
... View more
04-29-2020
05:08 PM
|
0
|
2
|
1905
|
|
POST
|
Hi Brad, This workflow should work. Can you share the device you are using and the version of Collector (assuming its 20.1 and not the beta version)? Also, I would suggest using the universal app link format moving prefix forward ie: https://collector.arcgis.app/?itemID=.... You can try the formatting above but I doubt it makes a difference for this scenario. Is the GUID value the only attribute you are passing? Regards, Colin
... View more
04-29-2020
04:36 PM
|
0
|
3
|
1905
|
|
POST
|
Erica, I would be happy to take a look if your data is in AGOL and you are willing to share. The easiest way to do so is to create a group, share the map and layers with the group, and invite the user Collector4ArcGIS to the group. I am assuming the layer renders fine with no filter applied to the layer/map? Also, which platform and version of Collector are you using? Regards, Colin
... View more
04-29-2020
12:00 PM
|
0
|
5
|
4927
|
|
POST
|
Erica, There are some known issues with View layers with View Definitions set on them to exclude fields. Is a View Definition what you used in the Visualization page? The difference in my experience is that the layer still appears in the layer list but does not render in the map. Can you let me know what specific type of filtering you used and on which fields? Regards, Colin
... View more
04-29-2020
10:31 AM
|
0
|
7
|
4927
|
|
POST
|
Hi Steve, Thank you for your help in identifying the problem. We are targeting a fix for this in the coming weeks with the 20.2 release for Android. The problem was determined to be specific to Android 10 devices and the method we were using to listen to NMEA. Regards, Colin
... View more
04-27-2020
04:43 PM
|
1
|
2
|
2190
|
|
POST
|
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
04-24-2020
11:22 AM
|
0
|
0
|
1462
|
|
POST
|
What device model and Android OS version are you using? We are investigating a problem likely related to this. Regards, Colin
... View more
04-23-2020
12:00 PM
|
0
|
2
|
1462
|
|
POST
|
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
04-22-2020
08:41 AM
|
0
|
1
|
2131
|
|
POST
|
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
04-21-2020
12:27 PM
|
0
|
1
|
4733
|
|
POST
|
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
04-21-2020
09:34 AM
|
0
|
0
|
4289
|
|
POST
|
Hi Charlie, I created a feature class in the default .gdb for the Pro project, then created the stand alone table, created a relationship class between the two using the GlobalID field in both as the key. Typically when using a GlobalID as the key for the parent table, the child key should be a field of type GUID. A GlobalID > GlobalID relationship wouldn't work. GUID is a type of field meant for accepting GlobalID values, in this scenario the GlobalID value from the parent feature. I am not sure if this is what you meant exactly but its somewhere to start. I would see if you can successfully create a related record in Pro to ensure its a valid relationship to begin with. If you are familiar with Collector Classic you could also try it there to try to isolate the problem further. Regards, Colin
... View more
04-20-2020
03:21 PM
|
3
|
2
|
4289
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 3 weeks ago | |
| 4 | 3 weeks ago | |
| 1 | 04-14-2026 09:11 AM | |
| 1 | 03-18-2026 11:54 AM | |
| 1 | 03-06-2026 02:09 PM |
| Online Status |
Offline
|
| Date Last Visited |
Thursday
|