Latest Contributions by Bud

‎05-15-2025

ArcGIS Pro 3.5.0 The "Add Spatial Clause" option is buried under the "Add Clause" button/picklist. I'm wondering if it would be more noticeable & intuitive to have a separate button for "Add Spatial Clause" right beside the "Add Clause" button. Or something better.

‎05-15-2025

@MichaelVolz GIS services aren't something I work with much; I'm more of a Pro user. But I did notice this: Spatial definition query by TanuHoque To answer you question, unfortunately we won't be able to support publishing a layer with spatial clause in its active definition query in the first release. We will continue working on it and hope to support sharing in a future release. Sharing layers with definition queries When a layer is shared as a feature layer or within a map image layer, only the active definition query is retained and honored. All other inactive definition queries are dropped. If the query contains a spatial clause, an error is returned. See 00428: The definition query spatial clause is not supported by the server for more information.

‎05-15-2025

ArcGIS Pro 3.5.0 Spatial definition query: When I click a layer in the Use the geometry of section, the layer's thumbnail is displayed, which is good. However, the layer name does not stay highlighted after clicking it. I think the layer name should stay highlighted after clicking it. Related idea: Display layer name in spatial definition clause

‎05-15-2025

It looks like the only spatial operation available for spatial definition queries is intersect. I'm wondering if other spatial operations would be beneficial, such as the equivalent of what's available in Select By Location. Select By Location - Relationship pick list:

‎05-15-2025

Add a spatial clause to a definition query A definition query can only include one spatial clause. It would be helpful to have multiple spatial definition clauses for complex spatial querying requirements. Related: Spatial Definition Query — Select multiple intersect layers in single clause Union Feature Layer — Group layers with identical schemas into a single layer; apply properties to group New Query Layer: Union

‎05-15-2025

Filter features with definition queries Definition queries are composed of one or more clauses. There are two types of clauses: attribute clauses and spatial clauses. All clauses are written in SQL syntax and constructed using the query builder. I'm wondering if "All clauses are written in SQL syntax" is misleading, and doesn't apply to spatial definition queries.

‎05-15-2025

@TanuHoque Are there plans to add more spatial operations other than "is intersected by" in future releases? Or are there other spatial operations available, and I'm just not seeing them? Spatial Definition Query - Spatial operations other than intersect

‎05-15-2025

Do spatial definition queries use SQL or ArcObjects code to perform the query operation? (ArcGIS Pro 3.5) Assorted thoughts: My best guess is ArcObjects is used, not SQL, to perform the query. I say that because I don't see any SQL when I switch to SQL Editor mode (Pro 3.5 Home Use; Oracle 18c Express database; SDO_Geometry; non-GDB; ). I suppose using ArcObjects instead of SQL makes sense: Spatial database queries are often orders of magnitude slower than ArcObjects, even if the SQL query and spatial index are set up & used correctly. File geodatabases don't have spatial SQL functions. I assume ArcObjects would be easier to implement, instead of writing database-specific SQL spatial queries for each kind of geodatabase, each kind of enterprise database, and each kind of spatial type (i.e. ST_GEOMETRY vs SDO_GEOMETRY). Maybe a lot of the ArcObjects spatial querying code already existed for tools like Select By Location [or clipping layers in the map properties] and could be repurposed for spatial definition queries. It almost seems like Esri did something similar to what I suggested in this comment (it was originally a separate idea): https://community.esri.com/t5/arcgis-pro-ideas/spatial-definition-query/idc-p/1552967/highlight/true#M32579 "One option would be Spatial SQL Definition Queries. But...spatial database queries are notoriously slow and are difficult to set up correctly...so I'm wondering if “Select By Location” functionality could be used as an alternative mechanism, since that tool is surprisingly fast, even for large datasets." Our organization is on Pro 3.4.3 for the foreseeable future, which doesn't have the new spatial definition query functionality. As an alternative, I wonder if I could steal the SQL from the Select Layer by Location GP tool, since it has an "Intersect (DBMS)" option, which creates a database view that has a spatial SQL query: https://community.esri.com/t5/arcgis-pro-ideas/select-layer-by-location-intersect-dbms-create-a/idi-p/1365586 Maybe I could put that SQL logic in a regular SQL-based definition query in Pro 3.4.3. Or just write an SQL spatial definition query from scratch. And test the performance to see if it's acceptable.

‎05-08-2025

@AlfredBaldenweck I submitted that as an idea: Temporarily invert map colors

‎05-08-2025

Sometimes it's easier to read content if it's inverted or in dark mode. For example, I inverted an old land survey in GIMP the other day and it was much easier to read—I noticed some details I had missed previously. I suspect some Pro maps would be easier to explore and read if the colors were inverted. Could an option be added to temporarily invert map colors in the map pane? It would just be enabled while exploring a specific area in the map. I'd disable it when done. Source: @AlfredBaldenweck 's comment in Temporarily invert image colors for dark mode georeferencing. Maybe not what you're thinking of, but I think this would be a great addition to the View tab to just invert the entire map.

‎05-07-2025

ArcGIS Pro 3.4.3; Oracle 19c 11.3 EGDB; Traditional versioning moving edits to base. My organization has recently upgraded from Pro 2.9.5 (had attribute rule limitations) to 3.4.3. And ArcMap has been phased out. So now, we are taking the plunge into calculation attribute rules. We're planning to use attribute rules to automatically generate IDs in ASSET_ID fields in various existing FCs. Question: What do we need to consider when using an attribute rule to generate unique IDs for new rows in an existing FC? We may want to use use the attribute rule to enforce data integrity in general as well. How to start/continue the sequence at the largest existing number in the field? How to pad the numbers with zeros? Should the field allow nulls? Should the field be manually editable? Or should we disallow edits? Consider data dependencies/syncs to external systems like a work order management system. We could check to make sure there is a unique database index that enforces unique IDs. Or alternatively, switch from a database index to an attribute rule for this, since the database index causes issues when splitting linear assets. Consider relationship classes to other FCs or tables. I don't think we have any for our asset FCs, but it's still good to think about this. Should we prevent row deletions, for the purpose of integrations to external systems? Is there anything else we should consider?

‎04-30-2025

Related: GP tool to populate COUNT field with count of attribute occurrences

‎04-29-2025

ArcGIS Pro 2.9.5; Oracle 18c 10.7.1 EGDB I have an EVENTS non-spatial table (input table) joined to a ROADS FC (join table) via Add Join. I want to do a field calculation on an EVENTS field, utilizing the shape length from ROADS in the field calculation. However, the shape length has not been included in the joined attribute table, so I can't use it in Calculate Field. Could the shape length (or shape area) fields be included in joins for field calculations? I understand that the shape length isn't a real field in the database table; it's generated on the fly in Pro via ArcObjects. And I understand why the SHAPE field isn't included in the join; we wouldn't want multiple SHAPE fields in the same attribute table if joining from a FC to a FC. But that doesn't mean the shape length can't be included. I can't add a temporary SHAPE_LENGTH field in the FC because this is a corporate enterprise geodatabase that is locked, and I don't own it. And I would prefer not to copy data to a FGDB (and add a helper field) every time I need to do something like this in Pro. Creating a query layer with a length field via SQL wouldn't be suitable because joining to query layers is too slow in Pro. For what it's worth, sometimes this happens accidentally. Sometimes the shape length does get included in joins. I don't know why it happens, maybe it's a bug, but I suppose it proves that it's possible under certain circumstances. I thought I already had an idea for this, but I can't find it right now.

‎04-28-2025

Update: Linear Referencing M Coordinates have been implemented in GeoJSON. https://github.com/opengeospatial/ogc-feat-geo-json/issues/55 https://github.com/opengeospatial/ogc-feat-geo-json/pull/130

‎04-28-2025

For #1, I could use the Frequency GP tool or Summary Statistics GP tool to output a separate FGDB table with info about the duplicates. Then join the output table back to the EVENTS table and perform a selection. Then #2 and #3 should be relatively straightforward. GP tool to populate COUNT field with count of attribute occurrences Edit: When joining EVENTS (input table) to ROADS (join table), the shape length from ROADS won't be included in the resulting join. I suppose that complicates things, since I can't add fields to the enterprise geodatabase tables/FCs, such as a temporary ROAD_LENGTH field. Join to FC — Include shape length field in attribute table

My Ideas

Latest Contributions by Bud

Spatial Definition Query — Make the "Add Spatial Clause" option more visible

Re: Spatial Definition Query - Spatial operations other than intersect

Spatial Definition Query — Highlight chosen layer

Spatial Definition Query - Spatial operations other than intersect

Multiple spatial definition query clauses

Re: Do spatial definition queries use SQL or ArcObjects?

Re: Spatial definition query

Do spatial definition queries use SQL or ArcObjects?

Re: Temporarily invert image colors for dark mode georeferencing

Temporarily invert map colors

Considerations for using attribute rule to generate sequential IDs in existing ASSET_ID field

Re: Select duplicate rows in FGDB attribute table using SQL

Join to FC — Include shape length field in attribute table

Re: GeoJSON Linear Referencing M Coordinates

Re: Standalone Table — Select where no duplicates, join to FC, update table's field with joined shape length

Attribute Table — Keyboard shortcut to enter today...

Shrink Lines — GP Tool

Would a EGDB constraint attribute rule error messa...

Advanced views without locking layer schemas

Computed column (SQL expression field) in AGOL tab...

Experience Builder Tips and Tricks

Mapping and Charting Enterprise Databases

Roads and Highways User Group (RHUG)

ArcGIS Arcade

GIS Jobs