Latest Contributions by DrewFlater

‎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.

‎12-15-2023

I have published a new Geoprocessing Sample tool for averaging lines. You can download it and see if it works for your use case. https://www.arcgis.com/home/item.html?id=e47c400683ad443781660cef529a7637

‎12-14-2023

Hello all, now that Pro 3.2 is available, I wanted to mention that a remaining scheduling bug related to Select Layer By Attribute has been fixed. https://support.esri.com/en-us/bug/the-scheduled-execution-of-the-select-layer-by-attribut-bug-000159167 I hope that some of those who posted above might be able to upgrade to Pro 3.2 and see if their scheduled tools are working now.

‎12-14-2023

Since this was labeled for Geoprocessing I'm marking this already offered as the Pro 3.2 extent control shows the order of the extent coordinates match what is used in Map Properties. If you would like to recommend that feature class Properties be made consistent with the map extent and geoprocessing extent, please submit an Idea with the Geodatabase label. You have also described that the geoprocessing extent and properties extent have different formatting with commas and other characters. For typical use of the geoprocessing extent, there isn't really a use case for manually copying and pasting of coordinates, as it has buttons to get the extent directly from the map, a layer, or geodataset. https://pro.arcgis.com/en/pro-app/latest/help/analysis/geoprocessing/basics/extent-control.htm Unfortunately the Register with Geodatabase tool you pictured does not have an extent parameter, rather it is the type Envelope which doesn't support the same things as an extent. If you think it would be beneficial to have these easier ways of populating the extent for Register With Geodatabase, you could log another idea with the Geodatabase label to change the parameter type from Envelope to Extent.

‎12-08-2023

@pocalipse , @CharlesMacleod is correct that there is not a way through the Pro .NET API to change or set Geoprocessing Environments for your project. @pocalipse can you explain what your intention is for having an Add-in or Extension or other SDK element setting the project Geoprocessing environments? @CharlesMacleod mentioned the MakeEnvironmentArray function, which you can use to set all of desired environment settings, then reuse that environment array for any tools you run using ExecuteToolAsync, so the effect can be quite similar to setting the environments to the project. For example (pseudo code) var env = Geoprocessing.MakeEnvironmentArray(outputCoordinateSystem: a_spatial_reference, extent: an_extent_window); Geoprocessing.ExecuteToolAsync(tool1, params1, env); Geoprocessing.ExecuteToolAsync(tool2, params2, env); Geoprocessing.ExecuteToolAsync(tool3, params3, env); Maybe you have a different reason for setting the project's geoprocessing environments beyond their use for environments used in the tools you execute in an Add-in. Please let us know any details for this request. Since this is the SDK Questions forum, and the question is answered that we do not have a function to set project environments in .NET, if you would like to submit an idea like "Update project's geoprocessing environments using .NET" to the ArcGIS Pro Ideas site, we can get comments from the user community and use that to try to prioritize this new development work. https://community.esri.com/t5/arcgis-pro-ideas/idb-p/arcgis-pro-ideas

‎11-27-2023

I have my polygon feature class and point feature class (Point_1) in the same geodatabase. And set up this immediate calculation attribute rule on inserts. So when I draw a new polygon, it automatically calculates the number of intersecting points and puts it into the count_from_att_rule field. var points = FeatureSetByName($datastore, "Point_1") var countPoints = Count(Intersects(points, $feature)) return countPoints

‎11-20-2023

Hi - you need to set up an immediately calculation attribute rule: https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/calculation-attribute-rules.htm Which will run some Arcade code when a new feature is inserted into your geodatabase feature class. The Arcade code to run will get a Count of the Intersects because the new $feature and the house centroid points layer made into a feature set. https://community.esri.com/t5/arcgis-online-questions/arcade-expression-to-count-points-in-polygons/td-p/523659

Online Status	Offline
Date Last Visited	7 hours ago

My Ideas

Latest Contributions by DrewFlater

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: How can I average multiple polylines?

Re: ArcPro 3.0 did not fix scheduled tools

Re: Consistent extents notation in FC properties and GP tools - Status changed to: Already Offered

Re: Update environment settings

Re: Create spatial join on the fly

Re: Create spatial join on the fly

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