Latest Contributions by DrewFlater

There are around 100 of the most commonly used geoprocessing tools in ArcGIS Pro which can leverage parallel processing. Like you alluded to, parallel processing is not a silver bullet or one size fits all solution, so some tools use parallel processing in different ways. For some tools it is enabled by default to use all your machine cores in parallel, some tools use half, and some tools that support parallel processing do not do it by default. You can learn more about parallel processing in each tool reference topic. You pictured and described the Fill tool. https://pro.arcgis.com/en/pro-app/latest/tool-reference/spatial-analyst/fill.htm Here is the relevant excerpt.  This tool supports parallel processing. If your computer has multiple processors or processors with multiple cores, better performance may be achieved, particularly on larger datasets. The Parallel processing with Spatial Analyst help topic includes details about this capability and how to configure it.   When using parallel processing, temporary data will be written to manage the data chunks being processed. ... By default, this tool will use 50 percent of the available cores. If the input data is smaller than 5,000 by 5,000 cells in size, fewer cores may be used. You can control the number of cores the tool uses with the Parallel processing factor environment.   You can try to set the parallel processing factor to 100 and see if the performance for Fill is improved with this setting.  ... View more

@JesseWickizer is correct.  You can use and work with Microsoft Excel files in ArcGIS Pro like other tabular data sources. The only requirement to access and work with Excel files in ArcGIS Pro is that the appropriate drivers must be downloaded and installed correctly on the computer on which ArcGIS Pro is installed.  Individual geoprocessing tools that support tables as input do not list the full range of supported formats, it would be very redundant. @Bud you are right that Excel sheets (the tables inside the xlsx/xls) are valid inputs for all applicable geoprocessing tools. Note that Excel tables are read-only in ArcGIS Pro, so these tables can be the Append tool's Input Dataset but not the Target Dataset.   For more on Excel in ArcGIS Pro: https://pro.arcgis.com/en/pro-app/latest/help/data/excel/work-with-excel-in-arcgis-pro.htm ... View more

Hi all, the implementation cost for this development was not enormous, and given we want users to be able to transition easily from ArcMap (where VB calculator expressions were the default) to Pro, we feel this is an important enhancement idea. We have a working version in our open development builds and are testing assorted VB script calculator expressions. There is a significant caveat that if you were writing VB expressions that used ArcObjects functionality, such commands will not work in Pro as ArcObjects functions are not available.  @Bud you seem like you might be willing to provide example VB expressions that we can use for testing and evaluation? If you are able to provide some sample with reproducible data, that would be helpful for this development work.  ... View more

@Bud your summary is correct. ArcGIS in general has a hard limitation that any table can only have one Shape column. I talked to a few developers and our system would destabilize if we lifted a limitation that two Shape columns could be in one table as a result of a join or other process.  The Append/Upsert enhancement you explained is an easy solution for this problem, or you can write a few lines of Python code using a search and update cursor to read one feature geometry then write/calculate/update the geometry of another feature based on it.  ... View more

This idea has not received votes since 2010. If there is further feedback about the organization or user interface of processing tools in ArcGIS Pro, please log a new idea.  ... View more

ArcGIS Pro lists users custom toolboxes in the Catalog pane, and system toolboxes in the Geoprocessing pane. There is no intermingling of these toolboxes in ArcGIS Pro. There is an intention to give access to project toolboxes from the Geoprocessing pane, but again they will not be intermingled with the system toolboxes, rather in separate clearly-designated sections. These sections will not be "folders" or able to be renamed or configured, so I am not marking this issue as "Implemented" at this time.  There is a somewhat related and more recent idea about configuring the Toolboxes list here, for anyone who wants to vote or comment:  https://community.esri.com/t5/arcgis-pro-ideas/enable-arctoolbox-customization/idi-p/1001003 ... View more

Geoprocessing parameters display the parameter error icon next to the parameter label. It uses the icon style called GenericError, so the red circle with x inside is the common icon used to represent an error, not a floating red x.  The red x ,as an aside, is the generic remove icon which you can see in many places where you are removing an item from a list.  About the right side alignment idea in comparison to the left side alignment, I believe on the right side of the box would make the x more difficult to notice.  ... View more

@mj_gis that comment and picture from @MartinPrinz  is a mockup and suggestion that the tool Consolidate Map should have the same option you suggested. This tool still keeps the original databases if the map has data from multiple databases, all the datasets are not consolidated into one database. This is the enhancement that is under consideration. The Consolidation tools are definitely where this option to move all datasets into one shared database makes the most sense to the dev team.  ... View more

This idea is in planning with our development team, to add to ArcGIS Pro's KML To Layer tool in the near term.  When a geodatabase is provided which already exists, the current pattern is to overwrite the geodatabase. In the near term we will have parameters so that the user can choose to not overwrite the geodatabase but rather give a new feature dataset name and feature class prefix and those contents will be created inside the existing geodatabase.  ... View more

@Bud for scenarios which are updated existing, I suggest to use Add Join with the option to only keep matching records, then Calculate Field to calculate the target fields to get the values from the join fields (whichever fields you want). This is done internally as a sort of pre-process within the upsert option of Append, so the same strategy will work well. If there are duplicates in FC-B it will make a 1:m join.  ... View more

@Bud We had the Upsert development project in our backlog for awhile and were gathering requirements and researching how the capability could be applied to the Append tool. Seeing your Idea about a year ago, we thought it could be satisfied by the Append tool enhancement. So yes, this Idea pushed us in the direction of doing the Upsert development work in 3.1. There are always many factors at play when it comes to prioritizing our development work, and Ideas are a critical way we can work on and deliver capabilities requested by the user community. So keep up your Ideas and I'm sure more will be implemented in future releases. ... View more