Latest Contributions by DrewFlater

@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

Hi again @WentaoChe . This is a Topographic Production tool, but unfortunately our Ideas system does not offer that as a label, so I will act as a go-between to that development team.  This enhancement was submitted last year but marked as a known limitation by the development team as of this year: https://support.esri.com/en-us/bug/the-line-endpoints-output-from-the-polygon-to-centerlin-bug-000146471 I have marked this Idea as Needs Clarification, to see if the workaround provided by the development team can satisfy your request.  Make a copy of the input features. Measure the width of the polygon. Launch the Densify geoprocessing tool and use half the width of the polygon for the Distance parameter. Launch the Polygon To Centerline geoprocessing tool and use the densified features for the Input Features parameter. ... View more

This limitation has been resolved in ArcGIS Pro 3.2, which will be released later this year. The fix is already in the early software snapshots, including the Beta being prepared for release to the early adopter community early this fall.  ... View more

Look how easy it is in ArcGIS Pro 3.2 with the redesigned field map in Spatial Join (and other tools) to select multiple fields to summarize and pick an Action like Sum!    ... View more

ArcGIS Pro 3.2 has a parameter tip to indicate that the join table definition query will impact the join.    ... View more

The OID field naming for the output of KML To Layer has been addressed in ArcGIS Pro 3.2. The feature classes should always have an OID field named OBJECTID.  ... View more

Here is what we have in ArcGIS Pro 3.2   ... View more

The ArcGIS Pro 3.2 release will have a new Match Fields parameter on the Spatial Join and Add Spatial Join tools that can be used to accomplish what is described in this issue. When looking at set of join features that match the desired spatial relationship to a target feature, the match field values will be evaluated to see if they are the same. If the match field values are the same, the spatial join will be made. If the match field values are not the same, those join features will be excluded from the spatial join.     ... View more

In ArcGIS Pro 3.2, you can set the tool Icon in the tool Properties window on the General page. This icon is used whenever the tool is placed on the ribbon, in a Tools gallery, or on the Quick Access Toolbar. You can click the Icon to change it.      ... View more

@Bud Your two ideas about Display XY Data and XY Event Layers have been combined, and both are in the product release plan for ArcGIS Pro 3.2.  The context menus and ribbon for standalone tables has been configured with a Create Points From Table menu with the options to make a points feature class from the table XY coordinates (XY Table To Point) and to make an xy event layer (Make XY Event Layer). We think this will clarify the actions, and also bring xy event layers back in an accessible location. Your comment also mentioned Route Event layers, which have been on the table context menu all along under Display Route Events.  Pro 3.2 (in development) sneak peak: There is no plan for adjusting the Add Data menu in Pro 3.2, so changes to those options are not included, though the Pro mapping authoring development team is considering a redesign of that menu and available options in a future release.  ... View more

Hi @WentaoChe , hope you are back from UC safely, nice to see you there.  Since you show you are willing to string together multiple commands like in your AML to achieve the best performance, I was curious and tried several workarounds including using the memory workspace as an intermediate location for writing points before converting to shapefile. Unfortunately the bottleneck seems to be the shapefile writing, and I couldn't get performance faster than just going directly to shapefile from RasterToPoint.  For my test of 2 million tif cells, I found RasterToPoint with direct output to shapefile to take 55 seconds. Compare this to writing to memory (4 seconds) then CopyFeatures to shapefile (~70 seconds) was slower. I even tried using arcpy.da Search and Insert cursors to read the memory data and write to shapefile, and that took about 50 seconds so still not faster.  I am relabeling this to the Spatial Analyst extension, since that team owns the RasterToPoint tool. They might be able to offer some suggestions, though I think the limitation is in shapefile writing across the board.  ... View more

After technical review, the development team has found that renaming fields using the Make Feature Layer and other tools' Field Info parameter cannot be supported in ArcGIS Pro due to the new design of layers and field definition storage.  In ArcMap, renaming fields using the Field Info has this description: Field names can be given a new name by using the Field Info control. The second column on the control lists the existing field names from the input. To rename a field, click the field name and type in a new one. Field names defined in the Field Info control will be honored in subsequent tools. However, if this tool is the last tool in a model, the field names will be obtained from the source data on disk. To maintain the field names, the new layer has to be written out to a new data using Copy Rows or Copy Features tools. Notice specifically that the new field names were only used by subsequent geoprocessing tools, and were not displayed in the application. Workflows that were previously using Copy Rows or Copy Features to make a new output with the renamed fields can use the Export Features or Export Table tools in Pro, which offers a Field Map parameter where fields can be renamed, among many other things. If there is a workflow that is impacted by creating this intermediate copy of the dataset, you can consider writing the output of Export Features to the memory workspace for fast performance and so you will not have another copy of the data to clean up.  ... View more