Latest Contributions by DrewFlater

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

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

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

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

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

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

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

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

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

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

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

@hherrmann_coj if you download the zip file and extract it you'll find the .proExportedUI file, which can be imported in the Options dialog to load the quick access toolbar customization. I've pictured this working in 3.1.   ... View more

@COH_Spatial it is in our near term plan for KML To Layer, which includes other important enhancements and bug fixes as well. It will not be complete in ArcGIS Pro 3.2 which is the next release coming this year.  ... View more

Hi @dvonck, Expanded support for Parquet has been added in ArcGIS Pro 3.2. Big data connections are now called Multifile Feature Connections (as of Pro 3.0) but your existing bdc connection file will still work. Datasets in the bdc/mfc connection based on parquet files will now display when added to a Pro map, and can be used as a read-only input data source for most geoprocessing tools.  ... View more