Latest Contributions by DrewFlater

‎03-25-2024

Hi, The Metadata editor in Pro 3.3 includes an interactive table that lists the Geoprocessing History/lineage stored in the dataset's metadata, which you can delete or export. So you can choose to use the interactive experience, or for automation use the arcpy.metadata module. There isn't really a position for a geoprocessing tool given these alternatives.

‎03-22-2024

Automated metadata management in ArcGIS Pro uses the arcpy.metadata module, rather than a geoprocessing toolbox/toolset. https://pro.arcgis.com/en/pro-app/latest/arcpy/metadata/what-is-the-metadata-module.htm To remove geoprocessing history/lineage from a dataset's metadata: md = arcpy.metadata.Metadata(path_to_dataset) md.deleteContent('GPHISTORY') md.save() And to make it so when you run tools it is not saved in the metadata, use this Geoprocessing Option

‎03-22-2024

Hi @VinceE , @DanPatterson It's just a matter of prioritization. It will take many releases to update all tools that take an input field to support new field types and objects. This has not happened automatically for all geoprocessing tools in the first release of the new fields (3.2). Can you please post an enhancement idea for Sort to support the new temporal field type(s) in the Pro Ideas page, so that we can gauge user demand and prioritize accordingly? Thanks, Drew

‎03-20-2024

@LMedeirosUI can you please email me the crash dmp file you are experiencing? You can find it in this folder: C:\Users\<your user name>\AppData\Local\ESRI\ErrorReports with a timestamp matching when the crash occurred. Email to dflater@esri.com. It would be great if you would contact Esri Support to log the issue with your reproducible steps, so that the development team can work to fix the crash and any problems. As a workaround, you could try to use different tools, like Calculate Field instead of Convert Temporal Field, which offers Python-based functionality for adjusting or converting temporal field values. I won't know what tool is causing the crash until reviewing the crash dmp file using our development tools.

‎03-14-2024

@EDUARDOARDILARINCON this is being resolved as a BUG in Pro 3.3. The calculation is fixed to match the documented two decimal places for seconds and three decimal places for minutes. DDD° MM' SSS.ss" DDD° MM.mmm' So no manual rounding will be required starting in 3.3. This request was made by many users who wanted the rounded value, and no one seems to need an option for the full 6+ digits, so to keep the tool from having yet another parameter, the seconds and minutes decimals are simply being corrected to match the documentation.

‎03-11-2024

The Calculate Field expression control already grows up to 5 lines to show longer expressions. @Anne-MarieDubois comment on the other issue is about Calculate Value which is a ModelBuilder utility tool. I can confirm that the Calc Value expression control does not exhibit the same growing behavior.

‎03-08-2024

@Bud you can change the Metadata Style to anything except the default Item Description in order to see the geoprocessing history that is stored in the dataset metadata. https://pro.arcgis.com/en/pro-app/latest/help/metadata/view-and-edit-metadata.htm#ESRI_SECTION1_0FAB123C7C3C4CD49894272A899490ED

‎02-21-2024

Hi @Bud was that dataset derived by running a system geoprocessing tool or a custom ModelBuilder model or Python script tool? Has that dataset been used in a ModelBuilder model or Python script tool that applies the thick red line and labeling? I am asking, because for a number of system geoprocessing tools and custom ModelBuilder or Python script tools that define the symbology of the output parameter, the geoprocessing framework stores a layer file representing that symbology and other layer properties in the dataset metadata so that if the dataset is added to another map, the symbology and layer properties are consistent to when the tool was originally run. This system was put in place early in Pro 2.x. The goal was that the result of an analysis often has a specific symbology and layer properties that are necessary for the result to be interpreted and understood, and when that info was not stored with the dataset, only the layer produced by running the tool would have the full information necessary for the result to make sense. It's been several releases at least since the Geoprocessing framework has done this. I am not familiar with the thick red line with labeling, so that's why I'm asking about custom model or script tools. A way to be sure the layer file has been stored in the dataset metadata is by exporting the metadata to an xml file and look for the LayerFile tag. Right click the dataset in Catalog and select View Metadata. In the Catalog ribbon tab, in the Metadata group, click Save As>Save As XML>All Content. Use the browse dialog to select a location and name for the xml file. The xml file will look something like below including the LayerFile tag (I highlighted in Purple - also the XML has been "pretty printed" for easier readability). When this LayerFile is present in the dataset metadata, when the mapping system adds that dataset to a map, the LayerFile properties are automatically applied to the layer. If you find the LayerFile and do not to keep this information, you can delete that part of the XML, save the file, then back in the Catalog, select the dataset, and in the Catalog ribbon tab, in the Metadata group, click Import and browse for the XML file that you saved with the cleaned out LayerFile. If you can find what system or custom processes have been run using that dataset (the XML metadata also contains a useful lineage tag), we can then find out why the LayerFile had been embedded in the dataset metadata in the first place.

‎02-14-2024

These concerns about the tbx format are heard and acknowledged. The binary format of tbx means that there are opportunities for persistence streams to become corrupt while saving changes into the tbx, and these corrupted binary streams are almost always unrecoverable. There are not tools that can be used to understand problems related to toolbox corruption or unexpected things like the toolbox having empty contents. For these reasons and more, a new toolbox format, atbx, has been developed and Pro 3.0+ uses this new format by default. The atbx format is a zip archive containing json and other text files that define the toolbox properties, and tools inside the toolbox. The atbx format is less likely to become corrupt. If you encounter a corrupt atbx, you can extract the contents like a zip file, copy and paste the files and folders inside the extracted directory into a new folder, and re-archive as a zip then rename to atbx. This may help you recreate a new toolbox from the contents of a broken atbx. At this time there is no plan for a public utility or process for fixing or retrieving content from corrupt or broken toolboxes, in either the tbx or atbx format. But we are taking steps to make the atbx format and its specification more public and interoperable with other systems, and it is infinitely more able to be recovered than tbx due to the new storage format.

‎02-14-2024

This idea has not received further comments or kudos since it was added a few years ago, so it will not be prioritized in our development plans. The suggestion from @DuncanHornby to use ModelBuilder with an iterator and the Alter Field tool is really good. You can build a model that takes the alias table (1) as input, iterates (2) through each row which is a pair of one field name and the new alias, gets the existing field name (3) and new alias value (4) from the table row, and passes this into the Alter Field tool (5) to perform the alias update. You can see that my NewFieldAlias values have been used correctly and the layer has been updated with the new aliases (6).

‎02-12-2024

Table To Geodatabase offers a simplified tool for converting multiple input tables of various formats into one geodatabase. Export Table can be used if you wish to control the output table name or other settings applied during the conversion/export. Both tools can exist and be useful, find and choose the tool that suits your workflow.

‎02-09-2024

Hi @Derek_Scholar this work is in progress now for the ArcGIS Pro 3.3 release. Initial testing is showing this option may be supported again in 3.3, but I'll reserve that final determination for when 3.3 is closer to releasing.

‎02-07-2024

Hi @Katie_Clark , You could consider using this geoprocessing sample for converting the lines to polygon. This will maintain the attributes. https://www.arcgis.com/home/item.html?id=5d99da321d2f4e66a39731a707953b24 If you haven't used a geoprocessing sample in Pro before, it's really easy! https://pro.arcgis.com/en/pro-app/3.1/help/analysis/geoprocessing/share-analysis/geoprocessing-samples.htm#ESRI_SECTION1_635D1E675ED342A387AA0259243F3629

‎02-05-2024

Hi @jakek I just tried to reproduce what you described in ArcGIS Pro 3.2 and could not. Can you review the steps and see how it might be different for you? Add a layer to a map, for me called "Streets" Click the Select By Attributes button in the Map ribbon to open that window. Specify an Expression of ObjectID is equal to 1. Click OK to run the tool and get the single feature selected. Add a new group layer to the map, for me called "test" Move the layer "Streets" into the group layer "test". Click the "Streets" layer in the group layer in Contents to select it. The Select By Attributes window opens with the layer selected in Contents specified as the Input Layer, and it is the history of the last expression applied to that selected layer that enables this feature. So if you do not have a layer selected, the Expression will be empty when you reopen Select By Attributes. The Input Rows parameter should be set to the "test\Streets" layer, which is the Streets layer in the test group. The Expression of ObjectID is equal to 1 should be recalled.

‎01-19-2024

@Bud tabbing to the parameter information i is a requirement for accessibility standards (Section 508). It is natural for this tab stop to be placed immediately before the parameter control to provide the context for the parameter value that is to be specified. However we need to refine/improve this tabbing to make the parameter information popup display more consistently with other popup i buttons in ArcGIS Pro, also to correct the bug that multiple tab hits need to happen to get to the parameter control.

Online Status	Online
Date Last Visited	4 hours ago

My Ideas

Latest Contributions by DrewFlater

Re: GP tool to clear geoprocessing history from feature class

Re: GP tool to clear geoprocessing history from feature class - Status changed to: Already Offered

Re: Can't Sort Table on "Date_Only" Field Type?

Re: ArcPro 3.0 did not fix scheduled tools

Re: Choose decimal places of coordinates calculated using "calculate geometry" - Status changed to: In Product Plan

Re: Field Calculator — Vertically expand expression textbox (to multi-line textbox) - Status changed to: Needs Clarification

Re: View FC geoprocessing history in Pro UI?

Re: FC has symbology and labelling permanently stored in enterprise geodatabase?

Re: Toolbox Doctor for tbx files - Status changed to: Closed

Re: add a "Table to Alias" tool in ArcGIS Pro - Status changed to: Closed

Re: Table to geodatabase tool - specify output feature class name - Status changed to: Closed

Re: Have ArcGIS Pro's Layer to KML behave like the ArcMap Layer to KML

Re: Mention deprecated status of "Preserve Attributes" option in tooltip for "Feature To Polygon" tool

Re: Keep Previous Select by Attributes in Geoprocessing Window

Re: When tabbing through GP tool parameters, don't tab into Help tooltip - Status changed to: In Product Plan

Re: Can't Sort Table on "Date_Only" Field Type?

Re: View FC geoprocessing history in Pro UI?

Re: FC has symbology and labelling permanently sto...

Re: Why is ArcGIS Pro's Multicore Support Still So...

Re: Pro not exporting all fields of hosted feature...

Wildfire Response GIS