Latest Contributions by Bud

ArcGIS Pro 2.9.5; Oracle 18c 10.7.1 EGDB: I'm using the Make Aggregation Query Layer tool to join from an FC to a table. Both items have an ObjectID field, as expected. The Unique Identifier Field parameter seems to be mandatory. An ObjectID field is listed in the parameter picklist by default. What item does the ObjectID field pertain to? The FC or the table? My best guess is the ObjectID field belongs to the FC (the Target Feature Class). But I am wondering if the tool could make it more obvious. Related Esri Support cases: 03651040 Make Aggregation Query Layer - Target Feature Class "table not found" error 03651111 Make Aggregation Query Layer - ERROR 000840 Target Feature Class parameter 03651113 Make Aggregation Query Layer - Error 000358 No fields can be mapped to unique identifier ... View more

It looks like the Make Aggregation Query Layer tool creates an inner join by default.  It would help if users could choose to use a left join instead, via a parameter in the tool, since the purpose of the tool is to facilitate analysis without the need to write SQL. ... View more

It would be great if we could add a Catalog item to the map as a query layer using an OOTB button. That would be an efficient way to create a query layer; no need to fiddle with query layer setup. And it could be a good way to add an item to the map without locking it. Pro already has all the information it needs to create a query layer; I know this because it automatically creates query layers for Catalog items that aren't registered with the geodatabase when an unregistered item is added to the map. Related: Control schema locking behavior in ArcGIS Pro Contents — Right-click FC to create query layer   ... View more

It's my guess that ArcGIS Pro loads Excel spreadsheets into a table in memory, and that allows Pro to use SQLite SQL expressions on the spreadsheet. ArcGIS Pro uses the SQLite SQL dialect for expressions on Excel files? I'm wondering if that could be taken a step further: Not only allow SQLite SQL expressions (definition queries, Select By Attributes, etc.) but also allow full-blown SQL SELECT queries on the in-memory Excel table.  For example, a query that could Split comma separated values to multiple rows, but using the recursive WITH clause in SQLite (dynamic), instead of Python (static output). There would be lots of other uses, too. If the spreadsheet is already loaded into an in-memory SQLite table, then why not allow full SQLite queries on the SQLite table? I think that would really bolster ArcGIS Pro's dynamic analysis capabilities. ... View more

When creating a query layer using the New Query Layer dialog or the Make Query Layer gp tool: Provide an option, such as a checkbox, to include all rows from the underlying query; no rows would be hidden. I can’t stress enough that I want to see all rows from my SQL query. Related: Is ArcGIS Pro the right tool for tabular/join-based geodatabase analysis? ... View more