Latest Contributions by DrewFlater

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

The way that comes to my mind is you will need to cut up your video into chunks so it is multiple video files. Then you can add the videos as geodatabase attachments to the points, either interactively through editing, or in batches using the Add Attachments geoprocessing tool (assuming the video files are named in an easy way to match an ID of the point each video should be attached to). Once the attachments are ready, you can use the popup tool to click on a point and watch the video. I did this exercise, not with video, but with an audio track and it worked quite well. ... View more

As Nobbir said, both formats are supported Using tools in Python—Geoprocessing and Python | ArcGIS Desktop  We include both syntax options to support different preferences for running tools - some people prefer to think of every toolbox as a Python module, which is a more Pythonic way of executing functions - arcpy.toolbox.tool(). However we wanted to support arcpy.tool_toolbox() as well since this is the legacy syntax from the old arcgisscripting, and some people prefer to have this flat list where you do not need to know the toolbox a tool is in to access it. ... View more

Hi Jay, further protections against the crash and PYTHONPATH system variable have been added in the ArcGIS Pro 2.3 release. When the release is available, can you give it a try in your environment and see if the issue is addressed? Thanks ... View more

This bug with Apply Symbology From Layer not working in Python has been fixed in the ArcGIS Pro 2.3 release. For reference you can use Esri bug BUG-000106281. ... View more

Hi Ezi, Can you describe this further: "let me flatly say that ArcGIS Pro thinks too much before executing any type of geoprocessing" I am guessing that you mean validation in the tool is taking too long for a tool you are running? After you input some values into a geoprocessing tool, and before the tool is run, the framework evaluates that the values you entered are valid given the requirements of each parameter. If you can provide an example of a tool or tools that take a long time to validate in your workflow we will look into improving them. Thanks, Drew ... View more

Regarding problems with AddField, Merge, or TableToTable when running the script from Pro, would it be possible for you to get in touch with tech support on this problem? It sounds like a severe bug that we'd like to have analyzed by tech support and sent to development to fix the issue. You could also post the failing script and some sample data here if you have a set of steps that consistently shows the problem. Thanks ... View more

Analyze Tools For Pro runs Python2to3 to determine syntax updates to make, and this is the best available automated method from the Python community to see the changes required to run code written for Python 2 in Python 3. Analyze Tools For Pro also performs simple checks for arcpy functions or modules that are not available in ArcGIS Pro. These two checks have been very successful in getting many scripts written for ArcMap to work in ArcGIS Pro, but additional things not captured by the tool could definitely be encountered. However, we haven't heard about anything specific through tech support or other forum posts. If there are specific things you have found that require try excepts to get it to work in ArcMap and Pro, please post it here and the Python experts can evaluate and give feedback (and we can potentially integrate such logic into the Analyze tool). Thanks, Drew  ... View more