Latest Contributions by LanceCole

I can emphasize with you.  I think it took a few months to get everything working on our collectors, AGOL and Z conversion. I had assumed you were collecting data to a GNSS enabled map you had published on AGOL when using Collector.  Is this correct?  If so, in ArcGIS Pro you can open the data stored in this published map and copy the data to a local GDB.  You can also logon to AGOL and export the data from there as well.  The screen shot below shows a new blank map in ArcGIS Pro and I am adding the data from our AGOL survey map.  To add the data form AGOL: On the Map Tab Click - Add Data Go to Portal > My Content and navigate to where your collector data is stored on AGOL Click OK This adds the collected data to your map so you can then perform the export to a GDB as a copy You can also go to AGOL and export the data as a GDB from there and skip this step.  you would just need to add the feature class from the exported GDB to your ArcGIS Pro session. ... View more

On my.esri.com go to: My Organizations > Downloads Select the "View Downloads" button next to either ArcGIS Pro or ArcGIS Desktop Scroll down to the Data and Content section Click the Download button next to "ArcGIS Coordinate Systems Data" Mine is showing the current version being 10.7.167057 Your my.esri.com page may be slightly different depending upon your licensing but this should get you close. ... View more

Jeff,  Any word on adding support for capturing Z values directly into a z-enabled geometry?  Collector is working great but the need to perform post transformations on the GPS metadata to get true 3D data points can be problematic.  It would also be great to see the actual elevation in the field rather then the HAE data.  We are using a Leica GG04+ with RTK. Lance  ... View more

Don,  I moved my reply to your new question here and will continue our dialog.  Below was your last reply: Don Rodgers @ Lance Cole on Apr 3, 2019 7:47 AM Lance, thank you for your quick and thorough response. I can clearly see that your knowledge base and experience far exceeds mine, but I will try to keep up. In response to your follow-up questions: When I say NAD 83 I mean that the Seiler Rep who walked me through the Trimble R2/ArcGIS Collector setup had me enter NAD 83 2011 as the GNSS Coordinate system and as the "to" system in my Datum Transformation box in my Profile. All the data that our organization stores on our in-house databases is NAD_1983_StatePlane_Indiana_East_FIPS_1301_Feet. On the vertical data I ultimately want my data to be in US Feet. With respect to metadata fields what I have done is to add metadata fields to a published Feature Service Layer and then added that new Feature Service layer to my Web Map. I have attempted to Configure a feature service to store GPS metadata. The obstacle that I encountered is that the instructions indicate that I should add field names to my feature attribute table and these field names are longer than that field will accept. Helpful Yes • NoLike • Show 0 Likes I will update my original answer later tonight to reflect the additional information you just provided.  The first step you need to complete is getting your Trimble R2 parried with collector and pushing the correct data to ArcGIS Online (AGOL) database that is configured for GNSS data.  Please take a look at Record GPS metadata for Classic or  Prepare for high-accuracy data collection. It sounds like your Trimble unit is configured to use a geographic coordinate system of NAD 1983 (2011) and a ellipsoidal-based, vertical coordinate system also of NAD 1983 2011.  This is common for this type of system.  Once you have the data configured in your database, Collector will store the "Raw" GPS data from the unit in the Latitude, Longitude and Altitude fields for each point collected.  What the process described above does is take that raw data in GCS_NAD_1983_2011 / VCS: NAD_1983_2011 and using the tool "ProjectZ" creates new feature class of 3D points in NAD_1983_StatePlane_Indiana_East_FIPS_1301_Feet / NAVD 1988 (meters).  You then run a "Project" tool of the data to convert the NAVD 1988 in meters to US Feet and "Add XY Coordinates" to display the Northing, Easting and Elevation data in the attribute table.   ... View more

I will reply to your new question posted at Is it Possible to Collect Accurate Z Coordinate Values with Collector and Trimble R2.  I will also be deleting my response below and moving it to your question. ... View more

Don, Below are the instructions to convert the HAE to actual elevation transformation from the data obtained from high accuracy GPS using Collector.  I have assumed the following: You have configured the database receiving the data to support the GPS metadata.  In particular the ESRIGNSS_LATITUDE, ESRIGNSS_LONGITUDE and ESRIGNSS_ALTITUDE fields.  If you have not, this can easily be added using the Add GPS Metadata Fields tool in ArcGIS Pro. I can also provide additional instructions, if needed. You stated your GPS is configured or is receiving data in the GCS NAD 1983 (2011) for horizontal data and I am assuming it is configured to receive vertical data in an ellipsoidal based, North American NAD 1983 (2011) datum coordinate system.  It is critical that you have the correct coordinate systems for this data.  ArcGIS collector stores this raw data in the Latitude, Longitude and Altitude fields noted above. Insure your coordinate systems have been updated.  Go to my.ESRI.com and download and install the Current ArcGIS Coordinate System Data - I believe the current version is 10.7.10000.  You can check your Windows Control Panel > Programs and Features to see if this is installed. If you have not already, go to the Github ESRI / Collector-tools site and download the tools for collector.  I recommend you download the entire tool set using the Clone or download button, save and extract to a common location. Now lets get to the actual transformation of the 2D data stored in ArcGIS Online (AGOL) to 3D data with the correct elevation data.  Open ArcGIS Pro and load the original AGOL data into a map. Right-Click the feature and select Data > Export Features and point to a local GDB.  You will be working with is local copy of the data. On the Insert Tab select Toolbox > Add Tool box Navigate to the folder you downloaded from GitHub and add CollectorUtilis_Pro.tbx.  This should be located in the folder ...\collector-tools-master\CollectorUtils\pro Go to Catalog in ArcGIS Pro and select Toolboxes > CollectorUtilities_Pro.tbx > GeneralUtils > ProjectZ In the ProjectZ tool, select the newly created feature Class in the local GDB for the Input Features.  Mine is called SurveyPointFeatures_Copy for this example.  A warning triangle will appear as the data does not have z data - ignore For the Input Coordinate System - Click on the globe and select the following for Current XY and Z - based upon assumptions above Click on the Current XY box then select:     Geographic coordinate system > North America > USA and territories > NAD 1983 (2011) Click on the Current Z box and select:     Vertical Coordinate System > Ellipsoidal-based > North America > NAD 1983 2011 Click OK Confirm the X-Value is set to the Longitude field, the Y-Value is set to the Latitude field and the Z-Value is set to the Altitude filed.  These should populate by default. Enter an output feature class - I used "SurveyPointFeatures_ProjectZ" in the same GBD For the Output Coordinates - Click on the Globe and Input the following for Current XY and Z - based upon assumptions above Click on the Current XY box then select:     Geographic coordinate system > North America > USA and territories > NAD 1983 Click on the Current Z box and select:     Vertical Coordinate System >  North America > NAVD 1988         Select NVAD 1988 even if you want ftUS.  It is not possible to directly translate to NAVD88 (height) (ftUS) Click OK A Geographic Transformation will automatically populate, you can change to other options but typically this is the optimal transformation for the Input and Output coordinate systems entered into ProjectZ Click "Run" - This will use the Latitude, Longitude and Altitude fields to create a new feature class as named above in NAD 1983 and NVAD 1988 as 3D data points. If you need to convert the elevation data to US Feet, continue with the following. If you only need elevation in meters skip this step.  This step is only converting the NVAD 1988 in meters to NAVD88 (height) (ftUS) In the Geoprocessing tab search for and select the "Project" tool, it should be in the data management tools For the input Feature Class select the feature class created above - SurveyPointFeatures_ProjectZ in my example Input a new feature class name for the Output Feature Class - I chose SurveyPointFeatures_Feet For the output Coordinate - Click on the Globe and Input the following for Current XY and Z Click on the Current XY box then select:     Geographic coordinate system > North America > USA and territories > NAD 1983 Click on the Current Z box and select:     Vertical Coordinate System >  North America > NAVD88 (height) (ftUS) Click OK Check the Vertical Box Click Run One last step.  In the Geoprocessing tab search for and select the "Add XY Coordinates" tool, it should also be in the data management tools Select the SurveyPointFeatures_Feet or SurveyPointFeatures_ProjectZ feature from above and run the tool.  This will add X,Y and Z data to the feature.  Open the attribute table and the added Z value is your Elevation in feet or meters depending which feature you are using. I hope this helps you with adding the elevation data to your data.  As noted previously, please double check the coordinate system your GPS is running on.  This is critical for accurate translation.  You can also select a different output coordinate system if I assumed the incorrect system.  For example we output to a projected coordinate system rather than a geographic system.  So we set our Output Current XY to Projected coordinate system > State Plane > NAD 1983 (2011) (US Feet) > NAD 1983 (2011) StatePlane Ohio North FIPS 3401 (US Feet).  This will return Northing, Easting and Elevation, rather than Lat, Long and Elevation.  Lance ... View more

Excellent, I will write up a quick "How-To" this evening using your information. I do have a few more questions When you say NAD 83, I assume GCS_North_America_1983, WKID: 4269? On the vertical data do you want the NAVD 88 to be in Feet, US FT or Meters? I am also assuming you have configured your database and are receiving the GPS metadata with each point when collected to AGOL, correct? ... View more

I would be glad to help.  A few quick questions.   1) do you have access to ArcGIS Pro?  It is not needed but the approach is different between ArcGIS and ArcGIS Pro. 2) what corrodinate system is your Trimble R2 configured? 3) what corrodinate systems do you want your final data to be in? ... View more

Thanks for the input.  Sill been rebuilding my sandbox to test this again.  Going to make a full backup this time before attempting to connect anything together.  We currently have one ArcGIS Server and one Portal server in our production environment.  The ArcGIS server is federated to the portal and a hosting server to a ArcGIS Datastore.  The ArcGIS Server is also referenced to an enterprise geoDatabase. Everything is running great. We want to add a two additional ArcGIS servers.  One to share the processing load and one to run as an imaging server.  Also adding a file server for hosting shared ArcGIS Configuration files, image files, etc.  Every time I try and connect and federate the servers everything goes to pieces.  It is most likely the order that I am connecting everything together or federating the servers. I did learn that for multimachine site a webadapter for ArcGIS Server is required. Note: If you federate with a multimachine site or highly available ArcGIS Server, or if your ArcGIS Server is hosted in a cloud environment, use the Web Adaptor or load balancer URL in this field instead. The Administration URL setting must be a URL that the portal can use to communicate with all servers in the site, even when one of them is unavailable. If you use a Web Adaptor for this URL, ensure that you have enabled administrative access to the server through the Web Adaptor. Source: Federate an ArcGIS Server site with your portal I also learned that you MUST disable IWA on any ArcGIS server BEFORE federating. If you have an existing ArcGIS Server site that is using IWA, you must disable IWA on the ArcGIS Server site before you can federate it with your portal. Follow the instructions in the section below to disable IWA on your server before proceeding. If your ArcGIS Server site is not already using IWA, you can skip this section. Source: Setting up your portal and federated server to use Windows accounts Currently, I have the following built on separate VMs but nothing configured or connected together: Web Server with a "Portal" webadapter and "Server" webadapter ArcGIS Server 1 ArcGIS Server 2 ArcGIS Server 3 with Image Server Extension ArcGIS Portal ArcGIS Data Store SQL Server with a GeoDatabase created File Server with Image data, and shares created for ArcGIS server directories and configuration store Domain ArcGIS Server account created with appropriate permissions to the shares, data and system All servers have needed SSL certificates from an appropriate CA to fully support HTTPS What order is best to connect these together, implement windows based identity stores, register file shares and enterprise databases, federate which servers and set a host server?  We will may add an additional web adapter for the Image server and keep it separate from the other two (Yes/No?). Any input would greatly be appreciated. ... View more

SFC or System File Checker is available as part of a typical windows installation since at least Windows 98.    The command does need to be ran from an elevated command prompt so the user does need to have these rights.   I do want to add, SFC is checking the Windows OS files and has nothing to do with the ESRI product line.  We had had an issue with installing a windows update back in August of 2018 and I believe some of our system files became corrupted during the recovery at that time.   ... View more

After upgrading to the newest release of ArcGIS Pro (2.3.1) and still having issues with Pro crashing, hanging and quirky behavior we decided to start over.  After uninstalling and reinstalling 2.3 and the 2.3.1 update. Pro hung on the first attempt of opening a project.  We then installed Pro on a new system we had just received, no issues. Looking back to the system we were having issues with, we ran sfc /scannow from an elevated command prompt to discover numerous errors.  System File Checker was able to repair the errors and upon restarting we are able to open and use ArcGIS Pro without any issues.   ... View more

Once you purchased the software you should have received an email confirmation with the link to the downloads.  Depending where you are located you can try: my.esri.com or accounts.esri.com Once you have signed in, using your ESRI credentials, there should be various tabs for download and licensing.  Mine are under the "My Organizations" tab but I have an enterprise license. Start with the Desktop 10.x version installation and add the other needed components.  The Desktop install covers the majority of the needed components. ... View more

To what coordinate system was your base map generated? What coordinate system are you using for the data in Survey 123? Are differences generally in the same direction and distance for all points? Coordinate systems need to match or you will have a tranformation error.  These errors are typically in the same direction and distance. Are you manually placing the point locations or using the internal GPS of a device?  Many GPS units in mobile devises can have substantial errors dependent upon time of day and satellite positions.  These errors will typically be more random in direction and distance.  I have seen 10-15 m errors from iDevices. ... View more