Latest Contributions by LanceCole

Still working through this issue.  Republished the feature service using a new GDB and ArcGIS Pro 2.4.0.  Created a new map for collector and tested again.  Still receiving the periodic multiple points being submitted and a have also seen the lose of Altitude values and RTK corrections being posted to AGOL from Collector.  However, when the loss of the information was noted the Zeno Connect app and GPS appeared to be functioning correctly but this information in Collector and submitted to AGOL was inaccurate. We are going to try another iDevice on Friday to eliminate one other possible source of the issue. ... View more

Kevin Burke‌ The issue is still persisting.  We plan on backing up the data collected to date and republishing the feature service from ArcGIS Pro as an additional test.  I did make the map and feature services available to you through a share on AGOL under the user account provided by ESRI Customer Support.  Please feel free to collect data to this map if needed for testing. ... View more

Kevin  Per ESRI Customer Support request, we created two new feature services, one using ArcGIS Pro and the other using ArcGIS Desktop 10.7. We then tested both of these by collecting about 100 points in each. No duplicate data points were noted in either set of points collected. We also collected about 100 points in one of the feature services we had previous issues with. Again no duplicate points were collected.   Was a change made to AGOL that might have addressed this issue?   We will try collecting field points again starting Monday to see if the issue is persisting. ... View more

Tirrell Brown,‌ We had a few hundred to fix before we caught the issue. Many had asset IDs for the feature so we could script moving the inspection to the asset coordinates but for those inspections we had not yet surveyed, using a high accuracy GPS, these had to be manually adjusted.  Learning curve  Most points were within a meter and close enough you could pair the inspection to the asset.  Others were over a 100 meters away and through the process of elimination we could figure out what is what.  Internal iPad GPS are great for driving from A to B but just are not reliable enough to for single point positioning work.   ... View more

Tirrell, It is my understanding Arrow/EOS supports the direct collection of 3D data via Collector to AGOL.  Other platforms  you are currently limited to 2D data but you are able to store the GPS metadata which includes the raw Latitude, longitude and altitude information that can be utilized to create the 3D data should it be needed.  This is the approach we are using.   Fixing the iPad GPS data was a pain.  We were using 123 Survey integrated with Collector to perform field inspections on assets.  Unfortunately the iPad GPS points frequently placed the inspection so far from the asset it was difficult to identify which inspection corresponded to which asset.  We modified or Collector map to pass the x, y and asset ID from the feature to 123 Survey and override the iPad GPS coordinates.  We had to manually identify the rouge points and correct their position using imagery and phots.  Fortunately, we have access to very high resolution aerial imagery and Google - Street view became our new best friend. Some were just deleted as we could not ascertain which feature it was.  We now no longer perform inspections on assets until after we have assigned an asset ID or have valid x,y data already collected. ... View more

Tirrell, I am a little late on this questions but thought I would post anyway.   We are using iPads and Leica GG04+ high accuracy GPS with RTK corrections via the iPad cellular to our State VRS system.  Overall we are very happy with the results typically in the 2cm accuracy range but can be variable as with any GPS dependent upon field conditions and location.  Data collected over the past two years has averaged within about 6 cm accuracy. For these types of setup, RTK is typically performed on the iPad via the app for your GPS being utilized.  The app takes your raw GPS data and using a web based service determines the correction needed for the point being collected at that time and location.  This can be performed after the data has been collected (post-processing) but as cellular is available almost everywhere real-time is the norm. One advantage the Arrow setup, noted by Ken Klopp above, is it supports 3D point data directly to AGOL via Collector if Z data is important to you.  Other vendors such as Leica and Trimble are still working on this but it is forthcoming.  Elevation or Z data is still available but takes some post processing to calculate from the GPS metadata Latitude, Longitude and Altitude (height above ellipsoid) information collected. One word of warning about iPad internal GPS - Don't. Yes, the data can be within a few meters but it can also be within a few 10's of meters.  We have had data show on the wrong side of the street or even the next block over. Hope that helps... ... View more

One additional note, the features we are collecting points for is published to AGOL using the NAD_1983_2011_StatePlane_Ohio_North_FIPS_3401_Ft_US coordinate system. ... View more

Hi Kevin, Thanks for the quick reply. Yes, this issue started immediately after the update was installed on the iPads and only a few duplicate record were noted in the prior two months of data.  Unfortunately, auto update was enabled on the devices it installed the evening of the 6/25. We only have one Leica unit but use multiple iDevices depending upon what inspections are being performed.  The issue has been noted on both.  They are iPad (5th generation) now running iOS 12.3.1. Zeno Connect is version 3.1.0.1383 dated 11/15/2018 and Leica GG04+ firmware v7.500 on the GPS.  As noted, Collector is version 19.1.0, build 2666, that was updated to this version the evening of the 25th from I believe version 19.0.1. Currently we are collecting only point features to multiple published feature services on AGOL.  The user locates a feature I the field, positions the GPS and presses the "+" button.  Depending upon the map, the user may need to select from various features and populate needed attributes.  The user then presses submit.  This is where they have reported, on occasion, submit will take an unusually long time with a rotating circle.  Once we have checked these points on AGOL we have found multiple points have been collected for a single submit all with the same attributes. These are online workflows that have been in use since April.  All data is collected and updated real-time without the use of sync. Since yesterday, we have not seen second item again but have stopped collection except for a small test this morning to see if updating the iOS resolved the issue.   Please see attached an Excel sheet with data from two of our feature classes for this week.  The duplicate records are highlighted in yellow and the orange are were the altitude values dropped off yesterday that also includes repeated data.  Note, there is only one repeated point prior to 6/25 compared to the substantial increase 6/26 and after.  The only change was updating to Collector 19.1.0. Case has been submitted to ESRI - Number 02353057 ... View more

After updating to the newest iOS 12.3.1 and insuring the most recent firmware is installed on the GPS we are still receiving periodic duplicate data points.  We have not seen the loss of altitude data again.  Putting a ticket in with ESRI. ... View more

As noted previously, what you see on my.esri.com is dependent on the type of license, maintenance agreement and your level of access. I would recommend contacting ESRI customer support for your location and have them help you.  You may not have access to e-Learning as part of your license/maintenance agreement or your account profile is not configured correctly.  Additional info is available at Get Started with E-Learning. ... View more

As your XY data is contained in the excel sheet, you will need to replace the data in your ArcMap system each time you want to work with the data. This can be completed manually using the AddXY data, script this using Model Builder or using a scripting language such as Python.  You could run a model on demand in ArcGIS to delete the current data and replace it with the info contained in the excel sheet.  The advantage of using Python is you can schedule this to run at specified intervals or on demand unattended.  Here is an example of a python script for XY spreadsheet to geodatabase using python.  You will also need to delete or truncate the previously copied data in your system prior to replacing it with the new data. Overwriting can be allowed in python using the arcpy.env.overwriteOutput = True in your script or you can just delete the feature.  I would also recommend working with a CSV file rather than an XLS or XLSX file.  Excel files can be temperamental. One other caveat, mind your coordinate systems and make sure the coordinate system in your excel data matches what you are working with in your ArcGIS system.  You may need to perform a transformation as part of your import workflow. ... View more

Siran Erysian, There is third option available if you can just use AGOL and do not have to use Collector. Feature data would be editable but the table data would not. Let me know if you are interested as it will take some explaining. ... View more

Siran, I confirmed that creating a relationship class for each feature class to a single table does work when created from one database.  Please insure 1) you created a relationship class for each feature class to the single table 2) you may need to create a single GDB with all the needed features contained in one for this to work.  It may not work with multiple copies of the table in multiple databases. Using the relationship classes, not the hosted feature layer view, the features and table are editable once enabled in the feature service   ... View more