Latest Contributions by LanceCole

Dan,  Thanks for the great outline and intro to Spyder.  I had always used other IDE but after reading your blogs and comments it looks like this is well integrated with ArcGIS Pro and is a great IDE. I did run into one small issue setting Spyder 3.3.6  up on a new Pro 3.4.1 installation.  Upon starting Spyder, I received an error message that "an error occurred while starting the kernel".  Upon further investigation found the root error was "ModuleNotFoundError: No module named 'win32api'.  Looking back at the installation logs, +pywin32 was not included as part of the "conda update numpy"  statement when executed per my Revision 1 info.   A quick additional statement - "conda install pywin32" resolved the issue and everything is working great. Thanks again for all you do and your continued support. ... View more

Jamal, Based upon your script noted in this thread, you are using an update cursor that will apply to the original feature data when cursor.updateRow is called in line 29.  There is not an option to save the data in another feature as written.  This could be added or you can add additional code to make a copy of the feature class then apply the adjustment to the copy rather then the original data. Copy Features—Data Management toolbox | ArcGIS Desktop  ... View more

Adam Bourque, Are the points in the same feature class/service or different?  If they are in the same, you can select the points you want to adjust and apply a delta move using your control points to determine the adjustment values.  Take a look at Moving a feature relative to its current location (delta x,y).  The points are still not going to fall exactly on top of each other but you would likely be dealing with the accuracy of the instrument at that point. If they are in different feature classes or services you could experiment with applying different transformations to the points that may be applicable to the data.  See if one moves the data in closer together. Based upon your previous reply, you could have been using a base station that was a little too far away and an incorrect correction factor was applied.  As you noted, you could rerun the post-processing to see if that helps with the issue. One additional note, you still need to determine which point set is correct.  See if you can locate some imagery of the area that is higher resolution and accurately rectified or, better yet, if you have some survey grade data that can de used to cross check against.   ... View more

Adam Bourque‌, Is the 1m offset generally in the same direction (i.e. to the SW or NE) or is random?  If it is the general same direction, you may have a transformation error occurring or date/time issue with the post processing.  If the difference is in random directions, it is most likely an accuracy issue. ... View more

Kimberly‌,  Please take a look at the reply by Munachiso Ogbuchiekwe to the following GeoNet post: How can I get a List of ALL TAGS in my Organization?  ... View more

Adam‌, As you are post processing your data it is going to be difficult to determine the accuracy of your data in the field.  Even if a control point checks out, when you go to collect a point there are many factors that can degrade your signal introducing potential errors.  These can include cloud cover, solar interference, time of day, number of satellites, receiver obstruction such as tree cover or buildings, signal bounce, etc.  The first part of this list is partially addressed when you apply the post-processed correction but the later items are not.  Furthermore, the later part of the list can be hard to detect when it occurs. Considering a RTK solution using a hot spot or other cellular device to provide you with real-time feedback as to your current accuracy and confidence level would be the best solution.  Other satellite based RTK solutions are also available depending upon your location, needed accuracy and how long you can occupy the collection point.  Even then accuracy can drop off and not be detected, especially with signal bounce. Depending upon your needed accuracy, you can check your points against high resolution aerial imagery if you have that information available.  Control points are a great check for gross errors but, as noted above, do not address localized errors.  Your post processing should also provide you with relative horizontal and vertical accuracy data.  This unfortunately cannot look at the individual satellite data to help in picking up localized data errors that RTK can help in detecting. ... View more

Ross‌, Let's try this again... 1) Create a new ArcGIS Pro project called "LogSample" using a just a Map template.  Make sure to check to create project files. 2) Save the two CSV file to a easily accessible location such as your Desktop.  Anywhere is fine as long as you know where they are located or if you already have them accessible. 3) Using the XY Table to Point tool in the geoprocessing tab set: Input Table - point to the Rutherford Core Location.csv (on my Desktop can be on any drive) Output Feature Class - point to the LogSample.GDB that was created when starting the project and set the feature class to CoreLocation X Field - Easting, Y Field - Northing, Z Field - Surface Coordinate System to NAD83, StatePlane Tennessee (US FT) and NAVD88 (Height).  Note, you may need to clear both the vertical and horizontal to None before trying to set the state plane system.  This dialog can be quirky while setting the parameters. Click Run, accept the transformation and this will add the points to the map as 3D points You can see "CoreLocation" feature class has been added to the map as well as the "LogSample" database. 4) Next lets add the core log CSV to the database as a Table.  In Geoprocessing, open the Table to Table conversion tool.  Set the following: Input Rows - browse to the RutherfordCore Log.csv location and select the file Output Location - Browse to the LogSample.gdb and select the database Output Name - Input "CoreLog" Click Run, this till create a table in the LogSample.gdb and add the table to your map You can now see the CoreLog table added to the map and LogSample.gdb.  This is not the CSV file but an actual table in the GDB. 5) Now you can create the relate in the project.  In the Geoprocessing widow open the Add Relate tool and set the following parameters.  One big note here - this creates the relate in the project not the database therefore it is not accessible outside of the project.  You can also Create Relationship Class in the database that will persist outside of the project.  For simplicity, I am construction the relate in the project.  Layer Name or Table View - select "CoreLocation" from the dropdown Input Relate Field - select "Drillhole_name" from the dropdown Relate Table - select "CoreLog" (should already be selected automatically) Output Relate Field - "Drillhole_name" Relate Name - leave as Relate1 or choose what you would like to name the relate Cardinality - "One to many" Click Run, this will add the relate to the "CoreLocation" feature class linking to the "CoreLog" table The relate completed and as you can see, nothing is added to the CoreLocation attribute table.  As noted previously, related data is not visible in the attribute table for the feature to which the data is related. 6) To view the data we need to make a few changes.  You should currently have two attribute tables open - CoreLocation and CoreLog.  Select the CoreLocation attribute table and click on the three bar stack in the top right corner of the attribute window.  Once the dialog displays, check or turn on Select related records.  If it is already checked you are good to go. Select the CoreLog attribute table.  In the bottom left corner turn on the Show selected records filter.  Once checked, no records should now be displayed rather then all. 7) Leaving the CoreLog Attribute table active, go to either the Map or Edit ribbon.  Click on the Select tool and select one of the core location points in the map.  The CoreLog attribute table should automatically filter displaying the core information applicable to the selected location. Select another location and the CoreLog attribute table will automatically adjust to the new selected location.  There may ne a slight delay as the program filters. 😎 Another way to view the related data is to use the Explorer tool.  Go to the Map ribbon and select the explorer tool.  Click on one of the core locations in the map and you will see the information show in the pop-up windows.  You can drill down through the Pop-up data to see the related dat by clicking the arrow next to the listed info.  Unfortunately the attribute table does not update using the Explorer tool. 9) To get the best of both worlds, go back to using the Select tool as in #7 above but this time also open your attributes window (not the table - the window) by clicking on "Attributes" on the Map or Edit ribbon.  When you select a core location point in your map it will not only update the attribute table display but the attribute window as well.  You can even edit the data in this window or the main table. 10) One more tip then I will stop so I do not overload you totally.  In your Contents windows right click on your CoreLog Table and select Properties.  Navigate to Display then click on the "Set an Expression" button next to the Display field option. Once the Expression Builder displays enter something along the following to customize the Display Field.  This is in Arcade scripting language var depth = $feature.Top_Depth +"-"+ $feature.Bot_Depth; Concatenate([$feature.Strata_name, depth],", ");‍‍‍‍ The Attribute Window will now display the depth range and strata name rather then the drill hole name for the core log data.  This is a little more useful and fully customizable. I hope this answers your question and you can work through the process.  Working with relates takes a little getting use to as you cannot directly see the data.  You can also create a customized Pop-up to display the information in ArcGIS Pro or even AGOL.  Information is available at Customize pop-ups | ArcGIS Pro.  However, that is a question and an answer in itself. I will send you back a ZIP file containing the ArcGIS Pro project I just build using your data sample. Have a great evening/day ... View more

Ross Harvell‌ The first thing I noted is I only see one table in your TOC and I also do not see the points feature class.  Unfortunately, I cannot see all of the path so I cannot tell if the one table is in a GDB or it is a CSV.  Also, in item 2 of your post you noted you created a "join" but you show the relate tool and have created a relate.  Again, you cannot see related data in a table like you do joined data.  You need to use other tools to view the data such as the "Select Related Data" option in the attribute table or the "Explore" tool once it is related to a feature class. Can you provide a copy of your CSV files (or a small sample of the two files that contains related data) and what coordinate system the data is in?  I will gladly take a look at the data this evening and put together a more detailed workflow using your own data.  This will also allow me to see if there are other possible issues.  If you do not want to post your data online please provide an email address and I will reply to you personally. To upload data to GeoNet, save your two CSV files as a ZIP and reply to the post here on GeoNet.  Once you open a reply, click on the "Use advanced editor" at the top of your reply dialog.  This will enable the option to attach documents at the bottom of the dialog. ... View more

The 2007 driver has been depreciated, you need to install the Microsoft Access Database Engine 2010 Redistributable from Official Microsoft Download Center to work with Excel and Access.  It is needed for interoperability between Office applications and third party application such as ArcGIS.  Your IT department can include this as part of their MS Office deployment based upon group policy for GIS users automatically. Additional info on the needed driver is available at Understanding how to use Microsoft Excel files in ArcGIS—Help | ArcGIS Desktop  ... View more

John Diaz‌, Try importing your shapefile into a GDB as a table before preforming a Join or Relate.  This can be completed many ways, such as from Catalog, right click on your GDB and select Import > Table(s).  Then perfor the join on this table in your GDB not the CSV. ... View more

Ross‌, First, sorry I thought you were working in 10.x not Pro. Second, when you added the tables, did you import them into your GDB as a new table or just add them to your project as CSV?  Click on the List by Source icon (second one at the top of your TOC) and see if they are listed under your GDB or just a file path.  Make sure you are selected this table in your GDB and not the actual CSV when performing the Relate Third, my bad here for assuming you were on 10.x.  Show related data is in a different location in Pro.  Click on the three bar stack in the top right corner of the attribute table for your boring point data.  Select Related Data > Name of your Relate (Relate1 ??).  This will open another attribute window with the related records.  Take a look at View related data - ArcGIS Pro.  You can also set ArcGIS Pro to automatically select related records when one of the key records are selected. ... View more

Ross‌, The pictures did not upload, can you please edit your response. To insert images, you need to use the tool in the response toolbar. You will not be able to see the related data directly in the point layer attribute table, disadvantage of a relate.  In the top corner of your attribute table there should be a button called "Related Tables" when you hover over it.  When you click the drop down the relate you created should be listed, click on it and it will display the related records in your core log table. Also, make sure you created the relate between the boring point feature class and the core log table and NOT just between the two underlying tables. ... View more

Andrew, After thoughts, How long does the calculate field tool run each time i.e. first time when it works and second time when it does not.  You can view this from the "View Details".  If the first run you do, say Cell1 * Cell2 and place that in Cell3 works, what happens if you run it again as Cell1 +!Cell2 and place that in Cell3, does it run correctly? Is it just one particular field you are having issues with?  Have you tried to delete the entire column from the feature class and add it back in and then rerun the calculate field? And one more, Check if you by chance have any duplicate alias field names in any of your tables or feature classes. Its late, I am done.  Have a great evening. ... View more

Andrew, Let me see if I can find the info on that previous bug.  I think that was clear back in 2.2 though and has most likely been resolved.  You are not trying to update a joined table field, correct.  You are only using the joined data to update fields in the feature class to which the data is joined. ... View more