Latest Contributions by DrewFlater

The ArcGIS Pro Profile Graph works with any 3D Line data - you do not need to run or use the Esri-hosted elevation data or Profile ready-to-use geoprocessing tool.  If you already have 3d lines, you just need to right-click the layer and select Create Chart>Profile Graph. If you have 2d lines and an elevation surface, you first need to run the Interpolate Shape (3d Analyst) tool to burn the z-values into the 2d lines - either at the existing vertices, or at a regular sampling distance. Now that you have 3d lines, you can use them with the Profile Graph chart. EDIT: Also wanted to point out that since March 2019, the Elevation and Hydrology ready to use services have been FREE- no credit charges to run the Profile, Summarize Elevation, Viewshed, Trace Downsteam, or Watershed ready to use services in ArcGIS Pro or any other client. https://developers.arcgis.com/rest/elevation/api-reference/get-started-with-elevation-services.htm#ESRI_SECTION1_D50801BCC66D40D094555B3221BA6D81 ... View more

Cole Andrews‌ unfortunately due to a technical limitation of the geoprocessing value table datatype (what is used in Add Fields multiple as well as many other geoprocessing tools) the state of the empty rows cannot be stored, they are automatically cleaned up as soon as the mouse focus leaves the first text box you are entering values into.  So we need to approach the problem from the perspective of putting the + button in a location that makes it easier and require less scrolling to access. Our current thinking is that at the bottom will require less scrolling and mouse travel to add many fields. ... View more

Hi, The bug you linked, BUG-000116163, is not fixed yet. It deals specifically with arcpy.MakeFeatureLayer_management() when arcpy.env.addOutputToMap = False.  If your script is only doing a CopyFeatures then it might be a different issue that the script is failing. You do say after the copy the script "performs analysis" so I guess this may include arcpy.MakeFeatureLayer_management? You might be able to rewrite some steps in your script, as Make Feature Layer is no longer required as a pre-requisite for many tools like Add Join, Select Layer By Attribute, etc, as of Pro 2.2. https://pro.arcgis.com/en/pro-app/get-started/what-s-new-in-arcgis-pro-2-2.htm#ESRI_SECTION1_68F7BAF048AE4EF096C802EB7FD68817 (see the second bullet point)  ... View more

Glad you are finding the Undo toggle button useful. ... View more

This came up in a previous geonet discussion https://community.esri.com/message/736034-applying-field-calculator-only-on-selected-features?q=calculate%20field#commen…  The issue was found to be caused by duplicate layer names in Contents, and the Calculate Field tool used the duplicate layer that didn't have a selection rather than the duplicate layer that had the selection. Can you confirm if you have multiple layers with the same name?  ... View more

Good can come from any post. We've fixed this now in ArcGIS Pro 2.4 alpha software so that if the input data is empty, Calculate Geometry returns a helpful error. Thank you for posting. ... View more

Mark Peacey Was the data interop you needed to uninstall installed before or after you installed ArcGIS Pro 2.3? Was it perhaps an older version of data interop, like the 2.2 version? ... View more

Hi everyone. I have always said better late than never, and thought it was worthwhile to update this thread as there are some familiar faces still active on geonet.... This enhancement has been complete in ArcGIS Pro 2.4 alpha software, for both standard tbx toolboxes as well as PYT toolboxes, so you can expect to see this working when the 2.4 final release is available (or if you sign up and participate in the beta program).  How it works .... you can define a value table parameter, much like discussed above, where one column is a feature layer, and a second column is a field. If this parameter has NO DEPENDENCY set, it will apply an intrinsic dependency between the field column and the layer/data column, to read and populate the field list from the data selected in the first column. Again this only works if the parameter doesn't have a dependency set on another parameter -- we want this dependency to be applied WITHIN the value table, not between the value table parameter and another tool parameter. I hope it makes sense. Attached a small video of the script tool properties and the tool dialog to help illustrate. ... View more

Duncan Hornby‌ a project package of your original project would be the most useful in this case. I am not sure what improvements can be made since moving the information model of large maps and layers between threads takes some time in Pro, but we will look at the case and optimize it as much as possible. Like I mentioned, you may find running Add Join in ModelBuilder will be significantly faster, as in that environment tools always run in the main foreground thread, so it does not require the overhead of moving the map and layer information model between threads. Running in standalone Python will be the fastest environment, with zero overhead. While your image only shows one open map, was it possible that you had closed other maps that were previously open in the same project session? If a map was never opened in a session, we shouldn't be loading the information model for that map and it's layers, which lessens the performance overhead of moving between threads. But if a map was ever opened in the session we still may be loading it's information. This is speculative at this point until I can troubleshoot further, aided by your project. Thanks Drew - Geoprocessing team ... View more

Just for the few people who commented about a third text box on the tool - this is the hovertip that displays when you hover on the path in the Output Feature Class. ... View more

I don't believe this is at all related to BUG-000118472. Smooth Line and some other cartographic generalization tools were recently enhanced with some additional options, I believe the performance bug may have been introduced at that time. Paul Dudley‌ can you contact tech support with this issue, or post that data in a zip file for us to troubleshoot? I also see that the layer names used as input in the two screenshots is different, perhaps these contour datasets are different with regard to level of detail or vertices?  Thomas Colson‌ the team is NOT aware of any global performance issues with geoprocessing in Pro. We fix individual tools like this geonet post describes as the reports come up, and as our testing finds issues. I don't believe I have heard any other report that all tools are slower in Pro, it is usually quite the opposite. ... View more

This bug is addressed in ArcGIS Pro 2.4 alpha builds. When "Project to WGS 84" is enabled, the output coordinates are in lat lon, rather than in their native projection (and no CRS/Coordinate Reference System is specified in the geojson, per the specification). ... View more

Bryan, can you access the path %localappdata%\Esri\ErrorReports on one of the machines that experienced the crash? You should be able to find crash reports with a timestamp of when the tool ran and crashed. If you can please send this file to me at dflater@esri.com, and/or upload it here to the post, I would like to troubleshoot the problem to see if it is solved in more recent software versions (as indicated by Dan). Thanks for your help! Drew ... View more

I think it is likely you made the script tool parameters as data type Feature Class or Raster Dataset. To support drag and drop of map layers, you need to make the data type Feature Layer or Raster Layer. ... View more

Just for the discussion about ArcGIS Pro, there are two options for logging your geoprocessing operations - A> with the data/metadata, and B> in an external XML file Geoprocessing options—ArcGIS Pro | ArcGIS Desktop  ... View more