Latest Contributions by Bud

For multi-part lines, it would be helpful if there were a GP that could: Create a single midpoint for the entire feature. Place the point halfway along the entire length of the line (all parts considered). The Feature Vertices to Points GP tool doesn't seem to do this. It creates a point for each part. The Feature to Point GP tool (with the "Inside" option) doesn't seem to do it either. The point isn't placed halfway along the line. It seems to do something else, like possibly place the point in the middle of the feature envelope. Then snap the point to the line, to satisfy the "Inside" criteria. That's not the same as the line midpoint. Could a GP Tool be added that creates a true midpoint for multi-part lines? Thanks. ... View more

In the Attribute Table in Pro: It would be helpful if we could group rows by a common ID into an expanding tree. Similar to what we can do in the Access / Excel / SQL clients: That would make exploring data easier.   If that's not possible, then an alternative might be to visually separate rows with a border, or something similar:   I'm aware of the conditional formatting idea. But I think this is different...I don't think this would be considered conditional formatting. Thanks. ... View more

In my experience, SQL is often a gap in ArcGIS Pro users' skillsets. It seems to me that a course on SQL in ArcGIS Pro would be beneficial. Could Esri consider offering such a course? Or some other kind of resource? Some lesser-known SQL topics could include: Using correlated subqueries in select by attributes, definition queries, Append GP tool expression, etc. Example: One-to-first joins: Control what related record is used Using ST_GEOMETRY functions in select by attributes and definition queries Use the Diagnostic Monitor to view SQL queries sent from Pro to the database SQL in Arcade Querying GIS data in SQL clients like SQL Developer Using geodatabase system tables in SQL queries Working with data from on-prem external databases using SQL, in conjunction with GIS data, via database links, etc. Database views and query layers SQL comments in select by attributes and definition queries Generating sample data with SQL in a query layer or view: Generate grid line features using SQL Convert grid lines to polygons Generate a EGDB database view that has a spatial SQL query in it using the Select Layer by Location GP tool’s "Intersect (DBMS)" option. ... View more

Pro 2.6.8; non-spatial table; Oracle 18c EGDB: In the attribute table: If I delete a row by right-clicking the row —> Delete Row, then the scroll bar in the Attribute Table navigates away from my position in the table: It's quite aggravating when that happens; I lose my place where I was working in the attribute table. And that isn't how ArcMap works. Could that behavior be changed so that the user's position in the Attribute Table is preserved when deleting a row? Thanks. ... View more

When creating a database view in an Oracle EGDB using the Create Database View GP tool: I can successfully create a view if there isn't a comment at the beginning of the SQL query: select 1 as unique_id from dual --a comment But I can't create a view if there is a comment at the beginning of the SQL query, like this: --a comment select 1 as unique_id from dual When I move the cursor out of the View Definition textbox, then the SQL is automatically changed to be single-line: --a comment select 1 as unique_id from dual Which makes the SQL invalid (Oracle probably thinks the SQL is one big comment). ERROR 999999: Something unexpected caused the tool to fail. Contact Esri Technical Support (http://esriurl.com/support) to Report a Bug, and refer to the error help for potential solutions or workarounds. [ORA-00928: missing SELECT keyword] DBMS table not found [ORA-04043: object A_TEST_VW does not exist] [a_test_vw] Failed to execute (CreateDatabaseView).   Could Pro be enhanced so that we can put SQL comments at the beginning of database views? Or put differently, could Pro be enhanced so that it doesn't automatically convert the SQL to be a single line (don't remove line breaks). ... View more