Latest Contributions by Bud

ArcGIS Pro 2.9.12: If I click a geoprocessing tool parameter and then hit F1, the generic ArcGIS Pro help is opened. Bud_0-1711476071291.png https://pro.arcgis.com/en/pro-app/latest/help/main/welcome-to-the-arcgis-pro-app-help.htm  I think it would be better if the help for that specific GP tool (Copy Features) were opened instead. I'm aware I can hit the (?) question mark button to open the tool's help. But I think F1 should do the same thing if the tool is in focus when the F1 key is hit. Open this: https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/copy-features.htm    ... View more

ArcGIS Pro 2.9.12; Oracle 18c 10.7.1 EGDB: I want to export a table or FC, but I don't want the metadata to be included in the output. Could an environment setting be added to these tools that would let me exclude the metadata? Export Features and Export Table Copy Features and Copy Table GP tool to export FC without metadata ... View more

ArcGIS Pro 2.9.12; Oracle 18c 10.7.1 EGDB: Are there any existing geoprocessing tools that export a FC or table, but the metadata doesn't get included in the output? Use case: Testing a metadata issue but trying to avoid Python code or manually exporting/modifying/importing XML. ... View more

Edited. ArcGIS Pro 2.6.8; Oracle 18c 10.7.1 EGDB: Tools like Add Relate and Calculate Field get tracked in the item metadata (aka the FC geoprocessing history). Add Relate doesn't alter the FC schema or alter the data. Why track it in the GP history every time a user uses that tool on an EGDB FC? It adds a lot of bloat to the item metadata, which can cause issues. See: GP tool to clear geoprocessing history from feature class. Idea: Only track GP tools that alter the FC schema or data in the geoprocessing history. ... View more

ArcGIS Pro 2.9.12; Oracle 18c 10.7.1 EGDB: I have cases where I need to clear the item metadata (FC geoprocessing history) of a feature class in the geodatabase. For example, in 2.9.12, there is an issue where Route Event Layers are slow to the point they're unusable, due to extensive geoprocessing history in the FC. Removing the geoprocessing history in a FGDB copy via XML solves the issue, proving that the geoprocessing history is the problem. It would be ideal to have a GP tool to remove the geoprocessing history from existing geodatabase feature classes, rather than manually fiddling with XML.  Related: Don't track GP tools like Add Relate in FC geoprocessing history ... View more

If multiple features are returned in the Explore popup for a given FC, then I want to sort the results by CREATED_DATE descending by default. For example, in a CONSTRUCTION_DRAWINGS polygon FC, I want the newest record to be listed first. To make it easier to find the most recent construction drawing. Could functionality be added for applying a default sort order to Explore results for a specific FC?  Related Experience Builder idea: Control order of specific FC’s features in popup (show newest feature first) ... View more