|
POST
|
Hi Daryl, With regards to the issue you're running into with the missing GNSS metadata fields, we have a known issue with the current Collector for ArcGIS version where the values aren't being written to the fields when the data is stored in a PostgreSQL database. Because it sounds like you're working with the ArcGIS Data Store with Portal, PostgreSQL is the database that runs on the backend. Therefore this is probably the issue you're running into, as I recently reproduced it on my end using Portal as well. The problem is due to an attribute field casing discrepancy between Collector and PostgreSQL. This issue is reproducible on iOS, Android, and Windows. This issue will be resolved in the next app update that gets released. What operating system are you working with Collector on? Thank you. ***** Hi Dale, Because your issue is unique to iOS and not on Android for the same map, it sounds like you're running into a different issue than what I described above. Does this issue happen for every point you collect on iOS or is it intermittent behavior? Are all the metadata fields blank or just a few of them? Thank you. -Kevin
... View more
01-31-2017
02:13 PM
|
1
|
7
|
2911
|
|
POST
|
Hi Brook, Thank you for that information. In general, with regards to having a setting that only allows features to be captured via the GPS and not tapping on the map, this is something we're aware of and are planning to implement in the future. Unfortunately I don't have any specific details at this time as to when/how that functionality will be included. With regards to the proposed workaround for making the GNSS metadata fields required in order to force the field user to capture data via the GPS, in theory this should work just fine because of the fact that by-design the GNSS metadata fields are hidden when editing and capturing new features. Therefore if the user has a stable fix and capturing a point, the field(s) should be populated on the back-end automatically thereby making the 'Submit' button active in order to submit the feature. However, this could also lead to confusion among the field users because if they do happen to capture a point by tapping on the map, the 'Submit' button will remain grayed out even if they've populated all the attribute fields. The reason being is because the hidden metadata fields will not be populated and will prevent the feature from being submitted. The user will not be notified as to the reason why. It is therefore not recommended to use this workflow since GNSS metadata fields weren't designed to be made required, because they get populated automatically and require no user input. - Is there a particular reason why the field users are capturing points with a combination of GPS and manually tapping on the map? - Are they physically in areas where they cannot obtain a GPS fix with the receiver and are therefore just adding points manually? Thank you. -Kevin
... View more
01-09-2017
11:41 AM
|
0
|
1
|
2551
|
|
POST
|
Hi Brook, Thank you for that information. What I suspect might be happening here is that when the field user clicks the 'Submit' button in the upper right corner, they're inadvertently tapping on the map itself, thereby creating a map point and no longer a GPS point which will clear the GNSS metadata fields of their contents. For Collector on iOS, when working with tablets there is a small gap between the top of the collect panel and the bottom of header. Sometimes when going to tap on 'Submit' if you tap too close to that gap, it will actually drop a new point there. This is a current design limitation that's being looked into for a future release. The reason why I suspect that's what's happening is for a few different reasons; 1) this behavior happens intermittently and is not easily reproducible, and 2) when this issue happens all of the metadata fields are blank as oppose to just a few of them. Several months back, my colleague and I saw an issue where random metadata fields would be blank after having captured several points. Not all of them would be blank, only a few. But those few that were blank would fluctuate between different fields. This issue has since been addressed already and we haven't been able to reproduce it since then. Therefore I don't suspect that's what's happening here. I have a question for you. For the points that have the blank GNSS metadata fields, when looking at the map is the geometry in the correct locations or is it off? If you are running into the issue where the field user is tapping on the map when hitting 'Submit', the offset of that point should be noticeable. About how many field users/devices do you have? To answer your question, no, the metadata values that are already written into the fields when the GPS point is dropped on the map doesn't expire. The time it takes the user to actually submit the feature after the point has been added to the map, shouldn't have any bearing on this behavior. Thank you. -Kevin
... View more
01-04-2017
11:35 AM
|
0
|
4
|
2551
|
|
POST
|
Hi Brook, Thank you for sharing that information. I recently tried to reproduce this issue using an iPad Pro (iOS 10.2) and a Trimble R2 with and w/out RTK corrections and I was unable to reproduce the issue. For my feature service, I had enabled all of the GNSS metadata fields per the online documentation. My testing lasted for over 1 hour and approximately 80-100 points were captured and all the metadata was populated. My colleague also tested with a Trimble R1 and an iPhone 7 and couldn't reproduce the issue either. Could you provide more details of your testing? - What type of iOS device(s) are you using? - When you do reproduce the issue, is it just a particular GNSS metadata field that's blank or is it all the fields? - If its only a single field, is it the same field all the time or can it vary? - In your feature service, which GNSS metadata fields did you include? All of them per the documentation or just a few? Thank you for that information. -Kevin
... View more
12-29-2016
11:06 AM
|
0
|
6
|
2551
|
|
POST
|
Hi Mike, Thank you for sharing that information/feedback. This is a known limitation that we're aware of for iOS and Android. When/if a feature layer has a related table, continuous collect is no longer available in that map in Collector. This effects the entire map and other layers, not just the layer with the related table. The support for continuous collect with related tables in the web map is considered to be an enhancement and not a defect for iOS and Android. It should be resolved in a future release, however I don't have the specific details at this time for when that will be. Thank you. -Kevin
... View more
12-28-2016
10:26 AM
|
0
|
0
|
496
|
|
POST
|
Hi Josh, Thank you for that information. I see that you do have the correct field types, however they are in the reverse order. For the poles layer, that should contain the Global ID field and the inspection table should contain the GUID field. The reason being is because the poles layer is the origin and the inspection table is the destination therefore the Global ID's should be generated for the existing pole features. Then when a new inspection is created for that pole, that value should be copied into the related GUID field to link them together. That gets done automatically when adding the related record in Collector. But in general, the fields names don't really matter it's just the field types that do and the direction of the relationship as far as which is the origin and which is the destination. For testing purposes, I'd recommend creating copies of the pole layer and inspection table just to test out that relationship. Thank you. -Kevin
... View more
11-03-2016
10:46 AM
|
0
|
1
|
1093
|
|
POST
|
Hi Josh, With regards to the relationship class you've setup between the poles and inspection table, it should be between a GlobalID and GUID field as oppose to a common GUID field for both. The reason being is because Global ID's are system generated and are automatically copied over to the GUID field in Collector, thus linking the records together. What's likely happening in this case is that since no GUID value is being linked to the related record, its being orphaned. Try recreating the relationship to be between a GlobalID field and Guid field. In ArcMap, to add Global ID's right-click on the pole layer in the Catalog Window > Manage > Add Global Id's. Thank you. -Kevin
... View more
11-02-2016
01:01 PM
|
0
|
3
|
1093
|
|
POST
|
Hello, The issue you are running into is a known Software Defect that ESRI is aware of and is addressing. I was able to reproduce the same issue on my end as well. The Software Defect is: [NIM089305:Mobile Project Center does not respect changes to the portal URL when adding feature services.] The issue is that when an invalid ArcGIS Online URL is entered the first time, that URL gets cached by the software and does not respect changes made to it in order to make it valid. For example, I first entered my URL starting with an http and not an https. Please try the following workaround; exit MPC, launch MPC > File > New File > Settings > Content Sharing > ArcGIS Portal format URL as https://ess.maps.arcgis.com/sharing Then you will be prompted to sign in using your AGOL Organization credentials and it should work successfully. Thank you.
... View more
02-25-2013
01:36 PM
|
0
|
0
|
718
|
|
POST
|
Hello, With regards to NIM083798 - Fields for external list values in ArcPad Studio 10 only show on XP machines (not on Win7/Vista). ESRI tested and has confirmed the following workaround: 1 - confirm ArcPad Studio is closed before beginning 2 - right-click ArcPad Studio icon on desktop or Start Menu 3 - select Properties option to display ArcPad Studio Properties dialog window 4 - click Compatibility tab 5 - check the Compatibility mode checkbox > Run this program in compatibility mode for > select Windows XP SP3 option 6 - click Apply > OK buttons 7 - launch ArcPad Studio in normal manner, test whether DBF values display properly in the custom form editor; "text" and "values" dropdowns should now be populated as expected if this workaround was successful Thank you.
... View more
08-17-2012
09:20 AM
|
2
|
0
|
1117
|
|
POST
|
Hello, With regards to installing the SDK for AGM 3.0 with Visual Studio 2010, currently only version 2008 has been certified with the software. I have already submitted an internal Enhancement Request for this issue. According to the following links, only Visual Studio 2008 is referenced: http://resources.arcgis.com/en/help/windows-mobile-sdk/concepts/index.html#/What_s_new_in_the_ArcGIS_Runtime_SDK_for_Windows_Mobile_3_0/01sp00000067000000/ http://resources.arcgis.com/en/help/windows-mobile-sdk/concepts/index.html#/Frequently_asked_questions/01sp00000006000000/ http://resources.arcgis.com/en/help/windows-mobile-sdk/concepts/index.html#/Development_requirements/01sp00000003000000/ Thank you.
... View more
06-28-2012
09:53 AM
|
0
|
0
|
324
|
|
POST
|
Hello, Just so that I understand correctly, you are inquiring as to whether ArcPad is compatible with Windows Phone 7.5. Is that correct? Could you please clarify what you mean by "...need particular setting for loading project..." with regards to Windows Mobile 6.0? What type of device are you working with that is running Win Mo 6? Thank you.
... View more
05-18-2012
08:53 AM
|
0
|
0
|
278
|
|
POST
|
Hello, the reason why the error is being received when attempting to create a data package from the Publisher toolbar, is because the Bing Basemap is a map service hosted by esri/microsoft that is being viewed as read-only data in ArcMap. Because the data is located on external servers, there is nothing that the data package can package. Therefore that layer/basemap is invalid. However, the basemap does get written to the .pmf that can be sent to another user. Providing that they have internet access that basemap should display automatically when the .pmf gets opened in ArcReader. I hope this helps. Thank you.
... View more
05-03-2012
01:10 PM
|
0
|
0
|
1157
|
|
POST
|
Hello, On the GPS analyst toolbar, what tool are you trying to utilize in ArcMap? Thank you.
... View more
05-03-2012
11:41 AM
|
0
|
0
|
1077
|
|
POST
|
Hello, With regards to the error being received, I have run into this type of message before. Please ensure that you have your GPSCorrect.ssf file in the exact same folder location as that of the .AXF you are checking in from and that the .ssf file is spelled the same as above. I hope this helps you out. Thank you.
... View more
05-01-2012
11:27 AM
|
0
|
0
|
1077
|
|
POST
|
Hello, The best location for assistance with ArcPad Studio, as far as documentation is concerned, would be to go to Start > All Programs > ArcGIS > ArcPad 10 > Developer Help > Customizing ArcPad. This documentation provides examples and explanations about the different types of controls on the Forms. Just type in the Search tab what you are looking for. Also, for further assistance, I would recommend utilizing the ArcPad Samples. For the Redlands Sample, for example, you could open the Trees.apl in ArcPad Studio and be able to see how they set up their .vbs script and how they linked it with the Edit Form controls. I hope this helps you out. Thank you.
... View more
04-27-2012
07:11 AM
|
0
|
0
|
572
|
| 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
|