Latest Contributions by DrewFlater

Dana Thompson‌ Ted Hallum‌ can you explain the versions you are using of ArcGIS Pro and ArcGIS Enterprise?  The only case where I have seen this happens if if there is a tool inside of your script or model that has a fundamental change in Pro that isn't available in Enterprise. For example, say a new parameter was added to one of the tools in Pro 2.5, if you are publishing to an older version of Enterprise such as 10.7 it will have no knowledge of that new parameter and problems will ensue. Analyze does have checks for new tools and new parameters, but sometimes changes are more subtle and slip through the cracks.  There are also some basic compatibility rules between versions of Pro and Enterprise when it comes to web tools: Web tool compatibility—ArcGIS Pro | Documentation .  If either of you would be able to provide your model/script with a sample of the data you are using as input, we can try to debug the problem further. Email dflater@esri.com , I can get you set up with a cloud share to upload data if it is too big to email. ... View more

There are multiple things going on here. Natalie Robbins‌ correctly identified she had a custom Python toolbox in the system toolbox directory, and that ENVI toolbox likely didn't have the correct libraries to work with the updated ArcGIS Pro 2.5 Python environment. Installing 3rd party toolboxes into your system toolbox directory can have these negative effects when moving between Pro versions.  William Mayr‌ had you previously cloned and made a custom Python environment? Environments need to be repaired or re-cloned when updating versions of ArcGIS Pro. The Intelligence Tools PYT toolbox is not the problem, that just happens to be the first Python functionality that the application is trying to load, as the system loads all the system toolboxes alphabetically (that is alphabetically the first toolbox in the system toolbox directory built with Python). Removing that PYT will just make the next one in the system toolbox directory fail. You have an underlying Python environment problem that must be remedied to proceed. You may want to contact tech support if none of this Python environment stuff that I mentioned applies to you ... View more

Hi Rickey Fite‌, The mean is an area-weighted mean of those four buildings. The building that has the most overlap will contribute more towards the mean. Based on your pictured values and the output mean value it is very hard to tell if the value is correct, there just isnt enough information. We need to know the area of overlap between the highlighted circle and each building that intersects it, then we weight those buildings values by how much of the total overlap they contribute. If you want me to double check the match and send you the results, send a sample dataset to dflater@esri.com.  The mean WILL NOT be the average of (35.33333+46.5+44.83333+38.66667)/4. Doing an average like this throws away the spatial component of the analysis, since each of those buildings spatially overlaps the highlighted circle different. If you want a simplified result that does the basic average I just described, Spatial Join can accomplish it using a MEAN Merge Rule. Spatial Join—Help | Documentation  ... View more

Multiple field names can be given in a Python list: ["FIeldA", "FieldB", "FieldC"] ... View more

Thanks for your feedback. We avoid the kind of popups you described in ArcGIS Pro. But I agree it could be more clear that the tool will modify the input dataset, and you may wish to have a visual reminder to enable undo if that is important for you. It will likely be designed as a banner at the top of the tool that can be dismissed at any time, and links to the documentation about tools that modify the input dataset, and strategies for avoiding unintended data modification.  ... View more

Briana Mercuri‌ there isn't a way to restore one attribute that the geotagged photos to points tool produces. Since you've made changes to the points layer that you want to keep, an acceptable workaround that comes to mine is: 1. rerun the geotagged photos to points tool, which will generate the output including the direction field 2. run Join Field to move the DIrection field from the new output back to your original output point layer, based on the common "Name" or "Path" attribute in the geotagged output feature class. I hope the workaround might work for you! Good luck ... View more

David Wheelock‌ you are correct. In Pro 2.5 you need to run your model inside ModelBuilder to see all the verbose messages. We consider the messages from the tools inside the model to be debugging messages. Those standard processing and command line messages do not bubble up when running the model as a dedicated geoprocessing tool. We received feedback that large models delivered too much content with verbose messages due to every tool returning its command line execution syntax plus messages about when each tool started and completed, when the user was really only interested to see that the entire model tool completed, or warnings and errors. Those detailed verbose messages are important for some situations like debugging the model or profiling the performance, in which case you can run inside the model debugging environment - ModelBuilder - to see those messages. ... View more

Chandler Callison‌ sorry you are experiencing this performance problem. Would you be willing to share your project package? We would like to troubleshoot the issue. Send to dflater@esri.com, or contact tech support.  ... View more

If you need to have multiple parameters be different in the batch operation, I suggest to simply use the normal version of the tool, and use the geoprocessing queuing system to accomplish running this sequence of operations. Since you are modifying multiple sets it does not seem like there is much to be gained by interacting with a grid of parameters vs the tool dialog. Grant Smith‌ brought up a case of picking multiple pairs of base feature and compare feature. In the normal Feature Compare tool, select a base, select a comparison layer, name the output, click Run, and immediately repeat to add the next tool to run when the first one finishes. The parameters from the first one are maintained so if only one or a few things need to be changed that can be done efficiently (similarly to "filling" a batch column in the ArcMap batch grid).  ... View more

Hi Amanda Kochanek‌, since Richard cannot share his data due to confidentiality, I'm hoping you might be able to share the data where you experienced the failure with XY Table To Points, or perhaps follow the steps I gave Richard: If you copy the header row PLUS the first data row into a new XLSX then use that as input, does the tool still fail? If so, can you replace the values with non-personally identifiable data and send that copy to us? If this error is widespread we want to understand and fix the problem in a patch so users can take advantage of the new 2.5 version of the tool. ... View more

Hi Richard Marountas, I understand the confidentiality of your data. We do have automated tests for XY Table To Point using both XLXS and XLS data, and those test cases are passing in 2.5 so we're obviously missing some different column format or data contents. If you copy the header row PLUS the first data row into a new XLSX then use that as input, does the tool still fail? If so, can you replace the values with non-personally identifiable data and send that copy to us? If this error is widespread we want to understand and fix the problem in a patch so users can take advantage of the new 2.5 version of the tool. ... View more

Hi Thomas Colson, I'm a little puzzled at this case, as our in-house test suite has cases just as you described that are passing and I just tried it myself in the application and the calc worked as expected. If you look under the hood of Calculate Geometry Attributes, it uses arcpy.da.UpdateCursor to perform the updates. Some data sources and enterprise gdb configurations require an updatecursor in an edit session, some don't support edit sessions, it's really a grab bag. So the tool attempts to start and use an edit session when required or check that the cursor can retrieve data without the edit session. If it's not able to, it raises the error you described. Attached is a screenshot of the test I ran using a SQL Server Enterprise GDB polygon feature class that has the Geography Configuration Keyword, GCS coordinate system, not registered as versioned, with archiving enabled. The Double field gets updated with the Area in sq miles as specified on the tool. I can only say this is a case to report and work withing tech support, please.   All the best, Drew ... View more

Hello, I am a lead from the geoprocessing development team and have some information to share. We are developing a new open-format for toolboxes, based on a folder structure and json files to contain the properties of the toolbox and it's tools and their parameters. This open format will support better source code management, will produce less corruption/invalid binary file problems, and better support backward compatibility across a variety of releases. The story will start to come together in the near-mid term (likely around 2.7). However, at this time, we can accomplish a lot of what you described specifically for source control by writing your code and toolbox as Python toolboxes. Creating a new Python toolbox—Geoprocessing and Python | ArcGIS Desktop  This is a single Python file (text file) that contains toolbox and tool definitions as classes. Those classes can come from other modules as well. Python toolboxes are a great capability for developers who want programmatic control of the toolbox and organization of the code using basic Python structures. I hope you can consider this approach. We even have an old utility for auto-generating the PYT based on your TBX: GitHub - Esri/tbx-pyt-translator: Utility for converting a Geoprocessing TBX file to a pure-Python PYT file in ArcGIS 10… . Lastly, you can explore how some Esri system-tool developers are using Python toolboxes by exploring the PYTs in your ArcGIS Pro installation. C:\Program Files\ArcGIS\Pro\Resources\ArcToolBox\Toolboxes Drew ... View more

H. Alex Huskey‌, pretty much exactly what you described happens once per release, most recently in October 2019 for the Pro 2.5 release that will be publicly available early 2020. We call the process Holistic Testing, as you look at not just one area of the software but usage across all the functional areas necessary to get your job done. Roughly 25 individuals from primarily the U.S., across every industry, join us at Esri development headquarters in Redlands, CA for a week of testing your workflows with your data in a new software release, and reporting problems you find directly with the development teams. It is hands-on full days of testing and talking between you and the dev teams, and extremely useful for us to see the work you are doing and any struggles you are having. It's the closest you can get to the zoo animals, outside of the User Conference showcase floor If you want more information about participation send me an email at dflater@esri.com. ... View more