Latest Contributions by DrewFlater

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.

@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

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.

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

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

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.

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.

Online Status	Offline
Date Last Visited	yesterday

My Ideas

Latest Contributions by DrewFlater

Re: GeoTagged Photos To Points should allow the extraction additional EXIF metadata (Direction in particular) - Status changed to: Implemented

Re: Add Fields (multiple) could import from existing table or feature class template

Re: Have ArcGIS Pro's Layer to KML behave like the ArcMap Layer to KML - Status changed to: In Product Plan

Re: Choose if join will be one-to-first or 1:Many

Re: Choose if join will be one-to-first or 1:Many - Status changed to: In Product Plan

Re: Field Calculator Should Honor Domains - Status changed to: Implemented

Re: Enable Undo for Python based editing tools - Status changed to: In Product Plan

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: 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