Latest Contributions by LanceCole

Alexander, So by raw data you mean you only have a scanned or hard copy of the map?  No GIS digital data points, correct? As you know but for others, the strike is the orientation or rotation of the symbol on the map the dip is a number listed next to the symbol indicating the steepest angle of plunge.  On a map oriented with north up,  a strike and dip symbol oriented straight up and down the page, the strike would be 0 or 180 depending upon the side of the dip.  A strike dip symbol oriented straight across the page would be 90 or 270 depending upon the side of the dip if using azimuths.  I would recommend georeferencing your map into ArcGIS as you have coordinates for the corners.  Once georeferenced, add a strike and dip symbol for each point on the map then rotate the symbol to align to the symbol on the map.  You can also add the dip info as an attribute.  The orientation of the symbol can be extracted from the data and populated as an attribute.  Sorry but no automatic way to complete this but there are not that many points on the map you attached. Here a few links for georeferencing and symbol rotation:     Fundamentals of georeferencing a raster dataset     Rotating point feature symbols ... View more

Hi Alexander Do you have a sample of the data you are working with?  Unusual data would contain the dip without the strike.  I assume the data is in point format, is there a rotation value for the points that may correspond to the strike?   ... View more

1) can you please provide the link to the datasheet you are referencing.  I would like to use something you are actually utilizing to expand my reply. 2) if your surveyor has a survey grade GPS rover pole, have them shoot a series of points over an area that is readily  accessible.   I like the center of manhole covers because they are easy to find, big, do not move and can often be seen in imagery.  Shoot how ever many locations you would like to use as check points using averaging for a few minutes at each location.  Repeat on another day and average the results.  You now have a known set of points, in a known coordinate system that you can check your data transformations against. 3) the GNSS metadata that is stored with your collector data contains the latitude, longitude and altitude (height above the ellipsoid) in the coordinate system your GPS is running.  I use this data and project to coordinate system were are using.  I am really looking forward to Collector support for 3D points using our GPS.   ... View more

Oh the joys of data transformations. 1) you needed to lookup the data sheets for NGS Survey Control Monument you are using.  These will list the coordinate system and datum used for the published data.  They may be different depending when the monument was set and/or last verified. 2) make sure you are collecting the correct data using your equipment.  I am fortunate in that I have access to in-house survey control data specific for my location in a known coordinate system and datum.  Check with local surveyors, county map office for survey pin data on plats, state monument boxes for roadways, etc.  You only need a few points to cross check against.   3) selecting a transformation - I keep our collected data in the datum we work with for our GNSS, in our case NAD83 (2011).  I transform the control data to this system for verification.  This can be difficult but typically common sense prevails.  You know what system your data is utilizing and what system your control was collected with, what is the most logical path between those two. I prefer ArcGIS Desktop for the aspect of determining as you can load your data in and set the data frame coordinate system along with transformations for other systems. The transformations can readily be changed in Desktop whereas I have not found this functionality in Pro.  Once you have your data loaded in a MXD add your control data and play with different real-time transformation to see what works best.  In our case our control data is in NAD83(1987) but our collector works with NAD83(2011).  We found a combo transformation of NAD83(1987) to NAD83(HARN) to NAD83(2011) worked the best. 4) signs of a transformation issue     a) all your data is shifted the same distance and direction, within the accuracy of the data     b) a gradational shift such as data to the north is shifted NE, central data appears to be accurate and southern data appears to sifted to the SW.  Another example is data to the north appears accurate but as you look at data further to the south a larger shift is noted in some direction and increases the further south you go.     c) some pattern in the data differences 5) accuracy issues - if the differences between your data and the control points are random most likely you are not looking at a data shift but rather an accuracy issue.  You need to know the limits of your equipment and the control data.  Keep in mind if your equipment is rated accurate to 6 or 12 inches that is typically a plus or minus.  You need to double those values and not be looking for cm accuracy. ... View more

Alina, I am not going to be able to help much.  I have not had the opportunity to try the new z-enabled capability of Collector for ArcGIS (v19.0.1).  This is primarily supported with the Arrow/EOS receivers and software and we are using Leica receivers that, unfortunately, have not caught up yet.  Your workflow outline appears to be sound based upon my understanding. The main issue with data obtained from Collector is "What coordinate system is my data in?"  Going from a GPS receiver, running on various RTK systems, on different coordinate systems, that each manufacture integrates differently with Collector, pushing to AGOL, that uses base maps in one coordinate system but allows you to publish your features in another, back to ArcGIS Pro that does not clearly define which coordinate system it is currently working in, and the fact that there are hundreds of possible combinations of coordinate transformations, all to have your data not appear where you think it should be appearing, or is the data right and the map/image wrong.  No wonder it is confusing. One thing I can highly recommend is to create a set of control points.  I have two sets I use, one is a small number of points around the office neighborhood that I can quickly go for a walk, on a nice spring day, and test a new collector map.  The second is about 24 points over a large area that I can use to test at finer level that can catch things such as datum shifts that may not be visible on a small localized set of points. We collected these control points using a survey grade GPS, using the coordinate system we ultimately will be working with and typically using 5-10 minute averaging at each point.  The points have been collected at several different times and the results averaged.  I keep them in a shapefile or GDB feature class that is readily accessible. When I am working with a new Collector Map or trying to figure out is my new transformation workflow model working correctly, I go for a walk and collect these points.  Once collected I bring only the points into an ArcGIS session, perform my transformation workflow and then bring in my controls points to see how they compare.  Sometimes my collected data shows up in the middle of the Indian Ocean, other times it is a few feet off but most of the time it is within the accuracy of the GPS.  When it does not work I tweak my workflow and run it again, check my map or GPS configuration, recollect the points and check it again.  It is simple and quick and I am checking against a single absolute known. Working with multiple coordinate systems in you data is difficult.  We are in the process of migrating from NAD 83(86) to NAD 83(2011) the difference between the two systems can be 2+ feet.  The key here is to make sure you have the correct transformation assigned in ArcGIS between the two systems.  There is also a performance price to pay for working with multiple coordinate systems as some of your data needs to be projected on the fly.  This is most notable when it is your imagery that is being corrected. The best option is to work in a single system or as a second option work in your imagery coordinate system to minimize processing time.  Another option, if possible is to obtain a physical copy of the imagery, is to reproject the imagery to your preferred datum.  Just plan on some serious processing time depending upon the extent and image quality. Sorry I cannot specifically answer your question.  I hope this helps. ... View more

Correct, Collector does not work with vertical datums.  Additionally, the base map does not impact the raw data.  This is why you must use the raw data from your GPS that is stored in the Latitude, Longitude and Altitude attributes when points are collected to AGOL to create the 3D points and transform them to the coordinate system you ultimately need.  I believe these are store in the raw data format or configured data formate for all GPS units.  You may want to confirm this with Trimble, as we are using the Leica product line for our ArcGIS Collectors.  It is my understanding some GPS manufactures are providing full horizontal and vertical datum support but this is not via ArcGIS Collector but rather the apps provided by the GPS manufactures such as Arrow and EOS that integrate with collector. We we have our profile configured as shown below to work our State VRS system and post the data to AGOL as each point is collected in the field.  We work through the process we have been discussing to generate our survey points for internal use to the accuracy of the instrument. Our GPS receiver and State VRS are using GSC NAD 1983 2011 and we use the ESRI default for AGOL of WGS 1984 Web Mercator Auxiliary Sphere as our map coordinate system.  The transformation is the default Collector recommended for this paring. You may need to take a step back and insure you have your database configured, have added the GNSS enabled fields  and have it properly published to AGOL to be collecting the correct data.  This must be working before you can even think about performing the transformation on the data.  You also need to be sure your GPS software is also properly configured in conjunction with Collector.  I am not going to be much help with a Trimble unit, as noted above, we are using Leica.   Also, do you have RTK enabled and configured for your GPS.  This will substantially affect the performance of your R2 unit.  That sounded like something out of “Star Wars”. Sorry, I currently only have a few moments to respond but can provide additional information later this evening, if needed or you have more questions.  This was not an easy process so please do not feel you are not qualified.  There are just a ton of variables that all need to be inline for everything to work.  Once it is working, it is great. Small steps: 1) make sure your GPS is configured correctly and you are received the correct data, including RTK outside of Collector 2) make sure the GPS is correctly communicating with Collector. 3) is the correct data being posted to AGOL with the correct GNSS data 4) the data that is being returned back from AGOL is correct. 5) post processing is correct and using the correct transformations. ... View more

Randall, I looked into this a little further.  I found if I log onto Portal via the https://<Portal_server_FQDN>:7443/arcgis/home url, in our test sandbox deployment it is https://gisprt01.lgc.local:7443/argis/portal, all traffic is going through this path.  However, as soon as I go to the Status tab under Organization, it is using our web adapter alias for the path.  This is https://gis.lgc.local/portal on the test deployment.  This is resulting in the error shown as the path in the browser does not match the path being used.  The browser path is https://gisprt01.lgc.local:7443/arcgis/home/organization.html#status.  Go to another tab and it reverts back to the proper path.  So far, only fond this issue on the Organization > Status page on portal in both IE and Chrome. ... View more

Follow-up - I found if I clear the cache in IE and Chrome, the status page will load when using the FQDN of the web server hosting the web adapter.  https://<Webserver_FQDN>/<webadapter>/home but if I use the portal server https://<Portal_server_FQDN>:7443/arcgis/portaladmin or a pointer to an alias to the webserver https://<Alias_to_WebServer>/<webadapter>/home the status page will not load.  All other pages on the portal site appear to be working. ... View more

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