|
POST
|
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.
... View more
05-15-2025
08:20 AM
|
1
|
7
|
1215
|
|
IDEA
|
@AlfredBaldenweck I submitted that as an idea: Temporarily invert map colors
... View more
05-08-2025
06:55 AM
|
0
|
0
|
311
|
|
IDEA
|
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.
... View more
05-08-2025
06:54 AM
|
2
|
1
|
414
|
|
POST
|
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?
... View more
05-07-2025
09:09 AM
|
0
|
2
|
675
|
|
IDEA
|
Related: GP tool to populate COUNT field with count of attribute occurrences
... View more
04-30-2025
09:04 AM
|
0
|
0
|
1668
|
|
IDEA
|
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.
... View more
04-29-2025
08:43 AM
|
0
|
1
|
322
|
|
POST
|
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
... View more
04-28-2025
08:46 AM
|
1
|
0
|
321
|
|
POST
|
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
... View more
04-28-2025
05:28 AM
|
0
|
0
|
276
|
|
IDEA
|
For non-Python users, I’m wondering if a pick-list or search box could be used to load pre-canned field calculations into ArcGIS Pro. Similar to Calculate Geometry, but it would work for non-spatial requirements as well. Maybe it would be called ‘Calculate Attribute’. Such as getting the count of attribute occurrences from a different field in a standalone table. GP tool to populate COUNT field with count of attribute occurrences
... View more
04-26-2025
09:23 AM
|
3
|
1
|
400
|
|
POST
|
ArcGIS Pro 2.9.5; Oracle 18c 10.7.1 EGDB I have a ROADS line FC (has an ID field) and an EVENTS standalone table. EVENTS is a linear referencing table with ID, FMEAS (double), and TMEAS (double) fields. The relationship between ROADS and EVENTS is 1:M. One road to 0, 1, or more events. Some of the EVENTS.TMEAS values are larger than the length of the related road, which is incorrect. I want to: Select EVENTS where there is only one event per road. Join EVENTS to ROADS to bring the ROAD shape length field into the EVENTS attribute table. Calculate field: For the selected EVENTS, update the FMEAS field to the ROAD's shape length. How can I do that? I am running into join errors when trying to use a SQL subquery for the selection, so am looking for a different approach.
... View more
04-25-2025
01:24 PM
|
0
|
2
|
357
|
|
IDEA
|
ArcGIS Pro 2.9.5; Oracle 18c 10.7.1 EGDB or file geodatabase A user who is not a SQL or Python person has a standalone table with an ID field. The user wants to populate a COUNT field with counts of the IDs. ID COUNT 1 1 2 1 3 2 3 2 4 1 If I understand correctly, there isn't a GP tool that can do that. Could a tool be added?
... View more
04-25-2025
01:02 PM
|
1
|
2
|
540
|
|
POST
|
ArcGIS 3.4.3; Oracle 19c 11.3 EGDB Is it possible to publish custom mosaic dataset band symbology to Portal? View raster band-4 near infrared in ArcGIS Pro
... View more
04-12-2025
08:19 PM
|
0
|
0
|
212
|
|
POST
|
@LaurensKusse_hhdelfland I would be interested in hearing Esri Support's response. By the way, you might find this interesting: Intended use case for Select Layer by Location — Intersect (DBMS)?
... View more
04-11-2025
08:33 AM
|
0
|
0
|
803
|
|
POST
|
In a SQL query, you could use GROUP BY and COUNT to find duplicate values.
... View more
04-11-2025
08:02 AM
|
0
|
0
|
1604
|
|
POST
|
@LaurensKusse_hhdelfland Best guess is that only SQL queries that use spatial functions, and where the datatype is SDO_GEOMETRY, would make use of that setting; in other words, only spatial SQL queries that you have written yourself would use that setting. @MarceloMarques might have some insight.
... View more
04-11-2025
06:57 AM
|
0
|
2
|
810
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 01-16-2024 10:57 AM | |
| 1 | 01-15-2024 02:11 PM | |
| 2 | 10-15-2025 07:48 AM | |
| 1 | 05-23-2024 12:47 PM | |
| 4 | 10-06-2025 06:56 AM |