Latest Contributions by DrewFlater

In this new toolbox I can see one tool, DeleteVersionGetParcels, but the tool is devoid of any properties or parameters. The script tool refers to an embedded script source that only includes this code # Geoprocessing Script Tool arcpy.AddMessage('Hello World') So there is no reference to an external script file, which may or may not have been renamed.  I think it will not be productive for me to try to troubleshoot the problem further, it seems to be a problem with your system or installation of ArcGIS, or there may be some other steps or conditions that are hard to diagnose via a community forum. If you are able, please contact Esri Support to explain the problem you are having and get hands on troubleshooting and support.  ... View more

We can see your test tools in the atbx: asdfasdf, dfgdfg, dsfsdf, Model, Script, sdfsdf, yrdy, ZX. But the tool list inside the toolbox has lost those tool references.  Can you further explain how you were modifying the Python script file name in Windows File Explorer? Were you renaming a file internal to the atbx archive? It seems all the script tools in the toolbox have embedded/internal Execution script files, rather than reference paths to external standalone .py script files.  ... View more

Just to clarify the product plan, is to have all of your project toolboxes listed in a top section of the Toolboxes tab in the Geoprocessing pane. They will not be intermixed with System Toolboxes, rather in a specific Project section.  ... View more

@DWR_BuckEhler , @SteveCole , @Anonymous User , @MarianMcDuie  Apologies for the lack of information presented while closing the Idea. I should share the perspective of the development team that lead to the issue being closed. The same KML conversion tools have been supported for the last decade and more in ArcMap and ArcGIS Pro. When a tool is released there are things about the tool that cannot change, in order to better support backward compatibility (i.e. a model or script written in a previous version should continue to work in new versions). The tool name is one of the things that cannot change. So while a request to change a tool name may sound simple, it is not something our team does lightly if ever at all. We can change the UI label that appears on a tool while maintaining compatibility, though again this is only rarely employed because the underlying tool name would not change, nor would the function name arcpy.LayerToKML change. Changing the display name is problematic because it introduced a difference between the tool users see in the UI and in Python.   Onto a few substantive matters. I included the wiki link to define what KML is, as I believe that some of those following or voting on the issue might not know that .KMZ is actually the most common file format associated with KML. The KML in the ArcGIS tool name refers to the overall format and not the specific file extension of the output. Across a polling of common GIS and mapping applications, .KMZ is universally supported, so I do not fully understand why you would need .KML. .KMZ is a compressed archive of a .KML file plus other supplemental files that make the KML behavior and visualization richer, but if the .KML is needed all it takes is renaming the .KMZ to .ZIP and you can simply copy the .KML out of the archive. The owners and inventors of the format themselves suggest to use KMZ for almost all KML needs, as .KMZ supports many things that .KML does not and is compressed for a smaller file size.  Lastly, Esri's development teams do highly value user feedback. Specifically the ArcGIS Pro geoprocessing development team that owns the KML conversion tools values this site and community. During the ArcGIS Pro 3.0 release we were proud to be the team to deliver the most completed Ideas of any ArcGIS Pro development team. We receive many forms of feedback and have to prioritize it. The development engineers that work on this tool include a single software developer and a product specialist, so prioritization is critical for a small team. When we have to choose between improving functionality and fixing bugs, or changing the tool name or supporting .KML output , we thought it was best to update this Idea with the decision that the change will not be prioritized.  I hope this might make the decision more clear.  ... View more

@PhilLarkin1 which tool's executable script did you rename to cause the initial problem?  ... View more

Hi @PhilLarkin1 , sorry you have experienced this! When I try the same steps you described, the tools in the toolbox are not corrupted, and when I open the tool properties it simply says on the Execution page that the Script file at the previous path no longer exists.  If you report the bug to Esri Support we can further troubleshoot the problem. If you're willing to upload the atbx in a zip here we can start looking at the problem ASAP.  ... View more

The data format is KML, and .KMZ is a file extension associated with this file format.  https://en.wikipedia.org/wiki/Keyhole_Markup_Language There is a basic KML file within the .KMZ archive if someone needs the plain KML. But it will not contain all the information from the export of a layer only the basic features.  ... View more

Just for clarification, the Calculate Field window pictured at the top is a little crowded because of the edit session banner and controls at the top of the tool. The fix in the Pro 3.1 release doesn't make the dialog bigger by default or automatically, but if you make the dialog bigger and reposition, that size will be remembered the next time you open the tool.  ... View more

A dedicated Concave Hull or Alpha Shape geoprocessing tool has not been developed and is not planned at this time.  The Aggregate Points tool can often be used to accomplish the generation of similar enclosing shapes.  ... View more

@DanPatterson  that's the right issue. Instead of implementing a different error message for this condition, we just implemented it to allow PYT or ATBX 🙂 ... View more

This was implemented along with ENH-000138309  in Pro 3.0. ... View more

@JordanFuhrmann  it is currently in our Pro 3.1 release plan, though these plans are subject to change. I'm comfortable to say Near Term.  ... View more

@Michael_VanHatten I have not been able to look at this case further to see if I can reproduce the problems when adding the Add Join step and using feature services. I am getting some help from a teammate to keep looking into this. I would say that tech support would be more able to give live troubleshooting help for an involved problem like this. The BUG you mentioned about was specifically about Select Layer By Attribute, and that error has been resolved in Pro 3.0 (confirmed by some other commenters in the other threads). Since you are encountering more problems, we want to understand and resolve them. Thank you for your patience and help to understand the problem.  ... View more