Latest Contributions by DrewFlater

New options are being added to the Package Map and Consolidate Map geoprocessing tools in ArcGIS Pro 3.4.  ... View more

A direction field is provided in the output feature class created by the Geotagged Photos To Points tool.  https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/geotagged-photos-to-points.htm   If there are additional photo properties that are desired to be maintained in the output feature class's attribute fields, please log them as additional Ideas. ... View more

@Michele_Hosking  thanks for your feedback. I observed the same error you described when one of the fields in the template table already exists in the input table. This is a defect, which has been logged with Esri Support as BUG-000166581.  This bug does not cover your feedback that you'd like to selectively choose which fields to add. If you are looking for that capability I think it might be better to use scripting. For example, you can specify the a list of fields to exclude (my list is Name and Type), while adding the remainder of fields to the input based on fields from the target.  exclusion_list = ["Name", "Type"] #Update with your field names to exclude field_list = [] for field in arcpy.ListFields('Template_Table'): #Update with your template table name or path if not field.required: if not field.name in exclusion_list: if field.type=="String": field_type = "TEXT" elif field.type=="Integer": field_type = "LONG" elif field.type=="SmallInteger": field_type = "SHORT" elif field.type=="Single": field_type = "FLOAT" else: field_type = field.type field_list.append([field.name, field_type, field.aliasName, field.length, field.defaultValue, field.domain]) arcpy.management.AddFields('Input_Table', field_list) #Update with your Input Table name or path   ... View more

There are a few other things described in the comments, but the main point of the Idea is the support of transfering domain descriptions from the input to the output KML/KMZ.  This issue will be resolved in the ArcGIS Pro 3.3 release, now in Beta. The Layer To KML tool now honors the choice in the Transfer Domain Descriptions environment https://pro.arcgis.com/en/pro-app/latest/tool-reference/environment-settings/transfer-domain-descriptions.htm . So you will need to apply that setting to get the description values in the output KML.  ... View more

In ArcGIS Pro 3.3, the "first" in the one to first join will be the record with the matching field value with the lowest Object ID. Additional sorting may be provided in a future release, based on the Idea https://community.esri.com/t5/arcgis-pro-ideas/join-control-what-related-record-gets-used/idi-p/1237557 ... View more

The "Join one to first" Join Operation  has been developed for Add Join in ArcGIS Pro 3.3, available in Beta now.    ... View more

This functionality is delivered in ArcGIS Pro 3.2. You can use a choicelist of domain values in the Insert Values portion of the field calculator expression builder control.    ... View more

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.   ... View more

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   ... View more

@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 [email protected].  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. ... View more

@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. ... View more

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.    ... View more