|
POST
|
Hi Sarah, Thank you for that information. With regards to the group size, just for my clarification, this is a field name in the attribute table for the point feature service that's being used. Is that correct? If so, could you please provide details about that group size attribute field? i.e. field type, type of data being entered, domains/subtypes, etc. Is the layer symbology based off that field? Thank you. -Kevin
... View more
03-20-2017
10:31 AM
|
0
|
0
|
645
|
|
POST
|
Hi Sarah, Could you please elaborate more on the use case where this issue occurs on iOS? - What type of iOS devices are being used? - What do you mean by 'variables' in this case? - For the users that experience the crash, is it consistently reproducible or intermittent? - What types of services are you working with? i.e. hosted through AGOL, Portal, ArcGIS Server. - Are all the volunteers part of the same AGOL organization and have their own named user accounts/logins? - When did this issue start happening? Thank you for that information. -Kevin
... View more
03-10-2017
03:34 PM
|
0
|
0
|
645
|
|
POST
|
Hi Carl, Thank you for that explanation. I have a few questions for you: 1. Could you please elaborate on what you mean by mid-edit? i.e. You selected a feature > started editing it > then changed the subtype field. Is that correct? 2. I am assuming that you're using the subtype field for the symbology with the unique value renderer. Is that correct? 3. How many subtypes do you have? 4. When you configured each subtype prior to publishing, are each of the defaults/domains unique for each subtype template? 5. When you say that you have to close the record for the correct domains to appear, do you mean that you have to stop editing and start again for the same feature? What you might be running into is that, in general regarding the subtype/domain behavior on Android, with the current 10.4.2 version we had addressed a critical software bug at 10.4.1 regarding the behavior when changing subtypes and domains that are based off the layer symbology and it clearing out all existing values from all fields without warning. Although we had successfully addressed that issue, it created additional issues with the messaging that would ordinarily be received when editing. For example, if I am changing from subtype1 to subtype2, where subtype2 has completely different/unique default values and domains applied to it, ordinarily you'd be prompted to either 'Keep existing values' or 'Reset default values'. However that message is not working in Android 10.4.2. We are working to address further subtype/domain issues that should be resolved in our next update for 10.4.3. Thank you. -Kevin
... View more
03-09-2017
06:06 PM
|
0
|
2
|
760
|
|
POST
|
Hi Alan, Firstly, in order to automatically capture and store height information as well as other GPS information, you will need to configure the GNSS Metadata attribute fields on your point layer, namely the Altitude field - Configure GPS metadata storage—Collector for ArcGIS | ArcGIS Secondly, in general the altitude values that Collector stores in the metadata represents the Height Above Ellipsoid (HAE) and not Mean Sea Level (MSL). The antenna height value you enter for the receiver, will be subtracted from the incoming altitude value in order to be more accurate to ground level. Thank you. -Kevin
... View more
02-16-2017
03:43 PM
|
4
|
2
|
983
|
|
POST
|
Hi Nancy, Thank you for that information. I tested this behavior with Collector 10.4.1 using a Surface Pro 4 and I believe saw the same behavior, however I would like to confirm. While connected to the internet, I downloaded a map for offline use. I then took that map outside and walked to a location where I lost my connectivity to WiFi. I then captured a few features and proceeded to walk back inside WiFi range. Now it took me a few times to reproduce this issue, but I was able to eventually reproduce the behavior where despite the device having internet connectivity, I was receiving the same error when trying to sync. In my case, however, I found that in order to regain connectivity, I would simply choose Maps > My Maps/All Maps > then click the ellipsis button in the upper right corner and then click 'Refresh' to refresh the map gallery. Once the maps were populated I was able to sync successfully. I didn't have to remove the account or sign back into AGOL. I still had the same amount of edits and was able to sync successfully at that point. Have you tried this on your end as well with refreshing the map gallery? We're still looking into this behavior, but I wanted to share my feedback and workaround. Thank you. -Kevin
... View more
02-03-2017
02:40 PM
|
1
|
2
|
1170
|
|
POST
|
Hi William, Another possible way to try and narrow this issue down further, would be to publish your data to ArcGIS Online instead of portal. I understand that this isn't an ideal scenario and that you may not even be able to test this, but if you can and if it works, we would at least know that your data and relationship configuration is working successfully. You can then look at the portal side to narrow down further. Also, I know you said you were at the latest version of Collector on iOS, but just to double-check the version should be 10.4.2. Please ensure that's the version listed in the About page in Collector. Thank you. -Kevin
... View more
02-02-2017
02:02 PM
|
0
|
1
|
1461
|
|
POST
|
Hi William, Based on our conversation, everything appears to be configured correctly, and nothing stands out to me as being an obvious problem. Therefore in order to proceed further, if you have Technical Support maintenance, I would recommend to submit a case regarding this issue. That way they can look at your data and portal/server configuration more closely, outside of a public forum, to see if any issues are revealed. If you submit a case with Technical Support, please include the link to our GeoNet conversation so that the analyst you work with already has the background information and should help move the issue along more quickly. The contact info for Technical Support is at the bottom of Esri Support Esri Support Services Thank you -Kevin
... View more
02-02-2017
01:53 PM
|
0
|
3
|
1461
|
|
POST
|
Hi William, What type of DBMS are you working with? i.e. PostgreSQL, etc. Are you using the built-in ArcGIS Data Store with Portal? Thank you. -Kevin
... View more
02-02-2017
01:11 PM
|
0
|
5
|
1461
|
|
POST
|
Thank you for that information. So just to further clarify, you're saying that with that configuration, it is not working in Collector when trying to view existing related records. Is that correct? I am just trying to ensure we are on the same page. Thank you. -Kevin
... View more
02-02-2017
12:47 PM
|
0
|
7
|
1867
|
|
POST
|
Hi William, I understand its frustrating, but we'll figure it out. Just to clarify, are you using a GlobalID in the main feature class that's related to a GUID or is the main feature class using a user-defined field related to a GUID? I am just trying to understand further by what is meant by 'Used the GUID as keys'. Is the relationship one-to-one or one-to-many? Thank you. -Kevin
... View more
02-02-2017
12:32 PM
|
0
|
1
|
1867
|
|
POST
|
Hi William, Thank you for that information. For testing purposes, just to get the relationship functionality up and running, I would recommend to create a new feature class in the same geodatabase with a GlobalID field as well as other random fields to test with. Then related that to a table with the GUID field. Then in Collector, because the GlobalID field is system defined, it will populate automatically when new features are created. That value will also get copied into the GUID field, thus linking them together. Using the GlobalID/GUID relationship is oftentimes more ideal because it doesn't require any user interaction to link the records together and populate certain fields. Let me know if you have any issues with that test. If it works, the same relationship should be able to be adopted for your normal data. Thank you. -Kevin
... View more
02-02-2017
12:15 PM
|
0
|
3
|
1867
|
|
POST
|
Hi William, When adding new related records, are you manually populating both the Primary and Foreign Key fields with the same exact values? This will essentially link them together. If only the Primary Key field is being populated but the Foreign Key field is left blank, this will cause orphaned records. They can still be added, but are not related. Thank you. -Kevin
... View more
02-02-2017
12:03 PM
|
0
|
5
|
1867
|
|
POST
|
Hi William, Which operating system are you using with Collector? When did this issue start happening? i.e. has it worked in Collector before for you? How are the relationships configured between the origin and destination tables? i.e. using Global ID's to GUID fields, or user-defined fields? Are the relationships between feature class and tables or feature class to feature class? Thank you. -Kevin
... View more
02-02-2017
11:44 AM
|
0
|
7
|
1867
|
|
POST
|
Hi Dale, Sorry for the late reply. That's great to hear that it worked for the GNSS Capture map. At least we now know its not an issue with the iOS device or GPS receiver. I think I know whats going on here. On the iOS side, you're running into the same software bug that Daryl is above, regarding the issue with the GNSS Metadata fields and PostgreSQL since I am assuming you're also using the built-in ArcGIS Data Store with Portal. Therefore that explanation above also applies in that case. Again we are aware of that issue and will address it with the next app update for iOS. The reason why it works on Android, is because that issue was already addressed prior to that release. The reason why it worked for the GNSS Capture map on iOS, is because that uses a hosted feature service from ArcGIS Online and therefore doesn't use PostgreSQL like Portal does for the built-in data store. Thank you. -Kevin
... View more
02-01-2017
05:15 PM
|
0
|
0
|
2910
|
|
POST
|
Hi Dale, Thank you for that information. As a test, to remove your map and data from the equation (even though it works on Android), try the following on iOS: 1. Sign out of your current account 2. Click 'Try It' at the bottom of the Collector splash screen. 3. Just like you did originally when you signed in, go into the Settings and set up your Location Provider to use the GPS receiver being used. 4. Once that's done, launch the GNSS Capture map. 5. Collect new point features using the GPS receiver and see if the metadata is being stored for those. We can then go from there, depending on those results. Thank you. -Kevin
... View more
01-31-2017
03:34 PM
|
0
|
4
|
2910
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 08-21-2023 10:55 AM | |
| 1 | 03-02-2021 02:21 PM | |
| 1 | 11-16-2022 02:37 PM | |
| 1 | 02-01-2021 02:20 PM | |
| 1 | 07-19-2021 10:30 AM |
| Online Status |
Offline
|
| Date Last Visited |
10-13-2025
10:04 AM
|